Big problem here, though I don't think it's hopeless...
I flashed my Kaiser with HardSPL 3.34, then unlocked the SIM, and then properly set up an Android system on it.
Anyway, then I decided I wanted to go back to WinMo, so I found a stock ROM, and tried to flash it back with the KAISimg.nbh method by rebooting and holding down power+camera.
However, that image apparently contained an SPL image, and so I inadvertently flashed my phone back with a normal SPL (and unsuccessfully flashed the WinMo image). Now when I try to boot and flash using power+camera, it just sits there at "Loading...", and Android boots the kernel but can't seem to mount the file system on the SSD. So the phone is useless right now.
Is there a way to fix it or am I screwed?
EDIT: Okay, it seems I had to remove the flash drive, then boot with power+camera. I plugged in my USB cable and it went into USB mode, then I installed an official ROM from HTC's website. Seems to work now! To everyone who helped me in the parallel universe where I didn't figure this out: thanks!
For future reference, if you actually got HardSPL installed then you wouldn't be able to flash a normal SPL without going through some extra hoops. (That's the point of HardSPL). Although it will say that it flashed the SPL it will not actually overwrite the HardSPL.
Related
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*
A few days ago, I attempted to root my girlfriend's T-Mobile G1 phone, previously unrooted, by following the CM instructions in the CM Wiki page for G1 users.
Throughout the entire process, I received the expected output from the g1 screen - that is, until finally installing the latest CN stable ROM - 4.2.15.1. After this install completed from recovery mode, I rebooted the phone by pressing home + back, the screen displayed an image of a box and phone, and then proceeded to the recovery screen again; I rebooted the phone again - this is when the phone started to hang on the G1 screen.
There is a chance I may have forgotten to flash the CN ROM 4.2.15.1 before rebooting, and then subsequently flashing the CN ROM. I am not completely sure about this.
Anyways, here are the steps I took: Formatted SD Card to FAT 32; Downgraded my phone to RC29 - DREAIMG.nbh using the bootloader; after saving the recovery image file cm-recovery-1.4.img to my SD root dir, I used telnet to flash that recovery file. Next, I downloaded all the necessary OS files - DRC83 Base Defanged; Updated Radio file; 4.2.15.1 ROM. Next, in recovery mode, I wiped the phone, and proceeded to install those files in that order.
After getting the hang on the G1 splash screen, I tried to repeat the process over, from flashing the old RC29 ROM to flashing the updated ROM files. However, I have gotten the same result. Now, after reading about how to revert rooted G1 phones back to the stock firmware, I have managed to get the phone running on Cupcake - 1.5, through the CRB43 update. The CRC1 Update consistently fails during the installation - something like patch error code - failed update on line 243. I guess I may need to wait for a system update from t-mobile to get the phone up to date again.
I thought the original problem may have been a corrupted file - but I have repeated this rooting process many times, and have downloaded new files each time, and usually tried to confirm the MD5Check hash, so I doubt this is the problem. Also, today, I received a system update from TMO, and even then, the system hung on the G1 screen again. I've tried to fix this problem myself, but man, I'm at a dead end.
Any advice would help.
I have the same issue, although it first happened while I tried to upgrade from superD to CM5.
The only ROM I can get to run is the ADP1.6 from htc (the -ota- one)
I've tried every ROM and I can't even Nand back to my previous backup...
The thing is driving me nuts, but, although I reinstalled DangerSPL (with success), I can't run (because installation goes fine) anything else than stock 1.6 (which is still better than your cupcake my poor friend).
Even Defranged DRC83 won't run.
All ROMs get stuck on G1 screen...
I've opened a thread about this but so far, got no working advice.
If I have some time available, I'll try switching back from Amon_Ra's recovery 1.6.2 to Cyanogen's recovery 1.4 to see if it works (hell, that's the only thing I haven't tried. Spent a whole weekend on this ****...)
Let me know if you manage to run a custom ROM.
Good luck
alou2 said:
I have the same issue, although it first happened while I tried to upgrade from superD to CM5.
The only ROM I can get to run is the ADP1.6 from htc (the -ota- one)
I've tried every ROM and I can't even Nand back to my previous backup...
The thing is driving me nuts, but, although I reinstalled DangerSPL (with success), I can't run (because installation goes fine) anything else than stock 1.6 (which is still better than your cupcake my poor friend).
Even Defranged DRC83 won't run.
All ROMs get stuck on G1 screen...
I've opened a thread about this but so far, got no working advice.
If I have some time available, I'll try switching back from Amon_Ra's recovery 1.6.2 to Cyanogen's recovery 1.4 to see if it works (hell, that's the only thing I haven't tried. Spent a whole weekend on this ****...)
Let me know if you manage to run a custom ROM.
Good luck
Click to expand...
Click to collapse
I have this problem too, first time rooting for me too... I used this guide:
http://forum.xda-developers.com/showthread.php?t=548924&highlight=root
and got stuck on the G1 screen after pressing Back and Home after installing the same version of cyanogenmod
I am so frustrated... Just got a G1 last week from a friend as a gift, fully functioning with 2.1, but then I decided to flash a 2.2 rom, so I downloaded everything I need, radio, SPL, and a 2.2rom...
So first I rooted it, and then I flashed the radio if I didn't remember wrong, and then I rebooted the device, and that's when the nightmare begins...
My G1 started to boot loop, and I can't get into recovery but only fastboot. Then I thought if I am able to get into fastboot then I guess I still have hopes, so I downloaded the dreaimg.nhb and successfully installed it! but no luck, it still boot loop at the T-Mobile screen and couldn't access recovery...
I brought it to some guys to flash the IC as I thought it's bricked, but they told me it's probably not the IC's problem since it could access fastboot, and they told me it's probably because some hardware is broken and told me to change the mother board... but I was like hell no, cuz I could go get a new phone with that price...
I have seen some other ppl have the same problem on other threads, but no one gave a full answer, and I am pretty sure it's not hardware problem! so hopefully someone could give me some advice, thnx!
(Just so u know I am in China, so please don't tell me to bring it to the T-Mobile store... lol)
did you do a clean install of a rom once you flashed the .nbh file?
nah, I couldn't even get into recovery... if I hit the home bottom + power it will just start boot looping... or could I actually flash rom via USB?
once you flashed .nbh it will erase the recovery if i am not mistaken. since you have already flashed the .nbh your phone is very basic. might as well go for the newer spl+radio straight away.
go to here http://forum.xda-developers.com/showthread.php?t=831139
read the whole guide a few times and understand it properly before you execute them. what this combo of spl +radio would do, is it provides extra ram for our g1.
what is the current details that you get when press camera+power?
try to flash stock dreaimg.nbh and re root you phone.. follow this guide...
http://forum.xda-developers.com/showthread.php?t=1098899