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..
I tried after 2 weeks of investigation, to upgrade from 6.1 to 6.5. I downloaded hardspl and Ryans 6.5 Heavy for sprint. I read everything about doing the install. I made sure Windows Mobile Center was working and sync'd. I started the the hardspl and did everything it asked. I watched the Mogul go into I guess bootmode. The Red, Green, Blue and white, and then nothing. Somehow the phone became disconnected. According to Windows Mobile Center. I tried re-connecting and failed. I tried AFM's solution for flashing from SD card, with no change. Stuck. I copied RUU_signed.nbh on the SD card. That didn't do anything. I put the 6.1 program from HTC on the Card with the .nbh file and still no good. Beginning to think I didn't read enough. Anyone know how to get this phone back to normal again? Thanks for your time.
Hootyhoo said:
I tried after 2 weeks of investigation, to upgrade from 6.1 to 6.5. I downloaded hardspl and Ryans 6.5 Heavy for sprint. I read everything about doing the install. I made sure Windows Mobile Center was working and sync'd. I started the the hardspl and did everything it asked. I watched the Mogul go into I guess bootmode. The Red, Green, Blue and white, and then nothing. Somehow the phone became disconnected. According to Windows Mobile Center. I tried re-connecting and failed. I tried AFM's solution for flashing from SD card, with no change. Stuck. I copied RUU_signed.nbh on the SD card. That didn't do anything. I put the 6.1 program from HTC on the Card with the .nbh file and still no good. Beginning to think I didn't read enough. Anyone know how to get this phone back to normal again? Thanks for your time.
Click to expand...
Click to collapse
Just passing through here at xda, I can help you if you this evening, no time during day today. If you don't get it before then. You can reach me at ppckitchen.org in the chat section.
But until then you can post what your bootloader version says right now, in order to see what you got.
current bootloader version?
current radio version?
If your current bootloader is either the 2.40 or 2.47 then all you might need to do is flash a custom rom. Hard to tell if you don't give all the info needed to know where you are at exactly.
Also the nbh on the sd card has to be renamed to TITAIMG.nbh not left as the RUU_signed.nbh it was. SD card can be NO BIGGER than 2gig. and must have a format of FAT32.
Hit me up in ppck this evening if need be. Justpctech might be around as well.
Well thats where the problems are coming from. I'm using a 4g card and I forgot to rename the file. Yes the bootloader was 2.4. Screen says : upper right corner -RUUNBH .........Starting at left side towards top: TITA 100 MFG.....SPL-2.40.OLIPRO....CPLD-9
i believe the the problem was the SD card and the naming. Thanks so far. Heading to work at the moment but will try later. Thanks again.
Perfect, that one is best IMO.
I recommend this from where you are.
1. Flash the sprint stock rom from here Because it contains a gps radio, 3.42.02 which is fine. Now if you already KNOW you have that radio, skip this step and go right to step 3.
2. After flashing that rom when it comes to the part "tap here to align screen" : At that point instead of tapping here to align screen, do a soft reset. This will allow the customizations to NOT run.
3. Start flashing custom roms. If you don't like the one you flash, then just flash another, your bootloader and radio are good if you are on this step.
Just a note to anyone else, all you are doing is this:
1. Unlock with hardspl, 2.40 or 2.47
2. Upgrade radio to gps (this can be done by flashing that stock rom I supplied) or just putting the radio rom nbh on card and flashing.
3. Flash custom roms.
I'm trying to reflash the stock WM ROM on my Vogue, but I keep getting Error 260 in the RUU. My phone is currently on an Android ROM (the latest Incubus26Jc's Super FroYo, which I installed yesterday) but I should note that the sdcard wasn't being read by Android, and my phone can't mount to be viewed on my computer.
How can I revert back to the stock ROM now?
Thanks for any help.
biomech91 said:
I'm trying to reflash the stock WM ROM on my Vogue, but I keep getting Error 260 in the RUU. My phone is currently on an Android ROM (the latest Incubus26Jc's Super FroYo, which I installed yesterday) but I should note that the sdcard wasn't being read by Android, and my phone can't mount to be viewed on my computer.
How can I revert back to the stock ROM now?
Thanks for any help.
Click to expand...
Click to collapse
Error 260 is a connection error (sorry for being so obvious). Can you post the exact steps that you are following to flash?
Haha yeah, I know it's a connection error. I've done many flashes so it's weird that it doesn't work anymore.
I press the power+camera+reset buttons to go into the tri-colour screen, plug in the phone to my computer, run the stock Bell RUU and then get the error.
Tried this at least 5 times now, restarted my computer a few times, tried different USB ports. No luck. =/
biomech91 said:
Haha yeah, I know it's a connection error. I've done many flashes so it's weird that it doesn't work anymore.
I press the power+camera+reset buttons to go into the tri-colour screen, plug in the phone to my computer, run the stock Bell RUU and then get the error.
Tried this at least 5 times now, restarted my computer a few times, tried different USB ports. No luck. =/
Click to expand...
Click to collapse
I had to ask since I needed to make sure that you were doing the right thing . You mentioned also that Android is not picking up your SD card. Try to put a nbh rom file in the root of your card (hopefully 2 GB or less), stick it in the phone and reboot into bootloader. The device should pick it up and try to flash from SD. If this doesn't work, then I am afraid that you may have a bad board in your phone.
egzthunder1 said:
I had to ask since I needed to make sure that you were doing the right thing . You mentioned also that Android is not picking up your SD card. Try to put a nbh rom file in the root of your card (hopefully 2 GB or less), stick it in the phone and reboot into bootloader. The device should pick it up and try to flash from SD. If this doesn't work, then I am afraid that you may have a bad board in your phone.
Click to expand...
Click to collapse
Ah, the thing is that the 512mb card that came with my phone stopped working the other day, so I've been using an 8gb one instead, and I'm too far from any computer store to go and buy a smaller one.
I did try the .nbh trick but I'm guessing the phone wasn't reading the card.
biomech91 said:
Ah, the thing is that the 512mb card that came with my phone stopped working the other day, so I've been using an 8gb one instead, and I'm too far from any computer store to go and buy a smaller one.
I did try the .nbh trick but I'm guessing the phone wasn't reading the card.
Click to expand...
Click to collapse
Try to get a 1 or 2 GB and see if that works. If it doesn't.... I think your phone may be toast...
Okay, I'll try that as soon as I can. Really appreciate the help! Thanks.
biomech91 said:
Okay, I'll try that as soon as I can. Really appreciate the help! Thanks.
Click to expand...
Click to collapse
No problem and good luck!
hello all i was trying to install the android on my hd2 phone
got all the way to where i ran the rom updated utilerty and now its stuck on the htc screen ,at load up of the phone
i have read about this happening ,
and read that you hold the volum button and power and boots up ,,,which it does goes to system and the plug it in to my laptop ,,,,,
then get the USB on the screen of the phone ,,,,
but i dont have a rom to back it up with ,,could some one please point me in the right direction of where to get this fome and how to get it to work thanks
moose579 said:
hello all i was trying to install the android on my hd2 phone
got all the way to where i ran the rom updated utilerty and now its stuck on the htc screen ,at load up of the phone
Click to expand...
Click to collapse
I assume (since about ten people per day ask exactly this) that you flashed magldr but magldr didn't start as expected? This is caused by (as I type half a dozen times a day) by not having 2.08.hspl AND a compatible radio.
i have read about this happening ,
and read that you hold the volum button and power and boots up ,,,which it does goes to system and the plug it in to my laptop ,,,,,
Click to expand...
Click to collapse
bootloader
then get the USB on the screen of the phone ,,,,
but i dont have a rom to back it up with
Click to expand...
Click to collapse
not sure what that means, sorry.
,,could some one please point me in the right direction of where to get this fome and how to get it to work thanks
Click to expand...
Click to collapse
You haven't given any real details as to what you have done so far.
Details details details.
So, tell us what you did so far, please. Please be detailed, with names, filenames, versions, etc. not just 'i flashed that thing and now nothing works'
hope this helps more
ill start from the start
i first ran this file HSPL3_PKG.exe this run fine without any problems
then i ran this file rom updateutility from this rar folder ive downloaded called DFT_LEO_MAGLDR113_DAF
now this is where it all went wrong ,i ticked all the boxes and went thought the set up by following this video
got to 6;08 into the video and followed the steps
then got to 7;04 in the video and this is where the phone stayed on the htc screen for 30 mins ,,,and its done nothing
so i unplugged it
now i read that its possible to get the phone back to booting up with another offical rom from htc but carnt find the rom that ill need ,,plus the windows mobile wont reconise my phone in usb mode
hope this helps you a little more to solving my problem
and sorry i carnt post the link to the video yet as ive not done my 8 posts
ok, so its all fine so far, you just haven't yet done the next step, which is flash a compatible radio. (had you changed the radio after flashing hspl and before flashing magldr, magldr would have started straight away)
(I shall assume that you have a regular hd2, not a t mobile US model, since you haven't said, if it IS a tmous, then its a different problem)
download radio 2.15.50
enter bootloader
plug in usb
count to 5
run customruu to flash that radio
reboot
magldr should now start
thanks for your reply
ill go and find this radio now and keep you posted
thankyou
you rock dude
thank you so much for your time posting ,,
100% working andriod now
anything eles i should know please post
Lovely.
Only thing to know is that you shouldn't need to flash radio or magldr again now, if you want a different sized rom you may have to reflash cwm to change partition size, but if you ever have probs booting or whatever, nine times in ten someone will tell you to task29 and reflash stock and start over,,,, nine times in ten that's massive overkill.
Read read read is the best advice I can offer, see what issues others have and read the answer,, one day that issue might be yours, and you'll have a head start solving it. Never panic and start random flashing, that always ends badly, and means any help request posts are harder to work with.
thank for your reply
just a quick question for you
ive got a 16gb sd card in with about 300 app/games ,,and ive installed about 20 so far but now phone says memory full ,,should they be installing on sdcard instead of the phone memory
or is this normal for the phone memory to run out so fast
Depends on the rom, some leave 200+ free, some far far less. That's why most roms support an ext partition, which the phone treats as internal.
Backup your SD card (it will be wiped) start phone into cwm, then (I think its) advanced - format SD card, or something like that. Create a 1 or 2 gb ext partition, swap 0, and reflash the rom. C
The rest of the SD will be formatted to fat32 just like it is now.
It will detect the ext partition and use it as internal memory automatically. You should not choose the option to "move app to SD card", that will take the app off the ext partition and put it in the fat32 partition,, and some apps wont work from fat32.(angry birds for example)
Hey guys,
So my problem, I downloaded Xperia Beta ARC installed it seemed that everything was fine, used the storage alterer, since then my sd card doesnt work in any device! iv not been able to flash another rom or anything to my HD2.
So i tried the HD2 Android NAND Toolkit and task29'd it.
now im stuck on the loading screen just sits there does nothing. i fear iv ruined my HD2 any advice would be great. iv litlary tried everything! im not going to be able to use the sdcard anyone got any ideas of flashing a rom to the unit, i tried to get wp7 onto it but keep getting a error.
Any help much appreciated.
update -
trying downloading win 6.5 exe see if i cant get it back to original state! fingers crossed. could use a program to fix my SD card as i think its just a partition issue.
Ross
r0sc0sco said:
So i tried the HD2 Android NAND Toolkit and task29'd it.
now im stuck on the loading screen just sits there does nothing.
Click to expand...
Click to collapse
yes well it would do, you just removed the rom by task29'ing.
no clue what the storage alterer is, so cant help, but simply entering magldr, then from there cwm should let you flash a rom (once you sort teh card out, of course)
EDIT - oh right you used the toolkit, which also removes magldr(that isn't always the case), so you will need to flash that again too, , magldr - cwm partitioning - new rom.
To be honest, iv tried everything to fix the sd card, but its just a bit gutting its working then next minute its destroyed due to partions! will just purchase a new one and see how it goes!
Got the windows 6.5 onto my phone, im hopeing i can now go to win7! until i sort out my SD card issue.