Database Users

Can't access bootloader

I have a T-Mobile US XDA. I am not able to access the bootloader (power + soft reset). I cannot flash the bootloader or a new ROM via SD Card method. I have tried bootloader fix as well, it gives an error saying protection found.
Can anyone suggest/help me fixing this problem?

When I run Fix broken bootloader from Windows XP & I saw the below error message from DOS command prompt:
=============================================
C:\Program Files\XDAtools\binaries>pnewbootloader.exe bootloader_v5_15.nb0
Unable to find flash info offset, cannot disable bootloader writeprotect
=============================================
help please

G1 won't start the system

i wanted to upgrade my android G1 to android 1.5, i have downloaded the boot.img + recovery.img+radio.img
i have started by these :
HTML:
fastboot erase system
fastboot erase boot
after that when i tried to type on the prompt :
HTML:
fastboot flash system system.img
it says that there's no signature & verification failed. Installation aborted
and now my phone when i power it, it stops in the starter screen image.
what could i do to re-install my phone with fastboot command ? and what have i do to eliminate the verification of signature ?

sorry to hear dat mate. try flashing software but read all instructions b4 do dat

thanks, but the problem is how, because my first aim -i think- is to unblock the bootloader whitch is responsable of the message no signature found.
any one can help me ?

is there a method that allow me to install new system G1 without it verifies the signature ?

Stuck in RUU, 32A S-ON on 1.76.0007 with higher bootloader version

I installed the Rogers Magic+ upgrade on my HTC Magic, then tried to use a much older RUU to restore my phone to original condition.
The downgrade failed (I don't recall what the error was unfortunately), but now I'm stuck with RUU recognizing my bootloader version as 3.54, and the perfected, SH-ON 0007 RUU.
Obviously I can't get into recovery, or access the Android OS.
Is there anything I can try? I've been working on this for a couple of weeks, and are starting to think it's a confirmed brick.

Just flash the same ruu once again(with the same version nr)... then you should be on stock os!
From there you can root -> flash custom recovery -> enjoy yourself :0)

When I try this I get "ERROR[132]: SIGNARURE ERROR" (spelling error as quoted). I've read about trying the RUU on XP if this happens, that still did the same

Try to get into fastboot mode.
Then type this:
Code:
fastboot oem rebootRUU
Then try to run the RUU again...

It reboots back into RUU with the feedback "...OKAY", but the RUU still gives the same error message (ERROR[132]: SIGNARURE ERROR)

USDan said:
It reboots back into RUU with the feedback "...OKAY", but the RUU still gives the same error message (ERROR[132]: SIGNARURE ERROR)
Click to expand...
Click to collapse
Nothing u can do,unless the hight version RUU.My magic was stucked like this.
At last I use JTAG to repair it.

[Q] Need me some sbf files

Hey! Sorry if this question has been asked a ton of times, but I need the bootloader sbf for the Droid 2. I currently have D2.37 on there, but after doing an sbf for a reset, RSD Lite 5.5 would say "Failed flashing process. Failed flashing process. INterface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x196000 Command: ADDR (0xE023203F); phone connected". If I tried to boot the phone, it would say "Code Corrupt". Any searching I've done says that I need to reflash the bootloader. I've been trying to find it, but any mirrors of it are down, such as the ones located here: http://and-developers.com/sbf:droid2
So I must ask, does anyone have the sbf files I need?

flash modem_a error

I have been trying to fix my device it is stuck on boot screen. I tried to flash stock rom using miflash tool but it gives this error. There are no white spaces in path of the file but still gives me this error.

Have you unlocked the bootloader?