So I'm in the process of recovering my phone from a near brick. Unfortunately I replaced CM recovery with the factory one, and now I get an error whenever I try to flash any rom, and I can't drop to console to install CM recovery.
When I try to flash, it verifies it, and starts to install it, but instantly stops and says "Installation Aborted" and quits. No other error whatsoever.
Thanks for any help.
same issue here
Easiest solution for both of you is to start over and reroot using THIS guide.
Downgrading will reflash spl, radio, and rom
update your recovery image??
I tried to update my recovery image, but when I went to type the command, flash_image was not found.
On another note, I just tried to put RC 29 SPL on it, but it failed, again with no errors.
Also, my phone will now only boot into bootloader mode.
UndeniablyRexer said:
On another note, I just tried to put RC 29 SPL on it, but it failed, again with no errors.
Also, my phone will now only boot into bootloader mode.
Click to expand...
Click to collapse
How did you try to flash "RC 29 SPL" ? By the way RC29 is not an spl, it is an entire phone image including rom, radio, recovery, and spl.
Fingerlickin said:
How did you try to flash "RC 29 SPL" ? By the way RC29 is not an spl, it is an entire phone image including rom, radio, recovery, and spl.
Click to expand...
Click to collapse
Thanks for the correction.
I put DREAIMG.nbh from the link from your post on my sdcard and booted using camera + power. It asked if I wanted to start the update image so I pressed power. The loading bar almost reaches the end, but then stops and says that it terminated and the update failed.
I looked around a little and someone mentioned that sometimes the camera button gets stuck and therefore appears to only boot into bootloader mode. I took off my back panel and fiddled with it, but the camera button didn't appear to be stuck, and it still boots into bootloader every time.
My assumption is the DREAIMG.nbh got corrupted somehow, and my only option is to buy a microsd card reader and copy a new image.
The loading bar almost reaches the end, but then stops and says that it terminated and the update failed.
Click to expand...
Click to collapse
Try downloading the RC29 file again from HERE, you may have a bad copy.
I bought a microsd reader and downloaded a good copy. I have yet to try to install CM recovery or flash a rom, but thanks for getting me this far.
I just finished your guide, and it all seems to work. Thanks for your help. I had another question, though. I have an ADP, but I followed your guide exactly, do I now have a rooted G1 as opposed to an ADP?
I'm glad everything worked out for you. There are minor differences but yes you have a rooted G1 with a batt cover worth bragging about.
Related
I think i bricked my phone by fallowing this tutorial.
http://forum.xda-developers.com/showpost.php?p=3874647&postcount=406
It happened after flashing the spl.
My phone will not go past the white "t-mobile g1" splash screen.
thank you for reading.
Damn, another brick? Did you make sure you had a PVT board and not the DVT-1, DVT-2 boards? It's a known problem with the Special SPL that it pretty much bricks DVT board phones...at least so far. (check by booting with camera+power if possible, board type is shown on the first line of text)
Can you boot using home+power? Are you just stuck at the Splash screen? If so, after about 10 mins the screen will change, giving you an triangle error symbol. At this point push Alt+L. This should give you the recovery utility, where you will have access to wipe (you should prob do one) and reflash a rom.
Of course this is all assuming you have root already.
i dont know if i actually got root i fallowed some tutorial on that too today i can do both of those boots but dont know how to flash anymore updates with my phone stuck like this
aronissleeping said:
i dont know if i actually got root i fallowed some tutorial on that too today i can do both of those boots but dont know how to flash anymore updates with my phone stuck like this
Click to expand...
Click to collapse
Ok, so what you need to do is this:
1. Wait for the error message //remember it sometimes takes 10 mins or so
2. open keyboard, hit Alt+L //this will toggle your phone to the recovery utility
3. If you have root, you may have a recovery utility that says "JF version 1.43", if not you have the stock recovery utility
4. If you have root, you could try to DL pretty much any rom although I might try the Ion rom for its stability and simplicity //there are tons of instructions for flashing a new rom
5. If no root, search in the Dev section of the Dream forum for an OTA ( Over The Air, ie. stock) rom. In particular, search for Dreaimg.nbh, and read the instructions for reflashing it. This will help you gain root.
6. reboot, and enjoy (hopefully)
If none of that works, you can find the "Bricked G1's" thread on the Dev section too. I think your prob out of luck, but it's possible someone has/or is coming close to a fix.
re flashing ill let you know the out come
lol you didnt brick it since u can access the recovery image.
anyways what happened to me yesterday, i flashed latest radio, the latest spl and it wouldnt boot. i flashed a new system image but still no boot (t-mobile screen). I wiped the system (data partition) from recovery boot, and reflashed with a new system image, worked ok... so from what i get, u need to wipe / reflash system, if you upgrade spl...
is by using a card reader on a pc the only way to flash a different img if this happens to you?
my phone is in root and i'm on the same g1 screen. if i take the battery out i can boot to recovery mode but my only options are alt-w and alt-s. i've tried wiping and reflashing with the same spl img and it's not resolving anything.
Hi, I have a problem with my G1, I've been flashing new ROMs here and there as soon as they come out basically. Now, the last ROM I attempted to flash was Drizzy's Modified JACHero ROM updated on July 6th. From then on, my flashes never complete and the G1 continues in the typical HTC/HERO bootloop. I even tried flashing a new recovery image (that didn't work, only way to get it to take was flashing the RAW image from fastboot). I tried flashing a non-hero ROM (Cyanogen's newest release 3.6.2) and it still goes into the HERO/HTC bootloop (whaaa?). So the only conclusion I can come to is that the device is no longer able to take new flashes from update.zip.
However, I have noticed in the recovery menu while I'm trying to flash, the status bar stops moving at:
Formatting DATA:...
Copying files...
After that it jumps rapidly to Formatting BOOT:... to Writing BOOT... then installation complete. Without the status bar every completely reaching 100%.
If anyone has/had this problem and knows how to solve it, could you please please please let me know? Right now I'm sitting with a paperweight... =/ Thanks.
reflash rc29 had that issue before i redid root access and all was well
Attempting now... Thanks for the advice. =)
Will Edit with update when I've finished.
OK I downloaded the RC29 and put it on my SD card, but when I try to go into the bootloader to flash it like normal, there is not instruction screen to allow me to update DREAMIMG.nbh, it just shows the fastboot screen with androids on skateboard? How to do I flash it from here? Is there a command from fastboot?
h.nocturna said:
Attempting now... Thanks for the advice. =)
Will Edit with update when I've finished.
OK I downloaded the RC29 and put it on my SD card, but when I try to go into the bootloader to flash it like normal, there is not instruction screen to allow me to update DREAMIMG.nbh, it just shows the fastboot screen with androids on skateboard? How to do I flash it from here? Is there a command from fastboot?
Click to expand...
Click to collapse
did you use power + camera or power + back button
power + camera should just auto install
NVM! Thanks rigamrts, I didn't have the SD Card in haha. Got everything fixed and running again. Can't thank you enough for all your help.
lol, very nice. Can you changed your title and put [Solved] in it please? Thanks!
It's an old problem I never got solved, but simply been putting up with. Now that Cyanogen ROM's can be updated OTA, I'd really like to get my phone back to normal...
Problem started after flashing DangerSPL. I may have flashed old radio while having DangerSPL, however, my phone is not bricked.
Symptoms:
1. Everytime I flash a new ROM, wipe or no wipe, I come back stuck at the T-Mobile G1 boot screen. The only way I've found to get through is to take out battery and boot into ADB (the Camera + Power screen) and "fastboot flash boot boot.img". This almost always work.
2. Nandroid stopped working. Nandroid always errors during the process of backing up, and I'd only have splash1.img and splash2.img in the nandroid folder of my SD card.
3. "Insufficient storage available" with Dude's and Cyanogen's builds. I'm not sure if this one is related to recovery or SPL. This might be caused by past attempts at doing apps2sd (I've done both symlink and unionfs).
I've tried flashing the old HardSPL, but everytime I've done that, I either get stuck at the T-Mobile G1 boot screen, or the phone always boots straight to the SPL screen (3 Android skateboards) w/o me holding the Camera button.
Only way I've been able to make my phone usable is my going back to DangerSPL.
this may suck but have you tried downgrading to rc-29 and rooting again?
btw, this is newport country
david1171 said:
this may suck but have you tried downgrading to rc-29 and rooting again?
btw, this is newport country
Click to expand...
Click to collapse
What should the process order be? Flash rc-29 first then try and revert the SPL?
start at the beginning of this:
http://forum.xda-developers.com/showthread.php?t=442480
david1171 said:
btw, this is newport country
Click to expand...
Click to collapse
Yessir, I agree with you 100%.
Went back to start over the rooting process, and now I'm back at booting straight the SPL screen.
I think the problem starts after I upgrade the radio to the latest. I was booting fine into rc29, but I upgraded the radio and ROM (Cyanogen) at the same time, though I'm leaning towards radio starting the problem, not the ROM.
As a workaround, does anyone know how I can flash the boot.img file to the system w/o using ADB (through recovery console)? This would remove the dependence of a computer, making my problem more acceptable.
I tried to do a "flash_image boot boot.img" but it tells me file not found. I can't see files in my SD card while in recovery console.
Figured it out, but still issues:
after "mount /sdcard" and "flash_image boot /sdcard/boot.img", I get...
"header is the same, not flashing boot"
cigar3tte said:
Figured it out, but still issues:
after "mount /sdcard" and "flash_image boot /sdcard/boot.img", I get...
"header is the same, not flashing boot"
Click to expand...
Click to collapse
What if you renamed boot to something else and tried to flash it? Maybe it won't flash it cause it's the same file name and the system won't flash because of it. Just my .02.
But another thing I was thinking was not to update the radio if your on RC29 since the new radio version wasn't out at the time of RC29 so it may be buggy. Then upgrade to a new rom then flash the new radio. Again just a suggestion.
supremeteam256 said:
What if you renamed boot to something else and tried to flash it? Maybe it won't flash it cause it's the same file name and the system won't flash because of it. Just my .02.
But another thing I was thinking was not to update the radio if your on RC29 since the new radio version wasn't out at the time of RC29 so it may be buggy. Then upgrade to a new rom then flash the new radio. Again just a suggestion.
Click to expand...
Click to collapse
I had it named 4192-boot.img actually, just was lazy to type it out on this thread.
I left the phone at the boot-straight-to-bootloader state and called T-Mobile, a replacement is on the way.
cigar3tte said:
I had it named 4192-boot.img actually, just was lazy to type it out on this thread.
I left the phone at the boot-straight-to-bootloader state and called T-Mobile, a replacement is on the way.
Click to expand...
Click to collapse
awhh how sweet lol. thats one way to get it working.
I posted this in the "Brick" thread but I have not garnered any attention and IRC has moved too fast to get any reliable help.
Hello,
I've done some searching and I cannot find any definitive answers to my problem.
I was on CM 4.2.9.1 and tried to upgrade to 4.2.10.1 and had a bad flash (stuck at android boot). I noticed there was a new update, 4.2.11.1 the next morning and thought I would wipe completely and update from RC29. I downloaded all the files necessary and used spl to downgrade to RC29 which booted fine. From there I got root and started the upgrade part. I installed the RArecovery 1.5.2 which went fine. I then installed the defanged HTC recovery image and CM 4.2.11.1 then the newest radio and rebooted. That went directly back to the RA recovery after installing the radio. From there I installed the Hard SPL. After that finished and rebooted the phone booted to the Hard SPL or the recovery image.
Thinking I had messed something up I though I could start over and try again. I then booted to the SPL bootloader and flashed the RC29 DREAIMG.NBH to start over.
After that completed the phone will only boot to the SPL bootloader, which is now the original SPL. I have tried to flash the DREAIMG.NBH multiple times with the same result. When holding down Home and Power I get the ! screen.
Is my phone bricked? Or is there an image that I can flash to save it?
Thanks for any help.
David Perlik
[email protected]
Does it boot up into RA recovery? from there you can flash any zip... If you got root and the right radio and SPL. Put the latest Cyan on your SD and boot into recovery and flash away... If you can get it to recovery you are not bricked...
Okay... i reread... may be beyond my limited knowledge...
3rd time... I would pop out your SD and put recovery.img fromhttp://forum.xda-developers.com/showthread.php?t=442480... and make sure HardSPL is on there... when you boot into recovery and get the "!" hit ALT-L to get the menu... then ALT-S to apply the update.zip(HardSPL)... heck just follow the steps from the link above...
GOOD LUCK
No recovery at all. I'm assuming it was flashed back to RC29 specs.
You're not bricked because you can boot into SPL. You still have a recovery image on there, not that it's a good one, it's just a basic HTC recovery. What you do have is a hardware problem with you camera button most likely. See if you can blow some compressed air in there, try tapping it a little bit, it may fix it.
Good luck
I got stuck in a bad situation like this a bit ago...
If nothing else, you should still be able to get the dreaming.nbh on there, upgrade to donut and then reroot.
It's not a problem with the camera button as I can still get to the SPL and flash the DREAIMG.nbh.
The DREAIMG.nbh flashes fine, everything gets an ok, but when I restart the phone it boots directly to the SPL.
Just a quick update:
I've gotten a hold of a different micro sdcard than the one that I was using in hopes that some weird formatting error was happening with my old card. Alas, even with this new and freshly formatted card the DREAIMG.nbh will still not take correctly. All parts report ok while flashing, but my phone still boots directly to the SPL on startup.
Can anyone help?
Im having the same problem, but I can get into recovery, sd only has an fat partition, I made a thread here, can the Mods delete it
http://forum.xda-developers.com/showthread.php?t=619180
I have a G1 with CyanogenMod 1.4 recovery and the original SPL. It boots into either of those just fine.
When I select to apply any zip, I get the list of possibilities. I have tried wiping many times.
Whenever I choose an option from the recovery or flash something, a message appears that says
Code:
E: Can't read MISC:
(No space left on device)
This occurs even after a wipe. Also, I know that the SD card is not full or corrupted (I generally use it in a different G1).
After I have flashed something and reboot, it simply hangs at the G1 boot screen. I left it for half an hour, and it stayed that way.
Any thoughts?
what are you trying to flash? rom might require danger spl. i don't have a g1, so i'm not positive, but i'm willing to bet on it.
I actually tried flashing the danger SPL. In spite of saying "reboot to complete installation," I know it does not work. if I hold Camera as I turn on, it is still the original SPL.
Next bet?
tal82k said:
I actually tried flashing the danger SPL. In spite of saying "reboot to complete installation," I know it does not work. if I hold Camera as I turn on, it is still the original SPL.
Next bet?
Click to expand...
Click to collapse
1.33.2005 is what the danger spl shows up as, which i believe is your "stock" spl. if you installed it and rebooted without any errors it works. simple and plain.
Does the danger SPL look like the original (RGB color testing)? That is what shows up when I boot with camera pressed.
I was trying to flash either Super D or CyanogenMod, when I follow the instructions for either of them and do the final reboot, it never leaves the G1 logo screen. Yes I know that it is a while for the dalvik-cache to be reworked.
I have flashed roms successfully many times on my other G1.
I am very curious what the error message that I posted earlier means. Thanks for your suggestions!
Sorry for the double post. I have an update. I am pretty sure there is a problem with the NAND chip or something similar. I flashed the Amon_RA recovery, and it worked. I used Amon_RA to wipe, and re-partition the SD card. I then tried flashing the HTC 1.6 image for ADP1. And it worked. It booted into 1.6 with no problem (except that I no longer had root). So I tried to get root again. First I tried the Recovery Flasher app. It said that it failed. So I downloaded the DREAIMG.nbh to get back to RC29. When I ran it, I got
Code:
DREAIMG.nbh - FAIL
Update Terminate
UPDATE FAIL
Any thoughts are appreciated. Thanks!
[RESOLVED]
UPDATE: Apparently that last bit ended with bricking the phone. I took out the SD, put DREAIMG.nbh back on it. Put it back in the phone. Re-flashed from the SPL (holding camera while pressing power). It worked. I then went through with regular rooting, putting Amon_RA on there, with Super D 1.8. Everything smooth. I have no idea what really fixed it, but everything works fine.
tal82k said:
UPDATE: Apparently that last bit ended with bricking the phone.
Click to expand...
Click to collapse
i still lol every time i hear that. phixed my brick.
Yeah.... I wish my brick would go into SPL.
*sorry double post, browser messed up*