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..
Related
hey there, before you yell at me to search hear me out.
i followed the tutorial to root my phone from the latest legit version of android. i installed jesesfrekes 1.5 version along with the radio(?) from htc. i figured i would bring it back to the stock version so i did some searching and found that most threads didnt say much but go search! well i did find some hints that people were saying to download the original rc29 dreimg.nbh and power on via camera and power button and go from there. the problem is that when i boot into the phone via camera button and power button, all i see are little androids on skateboards and SERIAL0, with no instructions or prompts to continue. can anyone help me out on what to do from here to get the stock firmware back, and everything back to factory?
thanks in advance!
if you don't see the image update screen before serial0, it means the file DREAIMG.nbh is not on your sdcard or the card is not properly formatted. also note that the whole linux system is published under GPL and Android is an open source project, so mods are strickly legitimate.
You plug in usb cable then hit back button from there. Then it should say fastboot instead of serial.
Two things:
Hey there,
If you want to go back to truly stock, you'll first want to replace your SPL with the stock one. Once you go back to unrooted, you won't be able to do this again without getting root back. So it has to be done first. Right now, you've got HardSPL, or Engineering SPL. Once you reflash back to the ugly rainbow original SPL, I have a feeling you've put the DREAIMG.nbh ZIP FILE on your SD card. Unlike other updates you do in recovery mode, YOU HAVE TO UNZIP THIS ZIP FILE first, and put the unzipped contents (the DREAIMG.nbh file ITSELF, around 95 MB or so) on the SD card. If you just download that zip and put it on there, it won't work.
Good luck.
Ricky
please excuse my ignorance when using the term legitimage, i just did not know what terms to use to accuretly point to what i needed to talk about.
anyways, i think the problem may be that the sd card was not formatted correctly, for the img file is definitly there. i am having a hard time formatting it via pc, since everything i right click on the drive in "my computer" and hit format, the pc says no drive found, and my phone claims "preparing sd card" also, i tried the format option on the phone itself, which apprently did not work.
So you rooted your phone, flashed spl then updated to 1.5?
gooberguy said:
please excuse my ignorance when using the term legitimage, i just did not know what terms to use to accuretly point to what i needed to talk about.
anyways, i think the problem may be that the sd card was not formatted correctly, for the img file is definitly there. i am having a hard time formatting it via pc, since everything i right click on the drive in "my computer" and hit format, the pc says no drive found, and my phone claims "preparing sd card" also, i tried the format option on the phone itself, which apprently did not work.
Click to expand...
Click to collapse
Sounds like you're using Vista?
DesignDawg said:
Hey there,
If you want to go back to truly stock, you'll first want to replace your SPL with the stock one. Once you go back to unrooted, you won't be able to do this again without getting root back. So it has to be done first. Right now, you've got HardSPL, or Engineering SPL. Once you reflash back to the ugly rainbow original SPL, I have a feeling you've put the DREAIMG.nbh ZIP FILE on your SD card. Unlike other updates you do in recovery mode, YOU HAVE TO UNZIP THIS ZIP FILE first, and put the unzipped contents (the DREAIMG.nbh file ITSELF, around 95 MB or so) on the SD card. If you just download that zip and put it on there, it won't work.
Good luck.
Ricky
Click to expand...
Click to collapse
i am putting the straight nbh file on there, and not the zip, it seems like my problem lies in formatting. and may i ask what you mean by replacing my spl? what is the importance of this, and if it is of upmost importance, how do i go about doing it?
thanks a bunch for the quick responses.
Ryanmo5 said:
So you rooted your phone, flashed spl then updated to 1.5?
Click to expand...
Click to collapse
DesignDawg said:
Sounds like you're using Vista?
Click to expand...
Click to collapse
correct to both quotes
gooberguy said:
correct to both quotes
Click to expand...
Click to collapse
Unfortunately, I have had VERY LITTLE LUCK dealing with my G1 on Vista. Anything other than casually connecting it and transferring files casues the same types of headaches you're experiencing. Trying to scan the disk, trying to format it, fix errors, even eject the disk (safely remove) causes the phone to disconnect and/or Windows to claim not to be able to read it.
I'm not saying Vista and the G1 can't work together well, I'm just saying mine don't. --So I always use my XP machine whenever I try to do anything like that. Other than that, if you're sure you've unzipped your nbh file, sorry I can't be of much help.
after doing a little bit of research i guess i need to change the skateboard version of the spl to the gay pride one for 100percent original correct? how do i do this?
also i updated the radio(whatever that means ) from the HTC website, as per the tutorial. do i have to "downgrade" that as well?
my 2c:
the sdcard has to be formatted as fat32, not fat16. i never had luck with G1 and interfacing with a computer or doing anything like rooting a phone while the sdcard was fat16. works like a charm when its fat32 though.
i managed to get skateboard SPL to recognize my dream image.nbh by formatting the sd card on a windows xp as designdawg mentioned. now im trying to figure out if i need to downgrade the spl and radio, before i flash the dreamimage.nbh on there.
gooberguy said:
i managed to get skateboard SPL to recognize my dream image.nbh by formatting the sd card on a windows xp as designdawg mentioned. now im trying to figure out if i need to downgrade the spl and radio.
Click to expand...
Click to collapse
D'OH! It's too late, I think. I told you that on my first post. You must have missed it. In order to change your SPL, you have to be able to flash images signed with the test keys. You can no longer do that because you have RC29 with the stock recovery, which will only flash google-signed keys. The only way to go back to the original SPL is to re-root your phone now.
Someone please correct me if I'm wrong.
oh no! you must have misunderstood, i have not gone back to RC29 yet, i am still on jf1.5 patiently waiting instructions here, haha
gooberguy said:
oh no! you must have misunderstood, i have not gone back to RC29 yet, i am still on jf1.5 patiently waiting instructions here, haha
Click to expand...
Click to collapse
Oh. Gooood. Well, all you need to do is download the SPL file for the original, rename it update.zip, put it on your card, home+power to get to recovery mode, then ALT+S to flash your SPL back to original. Then you can use the original SPL (Camera+power) to flash back to RC29. RC29 will reset your radio and everything, so you'll be factory fresh at that point. I would throw an ALT+W in there somewhere to wipe it if I were you, or you can always do it after you've done RC29.
You're ready to go. (I just did all this last night myself).
excuse me if this is a dumb question, but where can i download the original spl? i would search for it but im not exactly sure what to search hah. thanks a lot for helping me out once again. also, would it be okay to alt+w right before i do the update.zip for the original spl?
In case anyone is following and still having trouble with this:
1. Download the Original SPL By downloading G1OrigBootloader_nocheck.zip from http://forum.xda-developers.com/showthread.php?t=455860
2. Rename to update.zip and flash via normal Home+Power Method
3. Download Original RC29 (http://forum.xda-developers.com/showthread.php?t=442480)
4. Unzip .nbh file and place in the root of your newly formatted card.
5. Boot with Camera+Power and follow the steps given onscreen to install
6. Don't enjoy losing root : (
EDIT: In order to get to the current build you have to update in steps so after upgrading to RC29 upgrade to RC30 and then to RC33 via http://forum.xda-developers.com/showthread.php?t=479571)
PS I had App2SD for a long time so the SPL would look for my image in the EXT3 partition and then quit when it couldnt find it. So I ended up having to format it completely to FAT32 and then it worked.
Hope this helps
Hello all,
As many of you know Rogers issued an update for 911 issues and sense ui just recently, unfortunately as I attempted the update via SD card method, the first update seemed to have gone well but after once it wanted to reboot it keeps on splashing the ROGERS over and over.
I'm thinking this is most likely because I am rooted and the process just didn't agree.
I am currently running amon ra's 1.2.3 rec. img
with amon ra's 1.6 rom
32A motherboard
BTW I still get to boot when I hold end+vol down
and when I hold end+home I get amon ra's screen but is quickly taken away after a few seconds.
Any help would be much appreciated.
___________________
EDIT:
For the record I think I know the issue, just don't know how to fix it.
You see, instead of getting this:
fa rm5.static.flickr.com/4046/4298577978_f3366c55ae.jpg
(wouldn't let me post a link as I am new)
after "parsing...[SD ZIP]"
I only got
[1] BOOTLOADER
[2] RADIO_V2
help?
good news and bad news.
good news, im pretty damn sure thats not a brick as you can still get into fastboot (the vol down + power)((atleast thats what i think fastboot is))
bad news, i dunno how to fix it.
i know theres a way to revert to original stock ROM via fastboot, so im sure it is fixable. don't know about custom ROMs via fastboot.
bed time, though. good luck, man, and dont get bummed cause im 99% sure you aren't just plain ****ed.
edit: just noticed screenie, but can't see it because my girlfriends retarded wanna-be stepdad decides to look at pr0n all night and continues to install "mywebsearch" **** and i can't get to it. :/
Hopped on my mytouch, still think your good but let someone else who knows more vertify that.
another option
one other thing you can do,
go to a rogers store, and tell them you tried applying the so called essential upgrade 'b/c you care about your safety' and the '911 issue is a important fix'. tell them you recieved instructions to do w/e it is using the SD card method.
basically, you tried the update ---> phone got messed up.
i know someone else did it and it was grounds for them just giving you a new phone.
not saying 100% it'll work, but its worth it b/c you get a new device with the new ROM on it if it does.
goodluck.
cdstewart said:
I attempted the update via SD card method
Click to expand...
Click to collapse
Can you clarify which SD card method? Was it using the official DREAIMG.nbh from Rogers?
I thought that I had bricked my phone because I went for a hail mary attempt to root my phone. But unfortunately it wouldn't get past the Rogers screen.
However, after talking to a CSR, they sent me a link to the Windows 7 file and it rewrote everything back onto my phone and I was able to boot it normally again.
@r3s-rt
Ya, thanks. I figured I wasn't completely boned.
@mbk.2k3
I thought about that but when I go home+end you can see I'm using amon ra, which would mean they know I rooted and therefore void my warranty
@dotster
This is the method,
Upgrade Instructions for Rogers HTC Magic
Requirements:
Rogers Magic
Battery Level of 50% or more. Do not start upgrade if battery level less than 50%
MicroSD card formatted in FAT32, please note cards formatted in FAT will not work.
Installing the Update via MicroSD Card:
Part1
The first part will prepare the device for the actual update but will not upgrade the Operating System, the upgrade itself will be performed in Part2.
1) Download the HTC_Magic_Update_File1.zip and extract the file within, SAPPIMG.zip to the root of the memory card in this form, do not extract it’s contents and please do not change the file name.
2) Backup your personal data: All personal data (contacts, applications, photos, bookmarks, etc) stored on the device will be lost after the update process. There are also 3rd party applications on Android Market place to back up your applications and personal data.
3) Power off the device.
4) Remove the existing microSD card from your device (if there is one already installed), press in on the microSD Card to eject it and then remove it from the slot.
Insert the microSD card with the SAPPIMG.zip on it in the microSD slot, slide it into the slot until you feel a “clickâ€.
5) Press and hold the Volume Down Button and the Power buttons until the display turns white.
6) The update will begin installing, please follow any onscreen instructions, press the trackball when prompted to press “Actionâ€
7. Once the update is complete, “Press Action to Complete†will be displayed on the screen, press the TrackBall for the device to reboot and complete the first part of the upgrade process.
8. Power off the device to prepare for the step 2 below.
Part 2
Upgrading the device.
1) Delete the SAPPIMG.zip from the microSD card
2) Download the HTC_Magic_Update_File2.zip and extract the file within, SAPPIMG.zip to the root of the memory card in this form, do not extract it’s contents. Please do not change the file name.
3) Follow the same instructions as in Part 1 - step 3 TO 8.
4) Delete the SAPPIMG.zip file from the card.
Click to expand...
Click to collapse
Keep in mind this is magic and not dream
Thanks for the help guys.
cdstewart said:
Hello all,
As many of you know Rogers issued an update for 911 issues and sense ui just recently, unfortunately as I attempted the update via SD card method, the first update seemed to have gone well but after once it wanted to reboot it keeps on splashing the ROGERS over and over.
I'm thinking this is most likely because I am rooted and the process just didn't agree.
I am currently running amon ra's 1.2.3 rec. img
with amon ra's 1.6 rom
32A motherboard
BTW I still get to boot when I hold end+vol down
and when I hold end+home I get amon ra's screen but is quickly taken away after a few seconds.
Any help would be much appreciated.
___________________
EDIT:
For the record I think I know the issue, just don't know how to fix it.
You see, instead of getting this:
fa rm5.static.flickr.com/4046/4298577978_f3366c55ae.jpg
(wouldn't let me post a link as I am new)
after "parsing...[SD ZIP]"
I only got
[1] BOOTLOADER
[2] RADIO_V2
help?
Click to expand...
Click to collapse
I had the same problem while installing the new update yesterday. I had to call Rogers to guide me through it and even he couldn't figure it out. My phone just kept rebooting over and over after installing the first update. Even in recovery mode it didn't give me a chance to wipe, flash or restore anything because it would reboot in a matter of 2 seconds. The tech support guy on the phone had no idea what to do. I finally realised that I had a seperate Mini SDcard USB adapter that I could put my SDcard in and then plug into the USB. That allowed me to access my SDcard so I was able to delete the first SAPPIMG and then put the new SAPPIMG from the second update onto the SDcard. I repeated the same process from the first update (I was able to access fastboot without it rebooting), everything installed perfectly and now the phone is up and running great. If you don't have a Mini SDcard to USB adapter I'd suggest picking one up at your nearest Electronics store. I believe I picked mine up at BestBuy for $35 which came with a 4gb class 4 SDcard. The adapter is so small that it actually sits on my key-chain. Hope this helps.
Rogers Magic
Radio: 6.35.10.18
SPL: 1.76.0010
(unrooted)
cdstewart said:
@mbk.2k3
I thought about that but when I go home+end you can see I'm using amon ra, which would mean they know I rooted and therefore void my warranty
Click to expand...
Click to collapse
if you're desperate it's worth a try. maybe it's just my personal experience with them but i have a feeling most of the rogers reps/techs wouldn't know/care enough.
@FoTwoZero
Thanks that sounds just like mine.
I'll give it a shot.
Were you rooted before?
cdstewart said:
@FoTwoZero
Thanks that sounds just like mine.
I'll give it a shot.
Were you rooted before?
Click to expand...
Click to collapse
I was rooted before, this is why I'm sure I've had the same problem as many of you. It seems though that this issue doesn't just stop at us... This issue has been happening with many other carriers and I'm not sure why (as of yet). I've flashed dozens of other Sense ROM's and even ROM's without Sense for ei. Espresso and Eclair and they all worked fine before. This new Sense ROM from Rogers is fantastic. So try what I did and you should be on your way with no issues.
Now if only we can root this damn phone.
Rogers HTC Magic (32A)
HBoot - 1.76.0010
Radio - 6.35.10.18
Chynkinese said:
if you're desperate it's worth a try. maybe it's just my personal experience with them but i have a feeling most of the rogers reps/techs wouldn't know/care enough.
Click to expand...
Click to collapse
After the update your phone won't be rooted anymore, therefor your warranty will still be in effect. After flashing the first update it already changes your SPL and Radio therefor Rogers wouldn`t know if you were rooted prior to the update. If you stuck in the boot loop just follow my instructions and you will be home free.
Now if only we can root this damn phone.
Rogers HTC Magic (32a)
HBoot - 1.76.0010
Radio - 6.35.10.18
@FoTwoZero
Just did what you did and I'm up and running!
Thanks
I think they did misname the updates though.
Because in the instructions given, and picture above correspond to the 2nd zip file.
cdstewart said:
@FoTwoZero
Just did what you did and I'm up and running!
Thanks
I think they did misname the updates though.
Because in the instructions given, and picture above correspond to the 2nd zip file.
Click to expand...
Click to collapse
Happy to hear that I could help. They did misname the files but how could you blame someone who goes by the name of Rogers. I have several services with them and it's nothing but headaches with them.
I'm sure it was a rushed update as well. The devs at HTC were probably pressed for time to get this update up and out the door within a couple of days. Rogers will possibly be a major distributor for them in the next upcoming years.
Thanks a lot!
That solved it.
Anyone been able to root this ROM yet..?? I have tryed everything and I just keep semi bricking my phone.. but I can always recover it.
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!
Hi searched the threads and cant find the answer. HD2 512.Radio_2_14_50_04
Put HSPL on it no bother
Ran Magldr 1.3 it flashed, the phone said reboot but didn't. Took the battery out and the phone restarted but came up with the hit 1 error.
Put it in bootloader tried to flash a standard rom, froze at 0% then failed.
Renamed the Nbh file and put it on the memory card, back into bootloader, phone said loading but nothing happened.
Tried to run task 29 sticks at 0%
The bootloader is stating usb, so I have now ran out of ideas, so any help would be appreciated.
husky_motox said:
Hi searched the threads and cant find the answer. HD2 512.Radio_2_14_50_04
Put HSPL on it no bother
Ran Magldr 1.3 it flashed, the phone said reboot but didn't. Took the battery out and the phone restarted but came up with the hit 1 error.
Put it in bootloader tried to flash a standard rom, froze at 0% then failed.
Renamed the Nbh file and put it on the memory card, back into bootloader, phone said loading but nothing happened.
Tried to run task 29 sticks at 0%
The bootloader is stating usb, so I have now ran out of ideas, so any help would be appreciated.
Click to expand...
Click to collapse
Here is my run down. try using a different USB port just in case it is a driver issue. Did you you use a 500MB to a 4GB Sd card formated Fat 32? Maybe you got a bad download try redoanloading or copying it to the SD card, maybe bad file transfer. Make sure you try running the update as administator. Heck just keep trying period, it seems like several people or having this kind of problem as you with not being able to get the phone to boot and then not being able to flash a ROM to fix it. But through perserverience they did get it to flash just had to keep trying and trying. By chance does it even show the screen on .oot up that has the R, G, and B in red letters if so what does the R and the D have beside them?
The minute you tried to flash a stock rom from SD,, you removed hspl, even if the flash stopped at 0%. In fact it stopped at 0 because hspl is no longer there to allow the flash and I suspect you used just any stock rom, not the correct stock rom.,,,, ditto with task29.
T-Macgnolia said:
Here is my run down. try using a different USB port just in case it is a driver issue. Did you you use a 500MB to a 4GB Sd card formated Fat 32? Maybe you got a bad download try redoanloading or copying it to the SD card, maybe bad file transfer. Make sure you try running the update as administator. Heck just keep trying period, it seems like several people or having this kind of problem as you with not being able to get the phone to boot and then not being able to flash a ROM to fix it. But through perserverience they did get it to flash just had to keep trying and trying. By chance does it even show the screen on .oot up that has the R, G, and B in red letters if so what does the R and the D have beside them?
Click to expand...
Click to collapse
Hi The phone does go into the red/geen/blue boot screen. (will post later what the writing in red states)
Using a 2gig memory card which was formatted using panosonic and is fat32.
Tried different usb then a different laptop (both running windows 7) Tried a fresh download of the rom from HTC using the seriel no on the phone so should be the right one. Tried to run the RUU from both the laptop and renamed on the card. Not sure if its worth trying to put CWM on it?
samsamuel said:
The minute you tried to flash a stock rom from SD,, you removed hspl, even if the flash stopped at 0%. In fact it stopped at 0 because hspl is no longer there to allow the flash and I suspect you used just any stock rom, not the correct stock rom.,,,, ditto with task29.
Click to expand...
Click to collapse
Hi
The rom was the official one downloaded from HTC based on the phones seriel No.
Will try installing HSPL again and Magldr, but was trying to put a standard rom on, as all the comments advise flashing back to standard if your having problems. Cannot understand why it is freezing at 0% on the laptop, or just saying loading when i try to do via memory card.
Cheers
husky_motox said:
Hi The phone does go into the red/geen/blue boot screen. (will post later what the writing in red states)
Using a 2gig memory card which was formatted using panosonic and is fat32.
Tried different usb then a different laptop (both running windows 7) Tried a fresh download of the rom from HTC using the seriel no on the phone so should be the right one. Tried to run the RUU from both the laptop and renamed on the card. Not sure if its worth trying to put CWM on it?
Click to expand...
Click to collapse
If you are using a computer with Windows 7 on it when you go to run the update utity right click it first then click run as administrator. Sometimes when using Windows 7 this helps.
Edit: Ifyou are trying to flash a Windows Mobile ROM then no CWM would not .ebifit you as it is for Andriod ROMs on the HD2.
T-Macgnolia said:
If you are using a computer with Windows 7 on it when you go to run the update utity right click it first then click run as administrator. Sometimes when using Windows 7 this helps.
Edit: Ifyou are trying to flash a Windows Mobile ROM then no CWM would not .ebifit you as it is for Andriod ROMs on the HD2.
Click to expand...
Click to collapse
Same with MAGLDR.
MAGLDR and CWM are ONLY for WP7 and Android.
Reflash HSPL , install the radio you named in the OP, then try a custom win6.5 rom such as Energyrom.....
Yea I understand, but when the standard rom would not run, tried a few android roms as well.
Now have managed to install the HTC rom from the sd card, but on reboot sticks at the white htc screen. Not sure if its maybe a battery issue. So am waiting for a wall charger to be delivered.
husky_motox said:
Yea I understand, but when the standard rom would not run, tried a few android roms as well.
Now have managed to install the HTC rom from the sd card, but on reboot sticks at the white htc screen. Not sure if its maybe a battery issue. So am waiting for a wall charger to be delivered.
Click to expand...
Click to collapse
Make sure you have a current radio version and not a older version. The most current radio version is 2.15.50.14, and you can download it here. It flashes just like a ROM either via computer and USB cable or SD card, exactly the same as flashing a ROM.
you may have a nand memory corruption. The phone should have been capable of reflashing itself if you can get to the bootloader and use a proper stock rom. If your phone either fails to flash or flash completely but gets stuck on next reboot, you can have some corrupted memory sectors. The phone will be able to write on them but the information can't be read, therefore the phone will lock up. Think of them like bad sectors on a hard disk drive. I had these sort of problems with some older HTC's and Eten's, in some case you could eventually flash them but however you will still experience some problems or errors. In other cases it will simply fail on every flash attempt or at the boot screen. I only managed to fix these by connecting the board to a JTAG interface and marking those sectors as "bad" then reflashing the phone after i run a special version of bootloader directly from ram memory, line by line.
I also saw these problems on boards with problems in the cpu area (bad soldering, mechanical shocks etc).
I hope that's not the case with you, maybe you simply have some logical problems with the internal memory or the spl area.
Cheers, thinking of sending it for repair, now ran out of ideas. Installed the latest rom from HTC, it said everything from radio to wallpaper had installed correctly, but still will not get past the white screen with the HTC logo.
you can try another last thing. place a stock rom onto the memory card, place the card in the phone then place the phone in a transparent bag and put it in the refrigerator. Wait for about 1 hour, then... with the phone still in the refrigerator area, start it (don't remove it from the bag) in bootloader mode to flash it from the microsd card. Wait untill the process completes, then at the first restart when the phone is displaying the logo, quickly open the bag, remove the battery, then leave the phone & battery separate, in the bag for another hour in the refrigerator. After all this, remove them from the refrigerator and try to normally start the phone while it's still cold. If this doesn't work, then i'm afraid you have 80% chances of hardware NAND memory corruption/damage.
If this works, then you have a problem with the qualcomm chipset, it's pretty known, the BGA soldering between the chip and motherboard got damaged by excesive heat produced by the CPU and now some connections are not making proper electrical contact, thus producing errors in the cpu's normal operation. If the phone is very cold, the cpu and soldering will contract, thus giving the BGA matrix a chance to remake those electric contacts, for the moment - untill it heats up again.
The 2 problems can be related to each other. First, a CPU that works improperly (due to BGA failure) can disrupt I/O operation on the nand memory chip. Overtime this could lead to a situation where some memory blocks are destroyed due to improper handling by the qualcomm chipset and although the memory chip reports a number of blocks available for writing when you flash the device, some of these blocks are unaccesable when reading back. Somehow, if this is the case here, these blocks must be marked as damaged, so the memory chip's controller doesn't report them back as available and prevent them from being used anymore. I don't know how this can be done in HD2 as i don't have the hardware datasheet for either the qualcomm chipset or the memory chip itself. Like i've said, it was possible on some older devices by disassembling and directly connecting the cpu to a jtag bridge, as i could figure out how the cpu works from the original aplication notes and datasheets from samsung.
Thanks for that, my wife stuck it into a shop when I was out. (she is sick of me messing on with it)
They have told her it is only a software issue, not sure they know what they are doing.
If they do not fix it I will try this method.
Cheers
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)