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..
All the guides I've found thus far that have described how to root your phone and flash to a new ROM have required using a modified ROM. Is it possible to turn a G1 into a Dev Phone 1 without the use of a hacked ROM?
If I understand the guides correctly, you need to flash back to RC29 to gain a root console, then you need to replace your recovery partition with one that will take ROMs signed with different keys, then you need to replace the bootloader, and finally you neeed to flash from a modified ROM.
Would it be possible to instead replace the bootloader, recovery partition, and ROM with their stock Dev Phone counterparts, thus essentially turning my G1 into a stock Dev Phone 1? The Dev Phone 1 has root access enabled, so wouldn't I enjoy all the benefits of the hacked ROMs?
Sorry if this has been answered elsewhere, but the guides seem to focus on modified ROMs and a search revealed nothing.
You can downgrade and root, after that install official ADP 1.5 and eSPL but this doesn't really make sense, grab JF's Cupcake ADP 1.5, hSPL and you will have more fun.
The recovery system > original recovery, more options, real backup. So is hSPL > eSPL.
In this thread it says I have to replace the recovery partition with a modified one so that the phone will accept images that have been signed with different keys.
Will the recovery partition already on my phone accept ADP images, allowing me to skip this step and only deal with the SPL and an ADP image?
hSPL only gives you the ability to write non-matching NBH files. With eSPL or hSPL, you won't be using NBH files anyways, so this doesn't matter. Might as well use the stock eSPL. And yes, you can certainly write the ADP1 image once the eSPL is installed, or you can write any of the custom images... I wouldn't use the word "hacked", since those based on the official ADP1 1.5 image really aren't hacked, they're just customized. And of course, once the eSPL is written, you can switch between system images at will without any kind of crazy hacking procedure to do so -- that's what eSPL is made for.
Alright, let's take this a step further...
I am trying to identify the exact set of files that determine ADP1 vs. G1. I flashed the JF ADP1.5 and ADPCP2.0. The later was identifying itself on the phone as T-Mobile G1, despite the file name. I returned to JF, but used the boot from ADPCP2.0 and did manage to get a lot of the speed in it, as it is much faster. I still want the whole file system, though, but I need to be on an ADP version. Before you go on about su and root and stuff... I have it. But programs such as Spotter remain free if you are ADP branded. So the question is what do I need to keep to keep ADP?
Thats easy. The file that identifies to the OS if its a G1 or ADP1 is /system/build.prop. Note that you can customize this file however you wish.
The main *real* difference between the ADP1 and the G1 that gives the ADP1 infinitely more power than the G1 is the bootloader. With the engineering bootloader, you can do anything.
Sprint HTC Mogul
I have done a lot of researching and haven't found a particular solution to my problem. I am fairly new to ROM flashing, so I may have made an unrecoverable mistake.
When I began to unlock the device, I used the TitanUnlocker which I now see that only should be used with pre-GPS. I thought it was successful and tried to flash the stock ROM then proceeded to the custom ROM. I have also tried to install the radio because of course, it doesn't have the radio like it should have. However, it won't boot and is in the following state:
When booting into WinMo, it sticks at the splash screen and also says No Radio. I have tried installing the radio via SD card, but the bootloader doesn't seem to recognize it and so it makes me believe that the microSD card slot is busted.
On the bootloader, it says:
TITA100
SPL-1.20.Olipro
I have tried flashing the stock ROM but it fails out at 11%.
Update for clarification: I cannot use Hard-SPL-MFG to get Olipro-2.40 since I cannot connect to activesync.
If there is anything you can think of to fix this, or the correct combination of bootloader, ROM, and radio, please let me know as this is my primary phone at the moment. Thank you!
Update: I also figure I'd try a different SD card (smaller) to see if that solves the problem with the updating via card.
Moved to general as not rom development
Figured out the problem. The 2gig card was rejected and it flashed with a 512mb card.
riseoftheinferno said:
Sprint HTC Mogul
I have done a lot of researching and haven't found a particular solution to my problem. I am fairly new to ROM flashing, so I may have made an unrecoverable mistake.
When I began to unlock the device, I used the TitanUnlocker which I now see that only should be used with pre-GPS. I thought it was successful and tried to flash the stock ROM then proceeded to the custom ROM. I have also tried to install the radio because of course, it doesn't have the radio like it should have. However, it won't boot and is in the following state:
When booting into WinMo, it sticks at the splash screen and also says No Radio. I have tried installing the radio via SD card, but the bootloader doesn't seem to recognize it and so it makes me believe that the microSD card slot is busted.
On the bootloader, it says:
TITA100
SPL-1.20.Olipro
I have tried flashing the stock ROM but it fails out at 11%.
Update for clarification: I cannot use Hard-SPL-MFG to get Olipro-2.40 since I cannot connect to activesync.
If there is anything you can think of to fix this, or the correct combination of bootloader, ROM, and radio, please let me know as this is my primary phone at the moment. Thank you!
Update: I also figure I'd try a different SD card (smaller) to see if that solves the problem with the updating via card.
Click to expand...
Click to collapse
you get this fixed? If not you can flash from bootloader. You just need to plug it in. But if I remember correct you need to be synced for bootloader 2.40. So you need to flash a pre gps 2.xx radio and flash a WM 6.0 rom. then you should be able to flash bootloader 2.40
I was using the new HTC Gratia Rom that was posted in the development forum, was restoring some apps with Titanium Backup manager when my phone rebooted, then it got stuck in a boot loop. I wiped it and rebooted again but no joy, stayed stuck in the loop.
Anyway, I recently installed a new recovery image, one of the ones for jailbreaking the PS3, so I have no USB access. Also it has a few extra options for wiping than the Amon RA recovery, and I guess I shouldn't have used the format boot option! Now on bootup all I get is "FASTBOOT USB", though I can still get into the psfMod recovery image.
That isn't much use to me though, as I stupidly deleted my nandroid backup and the update.zip file from my SD Card earlier while tidying it up a little bit. I don't have any other way of accessing the SD card and attempts to push another recovery image (with USB access) have failed.
I've also tried to install RUU's, both a T-Mobile UK one and a WWE one. That results in the following error: "ERROR [140] BOOTLOADER VERSION ERROR".
I guess because the current image version is: 3.31.110.1 and the RUU is only: 2.73.110.26. I don't think there's an RUU of this version available, from reading it sounds like it was an OTA, it's not something I installed myself, T-Mobile sent me this phone recently after my screen stopped working properly.
If you've managed to read this far without falling asleep, any suggestions would be welcome hopefully not just that I should buy a card reader cos I could do with getting my phone going again asap.
You got access to another phone which uses a micro SD? Could use that to put the zip onto the card.
Making a goldcard springs to mind as well
Sent from my HTC Hero using XDA App
Thanks for the tip, I had considered this already but I thought my brothers Legend (he doesn't live close) was my best bet. Turns out I had access to an N95 that did the trick
same problem
im a complete n00b
screen got replaced last month. new software was installed im guessing.
tried to use the tmobile ruu's to repair. there isnt one i can use though.
tried putting an engineering spl onto my sd card and using fastboot not really sure what happened there but it did not work.
does anyone have the appropriate update in zip format. not sure how i will get it to work but im trying all the things i read.
i do have backups but im not really sure what to do with them.
other than htc has anyone ever created an ruu?
mithdol
mithdol said:
im a complete n00b
screen got replaced last month. new software was installed im guessing.
tried to use the tmobile ruu's to repair. there isnt one i can use though.
tried putting an engineering spl onto my sd card and using fastboot not really sure what happened there but it did not work.
does anyone have the appropriate update in zip format. not sure how i will get it to work but im trying all the things i read.
i do have backups but im not really sure what to do with them.
other than htc has anyone ever created an ruu?
mithdol
Click to expand...
Click to collapse
What is the problem with urs exactly?
the problem is that im stuck in a cyanogen boot loop.
i have access to the generic fastboot only. therefore i have no ability to repair my phone from within the phone itself.
my phone is currently on hboot 1.76.0007.
i thought i had flashed clockworkmod. but for some reason or another beyond me it has disappeared.
the version of android i have running is 2.1, the tmobile version. the update number is 3.31.110.1. i understand that is the perfected spl version.
i have tried to fix using the ruu files. but i understand that the version on my phone as an ota update. therefore no ruu is applicable at this time.
i have tried many methods mentioned in various forums with no success.
thanks for responding to my post so quickly.
mithdol
Problem solved now
and the solution was so obvious............
...and what was that obvious solution? Because I'm facing a similar problem...
Thx in advance!
Been running dual boot system for over 6months no issues flashing either WINMO or Adroid. Everthing worked o.k.. Then moved into NAND but message says Kernel failto=ed to open. I thought maybe it was me. Did it again failed. I tried CWR partitioning and still failed. I've tried 3 different ROMs and no boot.
I tried to even go back to SD boot with old stable Rom and now I can't load ANY Android ROM. I boots to green splash screen and then back into WINMO.
Days spent on this need a seperate set of eyes. WINMO roms all boot just fine.
Did you follow the step-by-step guide from this post [URL="http://forum.xda-developers.com/showthread.php?t=893948] [GUIDE] Flashing Your First HD2 NAND Android Rom [For Newbs][/URL], try downloading all the files again any give it another go and make sure to follow the instructions in the link above. I hope you get to fix it.
That was the guide I used, and everything went as planned but no kernel opened. Will try again. Right now NO Android roms wil boot from SD card even after installing a new class 4 card and full FAT format. I guess if it's not broke don't mess with it.
did u format it to fat32 and put it as primary?