Database Users

I think I bricked.. cannot get to bootloader or recovery mode

Any ideas?
I tried to flash a new SPL.. probably a stupid idea on my part, and it loops at the G1 screen.
I was going to install the SPL, then install SuperHero v2
I press power+home to go to recovery, and it does nothing. I try to access bootloader, and it does nothing.
Is it officially bricked?

is the phone plugged in when you are trying to do this?
if not, then try reflashing your rom.

mrcrs said:
is the phone plugged in when you are trying to do this?
if not, then try reflashing your rom.
Click to expand...
Click to collapse
Well I can't boot into recovery mode =/
So I can't reflash a rom
It just stays at the G1 screen

Did you verify if you had a pvt board or not?

can you get into bootloader mode?

I did verify, and it had a compatible board. I believe it was PVT, but atm I'm pretty pissed that I can't remember. I just know for fact it was compatible, otherwise I wouldn't of even thought of going through the process.
To recap:
I cannot get into bootloader.
I cannot get into recovery mode.
It stalls on the G1 screen. It apparently is stuck in a loop.
I can get to the blue LED thing though. (Which apparently is worthless)

This is lame. (I'm an idiot)
Unless some miracle can happen, which I am very much hoping, I am going to declare it bricked.
Which means I'll have to either use my lame iPhone, or ditch out $200 for a new G1.

okay i'm sure you did this already but i gotta ask, did you try removing the battery for a few seconds then try booting into recovery?

Sooooooo....
You had a compatible board, but did you think to update to the latest Radio....?
If you didn't have the latest radio then that's what bricked your phone..
If you did then your phone shouldn't be bricked......
Did you have the latest Radio?

mrcrs said:
okay i'm sure you did this already but i gotta ask, did you try removing the battery for a few seconds then try booting into recovery?
Click to expand...
Click to collapse
Yeah, and no avail
I think I'll just remove the battery for the rest of the day, and pray that somehow it'll fix. lol

imnothimm said:
You had a compatible board, but did you think to update to the latest Radio....?
If you didn't have the latest radio then that's what bricked your phone..
If you did then your phone shouldn't be bricked......
Did you have the latest Radio?
Click to expand...
Click to collapse
Ah!
Found the culprit. You see, there aren't any guides that I could find that properly told me which order to do it, and how.
I thought it was SPL, then Radio, then ROM. But it's actually Radio, SPL, then ROM.
Well then I do have a brick. My first brick, woo.

Yup
Your Phone is indeed bricked...
HTC will repair it for 150...
Sounds like your only option

so if it was the saphirre or H's special spl you tried to flash but didn't upgrade the radio, then yeah... you most likely got a brick.
but what makes me wonder is that when i flashed H's special spl, i ran into the constant relooping of the g1 splash but i was still able to get into recovery mode. so i just reflashed my rom, and all was gravy.

They really will? Because $150 is $50 cheaper than I can get a new G1 (from craigslist)
But, if it's still a new phone, does it come with a 1year warranty from T-Mobile?
I know on my AT&T Tilt, at one point I messed it up, and they have a Warranty store locally, and I took it in and they tried to fix it but they couldn't, so they replaced it. Does T-Mobile have one of these anywhere?

hmmm
I sent mine into T-mobile and they replaced it for free, although I'm about 98%sure you need to have an account with T-Mobile for them to do that...
I'm pretty sure HTC is your best bet atm

Though I do have a t-mobile account. My mom and dad are with t-mobile, and I am with at&t.

if you are with tmo, then just call them.

Alright well I'll give them a call.
Maybe they will be nice

Well this sucks lol.
T-Mobile wont replace the phone because it's not purchased by me. It was purchased by someone locally on craigslist. So I would have to get in contact with that person and have them get me an exchange.
Yet another reason why I dislike T-Mobile. AT&T will just verify the IEMI, and if it shows that it's less than a year, or still under warranty, they will replace it.

I guess there's no failsafe way of fixing the G1, even after you messed up the first way to fix it?
I know in GPS navigators and stuff like that have their own failsafe mode to fix a brick. Then will force itself to connect to a computer so you can edit the whole filesystem.
Or a way to replace the system.. aka JTAG.
Recovery mode has to be accessed after a bootup. How stupid

How to intentionally brick your G1?

Here's my problem:
1) I had rooted my phone in the past.
2) I need to do a warranty return for a bad touchscreen and keyboard
3) I'm unable to flash back to stock because the home key is "stuck", so I can
only boot into recovery mode.
Is it possible to brick the phone so that it get stuck at the T-mobile loading screen before it default boots to the recovery screen?
If so, what is the most reliable way to brick my phone when all I have access to is the recovery mode?

fastboot flash a corrupt boot.img.

coolbho3000 said:
fastboot flash a corrupt boot.img.
Click to expand...
Click to collapse
That would be my first choice as well... except that I can only get to recovery mode, even when I hold down the camera button.
Closest thing I can do is flash an update.zip

my touch screen died today thank god for a trackball lol

g1junky said:
my touch screen died today thank god for a trackball lol
Click to expand...
Click to collapse
That's what I was thinking... I figure I'd just use my phone as-is until the replacement arrived, then I'd flash it back to stock before returning it...
If it's just a bad touch screen, they'll replace it without much fuss for next to free (just $10 shipping). Which is a very fair deal... unless you rooted your phone (boo!).
Then the home key got "stuck"... what bad luck... It's obvious when you turn it on that it's been rooted because of the custom recovery image... I'd rather make it a bit harder for them to determine my warranty's void instead of just having to turn it on.
@coolbho3000: I noticed that a boot.img file is included in some random update.zip (JFv1.3_RC8.zip) I just downloaded... Any idea what to hexedit on it to ensure it'll brick if I do an update through recovery mode? Or should I just pull the battery during the update (many times if need be)?
Update: I tried randomly screwing with the boot.img file using notepad++, but the damn phone won't use it for the update because the digest failed during the verification process. I also pulled the battery out during the part when it says it's writing the boot.img file (twice) without success -- although in this case, 'success' would be a bricked phone.
Why is this phone so hard to brick? Others just look at their g1 and can brick it...

I managed to brick my phone! It was harder than I thought (well, considering my many failed attempts), but here's how I did it:
I downloaded haykuro's 1.33.2005 special spl, renamed it to update.zip, and updated the g1 with it through the recovery panel. It's now permanently stuck at the T-mobile G1 screen. Worked for me, YMMV.
If that didn't work, my next two ideas were:
1) Very powerful magnet... high power speakers, or something else that puts out a lot of EM radiation (I'm sure I'd think of something). These things must have a low tempest rating.
2) Microwave (but that smells like desperation)
Hope this helps others in the same boat. I'll update with the bad news if they do, in fact, figure out I had rooted my phone anyways. I'm sure it's possible, yet probably unlikely. Otherwise, no news is good news.

Be glad you didnt have a custom spalsh image lol

Daemonjax said:
Here's my problem:
1) I had rooted my phone in the past.
2) I need to do a warranty return for a bad touchscreen and keyboard
3) I'm unable to flash back to stock because the home key is "stuck", so I can
only boot into recovery mode.
Is it possible to brick the phone so that it get stuck at the T-mobile loading screen before it default boots to the recovery screen?
If so, what is the most reliable way to brick my phone when all I have access to is the recovery mode?
Click to expand...
Click to collapse
Pretty simple. First do a recovery to factory settings using the camera and the start button. then copy the latest SPL from this website,
in the instructions it says that you have to flash the latest radio first, don't do that, just flash the SPL... reboot, voila, you have just successfully BRICKED ur phone..

Daemonjax said:
1) Very powerful magnet... high power speakers, or something else that puts out a lot of EM radiation (I'm sure I'd think of something). These things must have a low tempest rating.
2) Microwave (but that smells like desperation)
Click to expand...
Click to collapse
Magnets don't emit electromagnetic radiation -_-;;
A much easier way would just be to take a moderately high dc voltage (say ~48v) and fry part of the processor.

Daemonjax said:
I managed to brick my phone! It was harder than I thought (well, considering my many failed attempts), but here's how I did it:
I downloaded haykuro's 1.33.2005 special spl, renamed it to update.zip, and updated the g1 with it through the recovery panel. It's now permanently stuck at the T-mobile G1 screen. Worked for me, YMMV.
If that didn't work, my next two ideas were:
1) Very powerful magnet... high power speakers, or something else that puts out a lot of EM radiation (I'm sure I'd think of something). These things must have a low tempest rating.
2) Microwave (but that smells like desperation)
Hope this helps others in the same boat. I'll update with the bad news if they do, in fact, figure out I had rooted my phone anyways. I'm sure it's possible, yet probably unlikely. Otherwise, no news is good news.
Click to expand...
Click to collapse
You didn't have to hard brick it like that you know. There are other ways which will convince the warranty people just as well. Now it's really bricked.

hmmm well this was my idea....if my phone ever goes wrong or sumthing.... i will just crack the screen lol. so they cant see if what software was on my phone...

the easiest thing to do is flash the danger spl before flashing the radio if u havent flashed the Danger SPL already. If u did, just flash an older SPL. That should do the trick

nephron said:
the easiest thing to do is flash the danger spl before flashing the radio if u havent flashed the Danger SPL already. If u did, just flash an older SPL. That should do the trick
Click to expand...
Click to collapse
Or if you already have Haykuro's SPL just downgrade your radio hehehe

nephron said:
the easiest thing to do is flash the danger spl before flashing the radio if u havent flashed the Danger SPL already. If u did, just flash an older SPL. That should do the trick
Click to expand...
Click to collapse
So if you have the danger/haykuro spl and want to downgrade that spl for w/e reason the phone will brick??? or are you trying to tell him to downgrade the radio?

turboyo said:
So if you have the danger/haykuro spl and want to downgrade that spl for w/e reason the phone will brick??? or are you trying to tell him to downgrade the radio?
Click to expand...
Click to collapse
If you use Haykuro's "Danger SPL" and will try to downgrade the radio, it should brick the phone for good.

Even if your camera button is broken you can still get to fastboot through ADB. Just open an adb shell (doesn't matter if it is recovery or not) and type:
#restart bootloader
and voila - you can get into fastboot mode and flsh whatever you want.

brian_v3ntura said:
hmmm well this was my idea....if my phone ever goes wrong or sumthing.... i will just crack the screen lol. so they cant see if what software was on my phone...
Click to expand...
Click to collapse
thats dumb as hell cuz if u crack ur screen u have to pay $130 deductable well at least in USA and if u send it back with out telling them the screen cracked u get to pay $370 restocking fee but ifd u just brick with spl u get free replacement just pay shipping which im about to do cuz my phone was ****ing up and i got replacement sent(20 bucks shipping thats it) but magically i fixed the phone but its rooted and fully working again so if new phone is PVT board then im bricking my phone and keeping new one.

I need help
Hey people I have a cracked G1 screen and a rooted firmware, I want to get a free warranty replacement by saying that the "Update Failed" and act like a total idiot to the tmobile people..
I also have Haykuro's latest radio and latest SPL, can someone give me clear guaranteed instructions on how to brick my fine cracked friend?
Oh, and I also want to make sure that the TMOBILE people cant go to cyanogens 1.4 Recovery image after this thing is bricked, so AANNY help would be appreciatede

housecat93 said:
Hey people I have a cracked G1 screen and a rooted firmware, I want to get a free warranty replacement by saying that the "Update Failed" and act like a total idiot to the tmobile people..
I also have Haykuro's latest radio and latest SPL, can someone give me clear guaranteed instructions on how to brick my fine cracked friend?
Oh, and I also want to make sure that the TMOBILE people cant go to cyanogens 1.4 Recovery image after this thing is bricked, so AANNY help would be appreciatede
Click to expand...
Click to collapse
Grab the RC29 file, name it DREAIMG.nbh, and flash via the bootloader. Since that will downgrade the radio to the 1.1 version, you will no longer have the 1.5 radio that 1.33.2005 requires

This has got to be the funniest topic I've read in awhile.
Good luck to all you seeking bricked phones. Haha.

Is it truly bricked?

Ok so here's the problem...
I was able to root my Rogers Dream but then I messed up with trying to partition the sd card. It was then that it would not go past the rogers screen. After A LOT of reading I downloaded what I thought would the files I need to simply restore the phone to factory. Long story short, if I just turn the phone on it sits at the Rogers screen, I no longer have recovery mode and my fast boot goes to a RGBW screen with Serial0.
Also on the FastBoot screen it states:
DREA210 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.2.19.26I
I really just want to return the phone to the state it was before rooting it (store bought state). But because I can't access the fastboot through USB or even get to the Engineering SPL I'm really..really stuck!!
If I can get the proper FastBoot loaded somehow I think I can restore the rest.
Any help would be greatly appreciated.

no it is not bricked, try removing the sdcard

Still nothing.
Also if I press Home+Power or Camera+Power it still ends up at the same RGBW screen.

No, it isn't bricked
You are stuck at the stock SPL. I'm not sure about rogers but for tmobile you would want to put dreaimg.nbh on the root your SD card, load up the SPL. Flash dreaimg.nbh. Then it should boot into rc29 (I believe). Get root access, flash whatever flavor of recovery you want. Then boot into recovery and flash whatever SPL you want. Then you can get back into the SPL and restore whatever nandroid backup you had.
Again, this is what I would do on tmobile. Not sure about rogers, but I would assume since you would be loading your own backup everything will be peachy.

Ya I hear what you're saying. The problem is I can't seem to find an original Rogers DREAIMG.nbh file anywhere. I think I might be SOL and have to take into Rogers to get it fixed. I'm just not sure if I've voided the warranty or not.

I'm stuck at the exact same place - Rogers phone same, settings, screwed up somewhere along the way.
HTC told me (over the phone) that I can call Rogers and request service on my phone for them to flash it back to the original Rogers ROM because they're the carrier, but this would mean sending the device in..... Whether they'll do it or not, I do not know, but right now I'm trying to simply update to the engineering SPL and go from there. Stupid 0.95.0000 version is screwing everything up.
And I haven't been able to find any Rogers .NBH files ANYWHERE that would allow me to get back to factory settings. At this point, I'd be happy to know that I"m getting 3G and can install a custom ROM on my phone so that it'll at least work the way I want it to.

try here >>>>>> http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream/Magic32B_Firmware_to_CyanogenMod
dl the rc7 for europe and see if the fastboot recs it. if not try and find the system.img for rogers and ill tell you how to flash it via fastboot. if you had the system img it would already be good. no use of the nbh. also what is dif from dream and g1 besides apns and a small other few things?? if nothing then why not flash the g1 dreamimg?? once thats good then root and get it finalized? just wondering.
EDIT: I searched more for you. dont try my idea. im kinda dumb lol. i forgot that rogers and tmobile have dif boards. so this wont work and might brick you. so dont listen to me. sorry for missleading. im use to g1's in the usa sorry. ill keep searching for anything for you thou.
EDIT2: in fastboot can you >>>>> fastboot boot "name_of_your_recovery.img" ???
try that in fastboot to see if you can get into recovery. if you have no idea what i mean let me know so i can give some sdk instructions.

Unfortunately I can't because even though I can fastboot it won't allow me to connect to the laptop via usb. Basically the phone never gets to that point.

losingmyself said:
I'm stuck at the exact same place - Rogers phone same, settings, screwed up somewhere along the way.
HTC told me (over the phone) that I can call Rogers and request service on my phone for them to flash it back to the original Rogers ROM because they're the carrier, but this would mean sending the device in..... Whether they'll do it or not, I do not know, but right now I'm trying to simply update to the engineering SPL and go from there. Stupid 0.95.0000 version is screwing everything up.
And I haven't been able to find any Rogers .NBH files ANYWHERE that would allow me to get back to factory settings. At this point, I'd be happy to know that I"m getting 3G and can install a custom ROM on my phone so that it'll at least work the way I want it to.
Click to expand...
Click to collapse
I know! I can't believe out of every bit of information on how to root an Android phone there is basically nothing on how to fix it. At least for anyone using Rogers.

DO what I did, I had the same issue (T-mo) I used a micro Sd "converter" if you will...........and plugged it into my laptop's SD reader, copied the files over, and VIOLA!
I actually thought I bricked it 5 times.

TinBasher77 said:
Unfortunately I can't because even though I can fastboot it won't allow me to connect to the laptop via usb. Basically the phone never gets to that point.
Click to expand...
Click to collapse
I think you've misunderstood.. fastboot mode on the phone enables you to use the fastboot program on your pc to send commands. You can use it to boot a recovery image and flash the files you need to fix this. There's a sticky thread detailing how to set up and use fastboot in Q&A.

Does anyone...anyone at all know where I can get the official Rogers HTC dreaimg.nbh file? I have searched high and low and can't seem to find it anywhere. I'm pretty sure if I can get my hands on it I can fix the phone.
Thanks in advance.

TinBasher77 said:
Does anyone...anyone at all know where I can get the official Rogers HTC dreaimg.nbh file? I have searched high and low and can't seem to find it anywhere. I'm pretty sure if I can get my hands on it I can fix the phone.
Thanks in advance.
Click to expand...
Click to collapse
there is no rogers dreaimg.nbh

Hi,
How did you root your phone?
can you still boot into the recovery img? (home+power)
If you cant, try get back the recovery img (e.g. cm-recovery-1.4.img) and then home+power again. From there you should be able to update your spl to hardspl

Unfortunately I can't boot into fastboot any longer I just get the red/green/blue/white screen. This happens with both Home+Power or Camera+Power so I can't even use adb to force the images onto the phone.
Thanks for the help though.

Well problem solved (sort of).
I contacted Rogers and they're going to send me out a new phone and have me return the "defective" one.
Thanks for all your help and suggestions.

Stuck stuck STUCK in bootloader - help!

My problem here is that I just cannot get out of bootloader. NO ROM OR RADIO WILL INSTALL ON MY DEVICE.
I've tried using goldcard and attempting numerous .nbh files and each time the update fails on the Radio_V2 part. I've also tried updating with the standard and custom RUUs and these always fail at 91%. the RUU always says 'Error 270....update error...the image file is corrupted' no matter which ROM I use.
Updating the radio only stalls at 96% and gets stuck there.
Currently my bootloader says 'Update ROM code error Please try again. See the attached photo for a screenshot. I am able to connect to a pc ok and run updates.
Ive also tried a hard reset, which WORKS but still doesn't boot up the device.
Can anyone help here? If not it looks like my HD2 is going on eBay for spares!

My SPL is version 1.42
Why is yours 0.67????

I've no idea bro, it's an eBay purchase from before the general release of the device.

I hear the hacked hardspl and sspl is nearly done so maybe this will help you to upgrade the rom?
Have you checked you have not brought some prototype or something as your spl version is way out.
Hope you get it fixed very soon.

How can it show the "SECURITY UNLOCKED" while there is no cid unlock for this device?
How did you do it?
There is something wrong with you..
And an interesting point: your bootloader is different from mine, my updare process shows % progress in number and HTC logo behind the progress bar, yours is different..

ultraslan said:
How can it show the "SECURITY UNLOCKED" while there is no cid unlock for this device?
How did you do it?
There is something wrong with you..
And an interesting point: your bootloader is different from mine, my updare process shows % progress in number and HTC logo behind the progress bar, yours is different..
Click to expand...
Click to collapse
i think he as used some hd stuff,not compatible with leo of course

maybe because it's a pre-release (prototype) unit you can't update it to a newer rom

it does sound like a prototype...
shouldnt need gold card.
have you tried flashing from sdcard without gold card in there?
try talking nicely to cmonex to see if she can help?

hi
leoni1980 said:
My problem here is that I just cannot get out of bootloader. NO ROM OR RADIO WILL INSTALL ON MY DEVICE.
I've tried using goldcard and attempting numerous .nbh files and each time the update fails on the Radio_V2 part. I've also tried updating with the standard and custom RUUs and these always fail at 91%. the RUU always says 'Error 270....update error...the image file is corrupted' no matter which ROM I use.
Updating the radio only stalls at 96% and gets stuck there.
Currently my bootloader says 'Update ROM code error Please try again. See the attached photo for a screenshot. I am able to connect to a pc ok and run updates.
Ive also tried a hard reset, which WORKS but still doesn't boot up the device.
Can anyone help here? If not it looks like my HD2 is going on eBay for spares!
Click to expand...
Click to collapse
This looks like corrupted sectors in your device, try mtty, I think i seen similar problem before in herm or diamond
please searh the forum this one of them but try to find later version of mtty
http://forum.xda-developers.com/showthread.php?t=304408

try flashing without NK.nbf
Try flashing without the radio upgrade by removing the file mentioned in
the title (nk.nbf) from the folder where RUU.exe is exectuted (you might need to hunt fot the install files in the temporrary directories in your computer. The temp files are created after clicking the update.
Anyway, you're a senior You'll know what to so.
If there's no separate radio file for you, I would try taking the batt out,
then do a hard reset.
Peculiar !

Info
Try to flash using an official rom!! If You stil don't get through take off the battery for a couple hours then try again!! But If all this don't help, you'd better try to reflash with the rom you had previously

You used a MFG SPL = Developer SPL. Ask cmonex in the IRC for help. She works with the developer spl for hacking the spl.
good luck

Connect your phone to the PC using MTTY.
Send "set 14 0" (without quotes) and then task 8 to reboot.
Try if it works.

crazy cat said:
You used a MFG SPL = Developer SPL. Ask cmonex in the IRC for help. She works with the developer spl for hacking the spl.
good luck
Click to expand...
Click to collapse
oh good, she got some use from it

leoni1980 said:
My problem here is that I just cannot get out of bootloader. NO ROM OR RADIO WILL INSTALL ON MY DEVICE.
I've tried using goldcard and attempting numerous .nbh files and each time the update fails on the Radio_V2 part. I've also tried updating with the standard and custom RUUs and these always fail at 91%. the RUU always says 'Error 270....update error...the image file is corrupted' no matter which ROM I use.
Updating the radio only stalls at 96% and gets stuck there.
Currently my bootloader says 'Update ROM code error Please try again. See the attached photo for a screenshot. I am able to connect to a pc ok and run updates.
Ive also tried a hard reset, which WORKS but still doesn't boot up the device.
Can anyone help here? If not it looks like my HD2 is going on eBay for spares!
Click to expand...
Click to collapse
hey. can you send me a PM, I'm very interested in your device

Don't use it for spareparts..
I'm assuming you bought the phone?... Send it for repairs, they don't ask what you did. Just say you did a hard reset and this happend.. Believe me, they don't care at the repair shop (for sure @ eurotwice.be), great service they pickit up @ your door If you lost the receipt p.m. me

UPDATE
ok i didnt run MTTY through properly... after running task 29 this is the error I get....
ANYONE GOT ANY IDEAS????

The same problem exists in the link below
yes bro, please check this post
http://forum.xda-developers.com/showthread.php?t=371154&page=15

Boot screen....
OH MY.....
Just fired up the HD2 to try out some MTTY commands and the boot screen has fired up. This is the first time it's not gone straight to bootloader.
I will await the device possibly kicking into life......fingers crossed.

leoni1980 said:
OH MY.....
Just fired up the HD2 to try out some MTTY commands and the boot screen has fired up. This is the first time it's not gone straight to bootloader.
I will await the device possibly kicking into life......fingers crossed.
Click to expand...
Click to collapse
cool keep us posted how you get on.

Bootloader crash!

Hey Yall,
I dont know if this is because of android 2.1 or what.
But i installed the 2.1 RRU (RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6.35.15.11_release_signed)
I know that was very stupid of me, but i shall have to wait until someone with alot more brains, and knowledge of android to circumvent the security to downgrade.
But the problem is, when i try and re-flash anything, including the 3.32.405.1 it gets to the boot loader, and then hangs, the only was to reboot is to pull the battery, is this normal for the update?
The strange thing, i thought i would try (with the goldcard in ofcourse) installing the t-mobile (2.73.110) and it gets to the boot loader, but crash's, exactly the same as if i was installing 3.32.405 and i dont require to have the gold card in for it to reboot to the bootloader.
I have tried using the hboot method with HEROIMG.zip but still that does not provide any use because i get the error "Main Version is older!"
So is this normal of the bootloader for the new 3.32.405 or is it just mine?
If it is anyhelp, i have a t-mobile branded phone, and the computer im trying it form is W7 32bit
Thanks
Chris

Are you sure it is hanging??
When flashing a Radio it can sit on the boot screen for a Loooooooong time before continuing.

cdove85
it's ok
you have to wait somebody to crack new bootloader

Syrop said:
cdove85
it's ok
you have to wait somebody to crack new bootloader
Click to expand...
Click to collapse
Ohk thank you! i was worried that it had broke and i was stuck with a broken install
CHR1SGB said:
Are you sure it is hanging??
When flashing a Radio it can sit on the boot screen for a Loooooooong time before continuing.
Click to expand...
Click to collapse
Yeh it keeps returning with error 171 (i think its 171)