Phone stuck at 'G1 T-mobile' startup screen, cannot access recovery mode - HELP!!! - G1 Q&A, Help & Troubleshooting

Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?

yeah:) said:
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
Click to expand...
Click to collapse
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!

alroco20 said:
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
Click to expand...
Click to collapse
This thread is old, and OP is ignorant and wants to blame ROM Manager for his own problems. If you can't get into recovery, chances are you are using one built for another phone. Find the one for the G1.

Or ran into the know issue of cm5.0.7 that fash_image sometimes (more than not) fails.. thus applications using it sometimes fail.
But you have danger spl right? So flash the recovery via fastboot.. and if you don't have fastboot/adb and intended to run these custom roms its about time you installed it.

Related

WM5-Device Will Not Load Operating System

I am having a problem that I hope someone can help me with.
I have an SX-66 with WM5 on it. The other day the device suddenly stopped booting. I can get the device to turn on, soft-reset, hard reset and get into bootloader mode, but whenever I try to boot the operating system it gets stuck on the colored stripe boot screen and just sits there showing the version numbers and nothing else. I have followed the instructions on the Wiki for downgrading but I still have the same problem. I have tried draining the battery fully and recharging but still no dice. I am even able to reflash the device with my laptop and it says it succeeds with the up/downgrade but then it just gets stuck again. If I try to install a 1.40 the device says that the flash is successful but then WM5 tries to boot again and I am stuck at the striped screen.
Can someone please help me out? Do I have a brick?

Stuck in Bootloader screen

Hello all,
as the title says, one of my touch diamond's is stuck in bootloader screen.
I didnt do anything in between it working and not working, it was on my desk, put it there working, got it 5mins later, and it was in bootloader screen (tricolor screen).
What i've already done to try and fix it:
flash it with the original HTC rom, flash completes succesfully, phone reboots to tricolor screen, so no solution there.
install mtty and format the phone, this completes, reboot the phone, again goes to the bootloader.
reflash the phone with original rom after cleaning it with mtty, flash again completes succesfully but when it reboots after flashing it just goes to bootloader again.
Tried to flash a Hardspl: stuck at 0% and stays there. so that doesnt work.
BUT! when in mtty i give the "boot" command, it DOES start to boot WM. but then again, when i turn the phone of, and on again, or it reboots because of first start after flash, it goes to bootloader again. The VOLDOWN button is NOT stuck, cause when it boots i can use the vol buttons perfectly fine.
Anyone got an suggestion in how to unbrick it? i have a second, perfectly working diamond here too, if that helps in any way.
Some more info ive just seen in mtty, when i told it to boot, it said ONE BAD BLOCK IN CE, remove block ---- to ---- (dont know the exact numbers anymore)
hi..i had something like that...
just download this.
"RUU_Signed_1_93OliNex_HSPL_UnsignedEdition"
it's only 1.7MB and it's will make it work.. atleast it did the job for me...
Hi,
My T mobile touch diamond stuck in bootloader screen? Any experties to help me please.
Thanks in advance.

[Q] Cant get into recovery, Logo graphical error on boot

Hey guys, I'm having trouble with my nexus device, I was watching youtube on it and it froze and now doesnt boot. I can access hboot, but recovery just shows the X logo and restart. I've tried reflashing boot.img, reflashing the recovery, reflashed stock hboot, flashed new roms from fastboot. I've also tried passimg.zip, and flashing a different radio but it stops 90% the way through, and it gets stuck in loading passdiag.zip if I use the volume down button to boot instead of the trackpad button.
The graphic abnormality is like an artifacting. If you search youtube its called "Nexus one stuck on X, can't boot to recovery.", I cant however post a link.
Anyone encountered this before? Any insight is appreciated.
well I've managed to remove blackrose at least, and to get to the blackrose menu. You have to access it from command prompt with "blackrose.exe skip" while in fastboot. Though I'd put it here incase it helps someone else in a similar circumstance.

Hard bricked Wiko Rainbow

Hello,
First of all, sorry for my english as it is not my mother language
I've tried today flashing CM13 on my Wiko Rainbow, but I either failed following the instructions or the files I had were corrupted, leading to a never-ending boot.
I don't know if it was already a soft-brick back then, as the phone turned off while booting just after the installation, but 40min after it (obviously because of en empty battery, which was at 37% before installation)
At first, when the phone was plugged into the computer, the phone was booting up, showing the charging icon for a few seconds, and then was going into the infinite boot for 10 seconds, and then rebooting for the same process.
When I was charging the phone on a wall plug, the phone was just in an infinite loop.
The problem was that, when I did the Volume down + Volume up + power thing, I had a choice between Factory mode and Custom mode, but both of them led me to a black screen, and the phone powered off.
I then searched how to install a custom recovery with a soft-bricked phone, and I got a tutorial on SP Flash Tool, that told me to use a MT6582 scatter file, and to select only a Recovery. I downloaded a TWRP for my phone, and then started download, retracted the battery and plugged the phone on the computer.
I got this message : "brom error s_fthnd_file_is_not_loaded_yet"
The software told me to format the Flash, which I did, and this error now became this : "BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)"
The thing is that now, the soft brick is now a hard brick, and I can't get the phone to boot anymore, adb doesn't recognize my device, and after installing and reinstalling my phone drivers, no solution came out yet, so I'm hopping that you'll find a solution to help my problem
Thanks.
Regards.
MichelFou said:
Hello,
First of all, sorry for my english as it is not my mother language
I've tried today flashing CM13 on my Wiko Rainbow, but I either failed following the instructions or the files I had were corrupted, leading to a never-ending boot.
I don't know if it was already a soft-brick back then, as the phone turned off while booting just after the installation, but 40min after it (obviously because of en empty battery, which was at 37% before installation)
At first, when the phone was plugged into the computer, the phone was booting up, showing the charging icon for a few seconds, and then was going into the infinite boot for 10 seconds, and then rebooting for the same process.
When I was charging the phone on a wall plug, the phone was just in an infinite loop.
The problem was that, when I did the Volume down + Volume up + power thing, I had a choice between Factory mode and Custom mode, but both of them led me to a black screen, and the phone powered off.
I then searched how to install a custom recovery with a soft-bricked phone, and I got a tutorial on SP Flash Tool, that told me to use a MT6582 scatter file, and to select only a Recovery. I downloaded a TWRP for my phone, and then started download, retracted the battery and plugged the phone on the computer.
I got this message : "brom error s_fthnd_file_is_not_loaded_yet"
The software told me to format the Flash, which I did, and this error now became this : "BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)"
The thing is that now, the soft brick is now a hard brick, and I can't get the phone to boot anymore, adb doesn't recognize my device, and after installing and reinstalling my phone drivers, no solution came out yet, so I'm hopping that you'll find a solution to help my problem
Thanks.
Regards.
Click to expand...
Click to collapse
You're going to need the firmware (not just TWRP) to fix your phone. Have you been able to download it?
Hovatek said:
You're going to need the firmware (not just TWRP) to fix your phone. Have you been able to download it?
Click to expand...
Click to collapse
using SP Tool gives directly through the USB

Phone memory seems to be read only

As I said in the title. The phone's memory seems to be read only.
I can access the fastboot mode of the phone and issue commands like flashing the recovery but it doesn't seem to update anything on the phone even though I get the "OKAY" message.
My phone is unlocked and until last night I was running CyanogenMod on it just fine. But now I can't flash a new recovery or access it. I have TWRP installed but everytime I try to boot into recovery the phone gets stuck on the logo screen and flashes every couple of seconds.
If I try to start my phone normally I get the cyanogenmod logo on start up (even after flashing stock) and the phone never actually boots up.
Anyone had the same problem before? If you need more details I'll reply ASAP.
My phone is the retail European XT1068 Dual Sim. Thank you in advance for any help.
Same issue here (I'm MrPowerGamerBR on Reddit), the more I read about trying to fix this issue, the more I start thinking "this phone is dead, move on..."
There isn't no fix for this, the only way to fix is replacing the logic board.

Categories

Resources