Database Develop

Bricked? Can't get out of bootloader & "not allow" problem

I dug too greedily and too deep, and now I'm afraid my phone is bricked. Any help would mean the world to me!
Summarized: phone will only boot into bootloader, and not further. Installing images does not work because of a "not allow" error message.
Current device situation
Works: boot into bootloader with camera/power, boot into standard google recovery with home/power
Does not work: Boot to full OS. Powering the phone just starts the bootloader. Fastboot/ADB
Device info:
Dutch T-Mobile G1, 1.5 years old.
Bootloader screen:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-5
RADIO-1.22.12.29
Sep 2 2008
Serial0
Installed ROM
No clue! See below.
What I did before the brick
I had a fully working, rooted, installation of OpenEclair 1.2.0.1. SPL (forgot, by this time, which one), newest radio, Cyanogen's recovery, and all that.
OpenEclair started refusing to boot after batteries had been drained once. Needing phone immediately, I hastily installed dream_devphone_userdebug-ota-14721.zip from my SD.
Noticed that phone was not rooted anymore. Fatal mistake.
Wanted to re-root. So, followed (to the letter) all steps under "Downgrade" on Cyanogen's Cyanogenmod full update guide for the g1/dream firmware. I.e. tried to install RC7 via DREAIMG.nbh (rightly spelled)
Rebooted.
What then happened
G1 finished installing RC7, then I rebooted. On subsequent boots, it would directly go to the bootloader and not the OS. I think somehow the install corrupted.
What I've tried since the brick
Searching forums: Could not find situations similar to mine with any answers.
ADB/Fastboot: I've tried both of these. For ADB, it seems you need to be able to get into full Android mode, so that's a no. Fastboot does not seem to be enabled on this bootloader (no mention of it to be found, logically, since it's a stock bootloader). In windows, USB device is not recognized, throws an error and allows no installation of drivers.
Nandroid: Useless without working ADB/fastboot? I do have several backups of old working installs.
Images: Tried if re-downloaded RC7 or RC29 worked. No dice. Gives 0028022 "not allow"
Installing dream_devphone_userdebug-ota-14721.zip using the recovery mode. Gives no signature/verification filed errors.
Goldcard: Have no winphone, or access to one. Terminal emulator method does not work without working Android OS...
I'm at a loss what to try anymore. Help much appreciated!

Sigh .. your mistake was flashing an nbh in the firstplace..
The ota image is for the android dev phone and had root access over adb.. there are even guides as to how to reinstall a custom recovery from the ota.
Also its most likely that you had danger or another fastboot enabled spl that could have been used to get yourself out of any firmware issue.
However now you have a half installed stock T-Mobile system.. and will need to reflash a nbh.
This will either require a goldcard (see if you can get your Linux PC to read the sd cards cid, or find someone in your area to make one for you)
Or a Dutch T-Mobile rru/nbh not sure I've heard of such a thing in the wild.

ROM doesn't start, recovery fails, fastboot not recognized by PC

Today I tried to change ROM in my G1. With that I also wanted to change SPL and recovery. It was my first conact with flashing that phone. I flashed Samsung i7500 before, so I have some Android experience.
Recovery and SPL went OK. When I was flashing ROM, something has gone wrong, so I decided to restore nandroid backup I made before flashing new ROM. When I restored backup, system didn't load. It stops on "Android" text or on black screen. Recovery also got lost (I don't know how) - now I can see only picture with triangle and "!" sign.
First thought I have was to use fastboot to flash new recovery and have it working. But there is my problem - when I enter fastboot mode, PC doesn't see any new device. There is no difference in device manager when phone is connected or not. When I turn phone on normally (so system's stops loading on Android text), it's recognized by PC.
Have anybody had such problem? What should I do to restore recovery or flash working rom?

What ROM u trying to flash? Some ROMs need some base files. You can even install a new Recovry Image through Recovery Console. Thats what I did

OK, What SPL you have right now...
Once you flash new SPL, old nandroid might not work properly as the partition layout has been changed....
Let us know the SPL you have now, sometimes if the phone is not getting recognized..then you have some old driver installed, try to see if that's the issue...
ms93 said:
Today I tried to change ROM in my G1. With that I also wanted to change SPL and recovery. It was my first conact with flashing that phone. I flashed Samsung i7500 before, so I have some Android experience.
Recovery and SPL went OK. When I was flashing ROM, something has gone wrong, so I decided to restore nandroid backup I made before flashing new ROM. When I restored backup, system didn't load. It stops on "Android" text or on black screen. Recovery also got lost (I don't know how) - now I can see only picture with triangle and "!" sign.
First thought I have was to use fastboot to flash new recovery and have it working. But there is my problem - when I enter fastboot mode, PC doesn't see any new device. There is no difference in device manager when phone is connected or not. When I turn phone on normally (so system's stops loading on Android text), it's recognized by PC.
Have anybody had such problem? What should I do to restore recovery or flash working rom?
Click to expand...
Click to collapse

I have installed haykuro SPL as I remember right.
I tried to update SDK and its USB drivers, but no result.
I remember also, that "USB debugging" wasn't on - maybe that's why phone in fastboot isn't recognized on PC?
To be clear: when I plug USB cable in fastboot mode, PC doesn't show that there is some new device. It acts like no device was connected to it.

There are other new and safe method to achieve the same or more then what you are trying to achieve with Haykuro SPL...see here..Custom MTD
But anyhow you are stuck with it...when you say Phone is not getting recognized..try restarting the phone in fastboot mode while connected to PC...when you are pressing back button are you getting fastboot..
I am not a good person to suggest something on this...If I would have been in your place I would have flashed DREAMIMG.nbh file and would have started from start....but wait till somebody better will tell you how to recover the device....
ms93 said:
I have installed haykuro SPL as I remember right.
I tried to update SDK and its USB drivers, but no result.
I remember also, that "USB debugging" wasn't on - maybe that's why phone in fastboot isn't recognized on PC?
To be clear: when I plug USB cable in fastboot mode, PC doesn't show that there is some new device. It acts like no device was connected to it.
Click to expand...
Click to collapse

G1sanju, I don't know what to say!
You saved my phone
Flashing DREAMIMG.nbh helped, phone has booted

OK, I have a new problem now.
Recovery is still not working - I have Android 1.0 in phone.
Fastboot is still not recognized by PC, so I can't flash it. I don't have root, so I can't flash recovery by terminal - is there any Android 1.0 root instruction?
Or maybe DREAIMG.nbh of 1.5 or 1.6 ROM?
EDIT:
Now everything works, I flashed recovery using telnet.

DREAMIMG.nbh is an default image for G1, so it remove root access and leave the phone with the stock image...now you have 1.x radio and stock SPL...flashing haykuro SPL right now can brick your phone....
unlocker.com has some good guide to get the root access if you are looking for it....
Do not flash the Haykuro SPL or DangerSPL......That's of no use now....also there are chances that it can brick your phone....
Use Safe SPL...1.33.2003 those are full engineering SPL with fastboot access....
use CustomMTD to get the increase size as mentioned in my post above...
ms93 said:
OK, I have a new problem now.
Recovery is still not working - I have Android 1.0 in phone.
Fastboot is still not recognized by PC, so I can't flash it. I don't have root, so I can't flash recovery by terminal - is there any Android 1.0 root instruction?
Or maybe DREAIMG.nbh of 1.5 or 1.6 ROM?
EDIT:
Now everything works, I flashed recovery using telnet.
Click to expand...
Click to collapse

I installed recovery via telnet, then changed radio, installed CustomMTD and ROM. All working fine.

Its great that you have used customMTD rather then Haykuro SPL...this is safe method....I just warned you because that's a very common way to brick the phone....flashing NBH and then installing SPL assuming you have the correct radio is a very common way of bricking the phone...
Also if you are playing with SPL and radio's then its advisable to erase the recovery first...then do the install from fastboot and then reinstall recovery...
ms93 said:
I installed recovery via telnet, then changed radio, installed CustomMTD and ROM. All working fine.
Click to expand...
Click to collapse

[SOLVED] Touch HD is dead???

Hi all!
first of all sorry for my Egnlish
I tried to perform task29 on my HD and get an error "Invalid vender ID", in some guides i read that in this case I should use a stock .nbh files... I tried the .hbn file from HSPL thread from one of restore_stock_spl* zip files. task29 was performed normally. When I turn on device I can see the clear smart mobility screen only with "smart mobility" words in center. bootloader now showing me 1.54 Olinex version. Before task29 this version was 1.56.
And from this moment I can't do anything with device: I can't flash any rom or radio. When using RUU after three-colour screen device shows me a progres indicator which suspends on 0% and RUU progress is also 0%. after waiting some time RUU shows an "262 Update erorr". When I'm trying to flash ROM or radio from SD card I see the three-colour screen then grey screen "loading... No image file!!!" and then again the three-colour screen. It shows so fast that it looks like a screen blinking and almost impossible to read what is written on grey screen.
I have spend 3 days while looking for different files and flash packages, have read a guides and I'm at a loss.
Please helpme to make my HD work again!

sergey.ss said:
Hi all!
first of all sorry for my Egnlish
I tried to perform task29 on my HD and get an error "Invalid vender ID", in some guides i read that in this case I should use a stock .nbh files... I tried the .hbn file from HSPL thread from one of restore_stock_spl* zip files. task29 was performed normally. When I turn on device I can see the clear smart mobility screen only with "smart mobility" words in center. bootloader now showing me 1.54 Olinex version. Before task29 this version was 1.56.
And from this moment I can't do anything with device: I can't flash any rom or radio. When using RUU after three-colour screen device shows me a progres indicator which suspends on 0% and RUU progress is also 0%. after waiting some time RUU shows an "262 Update erorr". When I'm trying to flash ROM or radio from SD card I see the three-colour screen then grey screen "loading... No image file!!!" and then again the three-colour screen. It shows so fast that it looks like a screen blinking and almost impossible to read what is written on grey screen.
I have spend 3 days while looking for different files and flash packages, have read a guides and I'm at a loss.
Please helpme to make my HD work again!
Click to expand...
Click to collapse
Have you tried flashing stock rom which came with your device?

I have tried .nbh file from "HTC Stock ROM_BLACKSTONE_1.14.401.3 (22273) WWE.zip"
if it possible tell me what exactly should I download and how to use it, I'll try. I'll try everything you advise, because I didn't find solution myself and don't know what esle should I try. first of all where should I start? do I need to perform task29 correctly or do I need to restore HSPL to 1.56 version, or flash a stock rom?

* Dont connect your phone to your computer.
* Hold down the Volume down button and hit the power button.
* Your entering the tricolor boot screen and at the bottom the word "Serial".
* Now connect you phone to your computer with te USB cable the word serial disappear and now it says USB.
* Now you can normally flash/update your phone and please use hspl.

I had before a HTC Diamond. On that device I used to run "task29" until that command killed my device. Almost same as you, I could flash the device but I couldn't boot normally. My ROM memory probably got damaged for good so I had to replace the device with a new one. My suggestion to you: on a new device never use that command again and you will be fine.

iamjohno said:
* Dont connect your phone to your computer.
* Hold down the Volume down button and hit the power button.
* Your entering the tricolor boot screen and at the bottom the word "Serial".
* Now connect you phone to your computer with te USB cable the word serial disappear and now it says USB.
* Now you can normally flash/update your phone and please use hspl.
Click to expand...
Click to collapse
I tried this way. Progress is suspends on 0% and then I get an error "262 Update Error" in RUU What should I do first: change HSPL version or flash ROM/radio?
xdmcdmc said:
I had before a HTC Diamond. On that device I used to run "task29" until that command killed my device. Almost same as you, I could flash the device but I couldn't boot normally. My ROM memory probably got damaged for good so I had to replace the device with a new one. My suggestion to you: on a new device never use that command again and you will be fine.
Click to expand...
Click to collapse
it's terrible, hope my devise still alive...
There is one detail I didn't mentioned... If download task29 package and just simply execute task29.exe (using .nbh from this package) progress on device goes forward to 4% and then "Invalid vender ID" error occurs... So I think I should use another .nbh file but which one?. Hope this checking of vender ID is not that 4% of progress and some actions with device memory really starts...

sergey.ss said:
I tried this way. Progress is suspends on 0% and then I get an error "262 Update Error" in RUU What should I do first: change HSPL version or flash ROM/radio?
it's terrible, hope my devise still alive...
There is one detail I didn't mentioned... If download task29 package and just simply execute task29.exe (using .nbh from this package) progress on device goes forward to 4% and then "Invalid vender ID" error occurs... So I think I should use another .nbh file but which one?. Hope this checking of vender ID is not that 4% of progress and some actions with device memory really starts...
Click to expand...
Click to collapse
Try using a radio nbh for blackstone.
The original package, contains nbh for the LEO

thanks all of you for replay but I still need a help very much.
there are ways that I have tried
1. flashing rom/radio from SD card
2. flashing rom/radio using RUU
3. task29 using different .nbh files
4. install/restore HSPL
In the first way always hapens same thig: I turn off the device, turn it on, press volume down button, see tricolor bootloader screen, then for a very short time (less than second) i see a grey screen and there is written: "loading... No image file!!!", then i see tricolor bootloader again.
I tried different rom/radio files (it was "HTC Stock ROM_BLACKSTONE_1.14.401.3 (22273) WWE" and other roms I flashed before and different versions of radio files from thread int this forum).
for the RUU using ways I always get two situations: I turn off the device, turn it on, press volume down button, see tricolor bootloader screen, connect the devise to PC, execute RUU/taks29/HSPL/Restore_SPL, then press next a few times, then i see the progress in RUU and on device screen and there is two endings:
1. progress goes up to 4% and devise making a soft reset, load the black smart mobility screen with no orange version characters on screen bottom, RUU shows "Invalid vender ID";
2. progress suspends on 0% and after some timeout RUU shows "Error [262] Update error" and now changes on device screen.
last what I have tried: execute task29 with last hd radio 1.17.25.09 file and got invalid vendor id error, then execute task29 with radio 1.09.25.14 file and got update error.
my be this holds some information: in my bootloader is written following
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
what should I do?

sergey.ss said:
thanks all of you for replay but I still need a help very much.
there are ways that I have tried
1. flashing rom/radio from SD card
2. flashing rom/radio using RUU
3. task29 using different .nbh files
4. install/restore HSPL
In the first way always hapens same thig: I turn off the device, turn it on, press volume down button, see tricolor bootloader screen, then for a very short time (less than second) i see a grey screen and there is written: "loading... No image file!!!", then i see tricolor bootloader again.
I tried different rom/radio files (it was "HTC Stock ROM_BLACKSTONE_1.14.401.3 (22273) WWE" and other roms I flashed before and different versions of radio files from thread int this forum).
for the RUU using ways I always get two situations: I turn off the device, turn it on, press volume down button, see tricolor bootloader screen, connect the devise to PC, execute RUU/taks29/HSPL/Restore_SPL, then press next a few times, then i see the progress in RUU and on device screen and there is two endings:
1. progress goes up to 4% and devise making a soft reset, load the black smart mobility screen with no orange version characters on screen bottom, RUU shows "Invalid vender ID";
2. progress suspends on 0% and after some timeout RUU shows "Error [262] Update error" and now changes on device screen.
last what I have tried: execute task29 with last hd radio 1.17.25.09 file and got invalid vendor id error, then execute task29 with radio 1.09.25.14 file and got update error.
my be this holds some information: in my bootloader is written following
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
what should I do?
Click to expand...
Click to collapse
Hmmm... I want to know, what .nbh file did you include in the task29 folder you have? Remember, you must to copy a radio ROM to your task29 folder and name it as RUU_signed.nbh, don't copy an OS ROM to task29 as this will give problem.
From the information above, seems you had restore to original SPL? Try flash HSPL or USPL. If you have any problem flashing, you can ask in this thread http://forum.xda-developers.com/showthread.php?t=505377
Good luck, my friend. Cheers.

Agree with philrom: you are an the stock SPL. So, flash HSPL, then you should be fine.

Has this been resolved?

Fallen Spartan said:
Has this been resolved?
Click to expand...
Click to collapse
Yes. Sorry I forgot to post the ending of this story...
I didn't understood about flashing HSPL in formated device... I was really tired of using different ways and flashing different roms... I just took my device to a not official service center (there is no Touch HD for my country). There guys said me that I need to flash a stock rom of my HD birthplace country. They found out that it was shipped from Arab Emirates, than they found a required ROM and flash it. It cost me 50$. Now I'm using my HD as usual.
Thank for the replays!!!

Glad you got it resolved
Thread closed

[Q] Help Required regarding installing new ROM !!!

I am having Xperia X1 Black with factory installed Win Mo 6.1....so, now i wanted to try the Windows Mobile 6.5.3-Build- 29007. Can anyone help me with detailed procedure of installing new ROM on my X1.
I tried according to the procedure available in various post's. According to the procedure i need to first Hard SPL my phone. So, when i try doing that my progrees bar on the phone screen gets stuck at 0% and then i get a error that check the connection of the pc and phone.
In bootloader mode the configuration shown is as follows
KOVS110
SPL-0.78.0000
Micro P1-787
Micro P2-707
I even tried the direct SD card method in which i renamed the ROM file i.e RUU_signed.nbh to kovsimg.nbh...in this when i go to the bootloader mode, the tricolour screen shows with above mentioned specifications then after about few seconds another screen is displayed saying" LOADING..." and then gets stuck.
So, anybody can please help me with installing new ROM
Regards
Bhavik

guitarguru31 said:
I am having Xperia X1 Black with factory installed Win Mo 6.1....so, now i wanted to try the Windows Mobile 6.5.3-Build- 29007. Can anyone help me with detailed procedure of installing new ROM on my X1.
I tried according to the procedure available in various post's. According to the procedure i need to first Hard SPL my phone. So, when i try doing that my progrees bar on the phone screen gets stuck at 0% and then i get a error that check the connection of the pc and phone.
In bootloader mode the configuration shown is as follows
KOVS110
SPL-0.78.0000
Micro P1-787
Micro P2-707
I even tried the direct SD card method in which i renamed the ROM file i.e RUU_signed.nbh to kovsimg.nbh...in this when i go to the bootloader mode, the tricolour screen shows with above mentioned specifications then after about few seconds another screen is displayed saying" LOADING..." and then gets stuck.
So, anybody can please help me with installing new ROM
Regards
Bhavik
Click to expand...
Click to collapse
You bootloader should show
Kovs110
SPL-0.78.OliNex
MicroP1-787
MicroP2-707
don't know if .0000 and OliNex is different
http://forum.xda-developers.com/showthread.php?t=431218
look here for download the good Hard SPL and then replace the 0.78 in it, HARD SPL with cable / computer (I never use SD CARD because it never works for me)
then you TASK29 (find it in the forum), then you can flash it =)

CUSTOM ROM error

Device: HTC HD7 T9292
MID PD29100
SPL-1.57.2250.0
SD SANDISK 7580MB Class0
Total storage: 7.20GB
Available Storage: 6.80GB
OS Version: 7.0.7004.0
Firmware revision number: 2250.09.15702.728
Hardware revision number: 0002
Radio software version: 5.71.09.02a_22.51.50.21U
Radio hardware version: A.102.0.D4
Bootloader version: 1.57.2250.0(113571)
Chip SOC version: 2.2.5.0
Please help, i tried to install custom ROM due to some errors i experienced (constant need for HARD RESET due to white HTC logon screen bug; (stuck on bootloader htc screen)). I downloaded the first file DFT_RSPL_WP7FG1_LAUNCH" (also tried revision #3) but it won't change to RSPL...(there were no error messages..it say like it is all done, but it remain spl.) I chose spl 1.56 from list, there weren't 1.57. Therefore i couldn't install HSPL aswell.
Then i tried to install just RUU_Schubert_HTC_Europe_5.10.401.04_SLSPL_Signed_by_ansar". It installed to 100%.. and then says "Invalid image" File is courpted. When i started the phone menu was different a bit. I see some new icons..SingTel IDEAS; SingTel Xplorer; etc..
I should probably point out that i done all this without SIM card inside.
And i had problems with phone in past...it fall a couple of times...my camera is not responding from menu..and i had a "STORAGE CARD NOT WORKING" message.... I don't know is that has to do something with this...but it is better to tell all the informations.
Thanks for the time, any hint would be appriciated.
Thanks,
Nebojsa

nshA said:
Device: HTC HD7 7.5
MID PD29100
SPL-1.57.2250.0
SD SANDISK 7580MB Class0
Please help, i tried to install custom ROM due to some errors i experienced (constant need for HARD RESET due to white HTC logon screen bug; (stuck on bootloader htc screen)). I downloaded the first file DFT_RSPL_WP7FG1_LAUNCH" (also tried revision #3) but it won't change to RSPL...(there were no error messages..it say like it is all done, but it remain spl.) I chose spl 1.56 from list, there weren't 1.57. Therefore i couldn't install HSPL aswell.
Then i tried to install just RUU_Schubert_HTC_Europe_5.10.401.04_SLSPL_Signed_by_ansar". It installed to 100%.. and then says "Invalid image" File is courpted. When i started the phone menu was different a bit.
I should probably point out that i done all this without SIM card inside.
And i had problems with phone in past...it fall a couple of times...my camera is not responding from menu..and i had a "STORAGE CARD NOT WORKING" message.... I don't know is that has to do something with this...but it is better to tell all the informations.
P.S. I would give you more information about the phone, but it seems i messed it preety well with this Custom ROM thing..it won't start anymore; i can't go to settings>about" . It shows only (power on + volume down) screen.
Thanks for the time, any hint would be appriciated.
Thanks,
Nebojsa
Click to expand...
Click to collapse
Your device is bricked.
You might be able to save it if you can still get into USB host mode - Device off, hold down the volume down button and camera button together and power on the device, keep holding down the volume down and camera button until you see a screen with a phone and a laptop.
If you can get into USB host mode then you can try and flash the device using the goldcard/ Y cable method. You have to flash a stock/shipped rom that is specific to your device carrier with the Y cable.
Just follow the tutorial here:
http://forum.xda-developers.com/showthread.php?t=1597837

xdrc45 said:
Your device is bricked.
You might be able to save it if you can still get into USB host mode - Device off, hold down the volume down button and camera button together and power on the device, keep holding down the volume down and camera button until you see a screen with a phone and a laptop.
If you can get into USB host mode then you can try and flash the device using the goldcard/ Y cable method. You have to flash a stock/shipped rom that is specific to your device carrier with the Y cable.
Just follow the tutorial here:
http://forum.xda-developers.com/showthread.php?t=1597837
Click to expand...
Click to collapse
Thank you.. I will try that too. I edited my previous post. The phone start to work normally. I still can't access my camera, and i will try to replace Storage Card manually. I have a bit different menu now...so i assume Custom ROM install was successful. I'm doing all this to repair my "HTC white boot screen stuck problem". That ussally accure when battery reach low levels, so maybe it is battery problem aswell.
I will see if it will happen again when new ROM is installed.
Thank you for your time and help.
Regards, Nebojsa