Database Develop

need confirmation of bricked g1 or not

ok so i got my hands on my sisters old G1 and it was unrooted and with rc30.
so i was able to downgrade it to rc29, flash it with RA recovery 1.7.0, and i was applying the the spl next. i booted into recovery and flashed the spl, and when i rebooted the g1 i just got suck at the tmobile g1 screen, i left it there for like 10 minutes thinking its gonna do its thing but it was still stuck there.
i pulled the battery out and pressed home and the power button, and it still didnt wanna go into recovery. so i pulled the battery again. so pressed and held the camera button and power button and it booted into the g1 screen instead!
so at this point i think i bricked it since im just stuck at the g1 screen and cant do nothing from there and i wanted a 2nd opinion to confirm it, or for a possible solution.
im thinking i messed up with the spl, but the one i have DL is the same one i used with my old G1 and its still kicking some (this one has a problem with the flex ribbon cable i believe, but completely usable.)

Im pretty sure when a phone is bricked, you cant even boot your phone, so im pretty sure ur phone is not bricked.
sorry, idk how to fix this, but im sure someone does.

You have to flash a rom, of coursebit would get stuck at g1 screen bcuz it had no direction(no rom)
Sent from my HTC HD2

the situation is you can get into hboot but not recovery nor system，right?
you could flash radio/spl via fastboot ,then flash recovery, rom at last.
read this thread:http://forum.xda-developers.com/showthread.php?t=532719,try to fix it

edward0119 said:
the situation is you can get into hboot but not recovery nor system，right?
you could flash radio/spl via fastboot ,then flash recovery, rom at last.
read this thread:http://forum.xda-developers.com/showthread.php?t=532719,try to fix it
Click to expand...
Click to collapse
no i cant access recovery, or hboot.
when i hooked it up to the computer hoping that it might recognize it, nothing happened either when i tried to boot into hboot, or recovery.

so ive been doin some more digging into the internet and yep i did end up bricking it.
looks like im gonna perform some phone operation between the two g1s to have a fully working one.

so pressed and held the camera button and power button and it booted into the g1 screen instead!
you said this last day,it doesn't work now?

edward0119 said:
you said this last day,it doesn't work now?
Click to expand...
Click to collapse
no it doesnt.
i have no access to hboot, or recovery. and it doesnt get recognized by my computer if i try to have it hooked up with the usb, so i cant even use adb or nothing.
so like i said, i could pretty much confirm myself that i bricked it. so right now im like phoneless because my original g1 has an issue with it not showing nothing if the keyboard is CLOSED (yes closed, not open! lol) and it ended up closing on me when i tossed it in my bed (doh!)

damm that sucks man.. sorry for your loss lol

ldrifta said:
damm that sucks man.. sorry for your loss lol
Click to expand...
Click to collapse
haha its alright, only option right now is phone operation with the two g1s i have, but i need to buy a torx screwdriver for it since the one i got is the wrong size.
but its not such a bad thing because ive been hearing that i might end up getting a new HTC phone as a graduation present. so heres to hoping thats true! lol

I guess it is bricked,maybe it can be fixed by a serviceman

Well seeing it's screwed lol try out JTAG used it before to unbrick a phone once ^^ that should be a solution for you

xillius200 said:
Well seeing it's screwed lol try out JTAG used it before to unbrick a phone once ^^ that should be a solution for you
Click to expand...
Click to collapse
yeah i was looking into that, but idk it seemed wierd for me.
but last night i opened up the g1s and replaced the motherboards from eachother. and now i got a working g1!

[Q] Stuck at the X, move on to a new phone?

I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!

Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??

Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.

matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.

SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.

Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.

Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick

Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App

Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G

Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.

You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.

Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed

[Q]Possible brick after failed RUU install?

First of all I experimented with some custom ROMs. But after a while I wanted to go back to stock and tried to install a RUU I already used succesfull. But during the installation it hung up and I had to cancel it. And now it is impossible to use everything. The phone just show me the black background with the HTC log and four triangles in the corners. I can't use the bootloader, go into recovery or use adb, first of all because my PC doesn't recognize my phone anymore. Already tried to use adb and some tools like the AIO bye anders and the XL Multi tool. I also tried the Forum search for bricked stuff, but nothing worked so far. Any idea how to fix it?
And please excuse my bad english. It was a long day. ^^

In pretty sure that's completely bring, idk how yous brick the sxl, ivebdonebso much stuff to mine and I wonder how mines still perfect, you might wanna look into some articles about jtag!

Don't know how, as I said. I did also do a lot of stuff to my phone, custom ROMs, Themes, Kernel etc. Now I just tried to go back to stock, relocked, went into fastboot, everything as prescribed.
And during the installation I've got said that the installation was aborted. The progress bar on the phone didn't react and the software stucked too. Additionaly, my PC is really potent, without any other software problems so far. So, Software forced to close and I had no other joice than to put the battery out of my phone to restart it. And so it happened.
Thanks for the info about jtag. As an Electrician, it is really inviting to buy such a machine. But I think, this time I'll bring it to repair and wait for the results. Let to the experts their job. But thanks for the reply.

Mr. Despair said:
Don't know how, as I said. I did also do a lot of stuff to my phone, custom ROMs, Themes, Kernel etc. Now I just tried to go back to stock, relocked, went into fastboot, everything as prescribed.
And during the installation I've got said that the installation was aborted. The progress bar on the phone didn't react and the software stucked too. Additionaly, my PC is really potent, without any other software problems so far. So, Software forced to close and I had no other joice than to put the battery out of my phone to restart it. And so it happened.
Thanks for the info about jtag. As an Electrician, it is really inviting to buy such a machine. But I think, this time I'll bring it to repair and wait for the results. Let to the experts their job. But thanks for the reply.
Click to expand...
Click to collapse
So if you turn on phone all you have is a black screen? What if you pull out battery and insert it and hold down volume down and power button? Does it go to bootloader or also just black screen? If black screen try adb devices and fastboot devices. And when connected look in control panel what it calls the phone. Perhaps it says qsusb or something?
Sent from my HTC Sensation Z710e using XDA Premium HD app

I'm not being rude I'm.just stating sxl is very hard to brick if you even try to, I'm not saying its your fault either, a fault USB cable could brick your phone if your half way through an installation if you can't get into bootloader, recovery or pick up your device in adb, I think the only solution is jtag! All the best!

ricky310711 said:
I'm not being rude I'm.just stating sxl is very hard to brick if you even try to, I'm not saying its your fault either, a fault USB cable could brick your phone if your half way through an installation if you can't get into bootloader, recovery or pick up your device in adb, I think the only solution is jtag! All the best!
Click to expand...
Click to collapse
before jtag , if the phone is under 2 years , always try to send it in for repair they cant boot up the device , then they cant see if it is unlocked

Very true Anders! Just hope he has warrenty!

anders3408 said:
So if you turn on phone all you have is a black screen? What if you pull out battery and insert it and hold down volume down and power button? Does it go to bootloader or also just black screen? If black screen try adb devices and fastboot devices. And when connected look in control panel what it calls the phone. Perhaps it says qsusb or something?
Sent from my HTC Sensation Z710e using XDA Premium HD app
Click to expand...
Click to collapse
When yo flash RUU the phone goes into kind an own bootloader. The black screen with a silver HTC logo. This is the only thing i get into, but with four triangles, in each corner of the display. It doesn't matter what I do, tried to pull the battery, use the key combo, adb/fastboot etc. When the phone starts, it shows directly the screen described above.
Sent in for repair today and just can wait now. But thanks guys for your replies.

How did it go? Did they fix your problem? Also this happened to me, I discovered that the cause was because installing the ruu relocks the bootloader before it wipes the Rom, and mine failed just before wiping the Rom,I had a custom Rom installed so it would not boot into it because the bootloader was locked so I re-unlocked the bootloader then the phone booted up normally!
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

[Q] Bricked m7u

Hi guys, I have the non-lte One running on 2.24.707.3. Today, I restored my stock nandroid (4.2.2) and then tried the rumrunner s-off (rumrunner_m7_2.24.401.1). It worked, and I was successfully s-off, superCID on hboot 1.54. I then flashed a modified hboot(descenpet_HBOOT_1.54_2.24_MOD) to remove the red warning. All went well. Later, while I was recieving a call, the phone got hung up, so I did a reset (holding the power + vol down buttons). The phone got switched off, but never booted back up.. I tried holding the power + vol down buttons but even the buttons aren't flashing.. Connecting it to my pc makes no connection sounds, and again holding the combo makes no difference. The charging light also doesn't light up. Please tell me what I should do, and whether it is a hard brick or soft brick. Thanks in advance.

Just press and hold the power button on it's own and see if anything happens

EddyOS said:
Just press and hold the power button on it's own and see if anything happens
Click to expand...
Click to collapse
Tried it, no avail. I think it's a hard brick, it's detected in my pc as in the screenshot. Any idea what to do?
Its not clear in the screenshot, it says Qualcomm HS-USB QDLoader 9008

n1234d said:
Tried it, no avail. I think it's a hard brick, it's detected in my pc as in the screenshot. Any idea what to do?
Its not clear in the screenshot, it says Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
why did you use modified hboot now you are in serious trouble. As you are supercid download any ruu and try flashing and if your pc can connect via fastboot you can fix your phone. To check you must type in adb fastboot devices. if results are positive tell me i can help you then

hapticc said:
why did you use modified hboot now you are in serious trouble. As you are supercid download any ruu and try flashing and if your pc can connect via fastboot you can fix your phone. To check you must type in adb fastboot devices. if results are positive tell me i can help you then
Click to expand...
Click to collapse
I used a modded hboot to remove the red warning, have a look at this page (http://forum.xda-developers.com/showthread.php?t=2316726)
To do an RUU, I need to reboot in fastboot, but I can't even get the phone to charge.. Of course adb doesn't detect it..
Another point to note is that I rebooted several times after flashing the modded hboot, and it worked all those times, so this is just random... :'(

Why do people care about the red writing? Unless you're sending it to HTC for repair it makes no difference! It just leads to complications such as this

EddyOS said:
Why do people care about the red writing? Unless you're sending it to HTC for repair it makes no difference! It just leads to complications such as this
Click to expand...
Click to collapse
Well, 2 things
1: The process worked, ok? It's a perfect process to remove the red text, and the modded hboot also worked, I rebooted several times after flashing it.
2: The matter of the fact is that I am actually sending it in for camera replacement.. I guess I'll just tel them to replace the mobo along with it..
So, lets stop fighting like losers and find a way to get out of this situation! It'll help many people in the future
Sent from my iPod touch using Tapatalk

C'mon anybody? I can give more info if required, I'd prefer to know how to solve this myself, rather than relying on htc...
Sent from my iPod touch using Tapatalk

If it's not booting up , and you're stuck in that QDLOAD thing, it's usually the mainboard that's fried and HTC replaced the mainboard in my Sensation under the warranty when it happened to me. I was S-OFF at the time as well, and it came back 100% stock and working

n1234d said:
Well, 2 things
1: The process worked, ok? It's a perfect process to remove the red text, and the modded hboot also worked, I rebooted several times after flashing it.
2: The matter of the fact is that I am actually sending it in for camera replacement.. I guess I'll just tel them to replace the mobo along with it..
So, lets stop fighting like losers and find a way to get out of this situation! It'll help many people in the future
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
good luck buddy btw to remove tampered i just ran indian ruu

n1234d said:
C'mon anybody? I can give more info if required, I'd prefer to know how to solve this myself, rather than relying on htc...
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I think most of the time, that's not something fixable unless by a service center. You may wanna check this thread: http://forum.xda-developers.com/showthread.php?t=2331454
For one guy the phone "magically" just started again, but I wouldn't hold my breath.
Sorry mate.

Ok, thanks for the info.. Maybe I'll make a strong case. My phone was originally replaced with a new one within a week because of battery problems, and scratch marks that I didn't make.. Then the second one had its mobo replaced for that same battery problem, and now I was going to send this in for replacement because my lower speaker is louder than the upper, and my camera has the dreaded pink tint and my phone has a big gap on its side where the service center guys hadn't closed the phone properly..and now this.. Oh boy, am I gonna make a strong case!!
Sent from my iPod touch using Tapatalk

nkk71 said:
I think most of the time, that's not something fixable unless by a service center. You may wanna check this thread: http://forum.xda-developers.com/showthread.php?t=2331454
For one guy the phone "magically" just started again, but I wouldn't hold my breath.
Sorry mate.
Click to expand...
Click to collapse
Yeah, I haven't got any alarms to save me now ;'/
But mine did get bricked randomly..
Sent from my iPod touch using Tapatalk

How about I try this?
http://unlimited.io/qhsusbdload.htm

As it doesn't mention the One I'd say no

EddyOS said:
As it doesn't mention the One I'd say no
Click to expand...
Click to collapse
Oh well, I went ahead and tried it anyways, but nothing happened.. So back to my good ol Nokia for now.. Btw, does rumrunner work with hboot 1.55??
Sent from my iPod touch using Tapatalk

Not yet, no

I bet we'll be seeing a lot more of these threads now...

Okay, although I've read a lot and I've learnt quite some bit, I want to know that if it wasn't the phone that unexpectedly died, was it my mistake somewhere? So I'll start with what I did, step by step, please have a look and tell me if I did anything wrong
1. Originally on ViperOne, tampered and unlocked on hboot 1.54
2. Restored stock nandroid 4.2.2 (2.24.707.3)(India) unrooted
3. Downloaded rumrunner (the version that I previously mentioned)
4. Started the exe
5. Phone reboots 2-3 times, process completes at pouring(3)
6. Reboot to verify s-off
7. Restore ViperOne nandroid
8. Run Revone to reset tampered flag
9. Flash modified hboot to remove warning.. Succeeds, reboot to verify warning gone
10. Reboot like 5-6 times to admire at the bootloader
11. I got a call and my phone hung
12. Reset the phone by holding power+vol down
Aaand the phone never booted again..
Sent from my iPod touch using Tapatalk

crixley said:
I bet we'll be seeing a lot more of these threads now...
Click to expand...
Click to collapse
Lol yeah.. I wouldn't think of myself as a total douche though, maybe I missed something..
Sent from my iPod touch using Tapatalk

[Q] Cannot boot after flashing incorrect kernal.

Hello,
I'd like to preface this to say I've searched through this and other sites but have not found quite the same problem. I also apologise for the small wall of text. I just want to post everything that seems relevant.
Several weeks ago I unlocked my phone and flashed the latest stable Cyanogenmod. This has all gone fine. I decided today I wanted to try something else and settled on TeamAsylum's 4.4 rom.
Downloaded a whole bunch of stuff and was a little confused as the flashing process seemed a bit different and I didn't fully understand it. I booted into Clockwork Recovery and inadvertently flashed the raw kernel from here, which I downloaded in my searches earlier thinking I needed it. I rebooted the recovery but now I get nothing from the phone. No lights, no display, no vibrations.
I have tried a reset (Power+Volume UP). I have tried using SUS and Flashtool but both get to the same point and stop (hole Volume DOWN and plug USB in). Nothing happens after this. The only thing telling me the phone is alive is when I plug it in, Windows makes the detected sound. If it's plugged in when I hold power+Volume UP it repeats the detection sound as if the phone is trying to boot over and over.
I realise I have ****ed up by flashing the kernal of a different phone. I'm hoping someone can help me or guide me in the right direction.
Thank you.

Nightstaar said:
Hello,
I'd like to preface this to say I've searched through this and other sites but have not found quite the same problem. I also apologise for the small wall of text. I just want to post everything that seems relevant.
Several weeks ago I unlocked my phone and flashed the latest stable Cyanogenmod. This has all gone fine. I decided today I wanted to try something else and settled on TeamAsylum's 4.4 rom.
Downloaded a whole bunch of stuff and was a little confused as the flashing process seemed a bit different and I didn't fully understand it. I booted into Clockwork Recovery and inadvertently flashed the raw kernel from here, which I downloaded in my searches earlier thinking I needed it. I rebooted the recovery but now I get nothing from the phone. No lights, no display, no vibrations.
I have tried a reset (Power+Volume UP). I have tried using SUS and Flashtool but both get to the same point and stop (hole Volume DOWN and plug USB in). Nothing happens after this. The only thing telling me the phone is alive is when I plug it in, Windows makes the detected sound. If it's plugged in when I hold power+Volume UP it repeats the detection sound as if the phone is trying to boot over and over.
I realise I have ****ed up by flashing the kernal of a different phone. I'm hoping someone can help me or guide me in the right direction.
Thank you.
Click to expand...
Click to collapse
Try this:
Open flashtool
Hold volume up and insert usb cable( you will enter fastboot )
then select fastboot and flash a good kernel for CM.
let me know it this works

RaZieLRaH said:
Try this:
Open flashtool
Hold volume up and insert usb cable( you will enter fastboot )
then select fastboot and flash a good kernel for CM.
let me know it this works
Click to expand...
Click to collapse
Hi,
I tried what you said. When holding Volume UP and inserting cable, literally nothing happens. I don't even get a sound from Windows detecting it.
Whilst trying this several times though I did notice if I press Power the phone seems to stay on for 30-60 seconds. If I press Power and plug it in, Windows will make a sound. It will then make another sound after 30-60 seconds as if the device has been removed or turned off.

no clue then sorry can't help

Nightstaar said:
Hi,
I tried what you said. When holding Volume UP and inserting cable, literally nothing happens. I don't even get a sound from Windows detecting it.
Whilst trying this several times though I did notice if I press Power the phone seems to stay on for 30-60 seconds. If I press Power and plug it in, Windows will make a sound. It will then make another sound after 30-60 seconds as if the device has been removed or turned off.
Click to expand...
Click to collapse
Just for giggles, check your device manager to see if you have an unknown device... (you may need to install the fastboot drivers...) I've bootlooped my phone a couple of times while putzing with my phone... And can normally get back into flash mode and fast boot mode...
Sent from my Xperia ZL using Tapatalk

scifan said:
Just for giggles, check your device manager to see if you have an unknown device... (you may need to install the fastboot drivers...) I've bootlooped my phone a couple of times while putzing with my phone... And can normally get back into flash mode and fast boot mode...
Sent from my Xperia ZL using Tapatalk
Click to expand...
Click to collapse
I did check this. There are no unknown devices. I did install the Xperia Z/fastbot/flashboot drivers from the flashtool folder. When it does make the detection sound Device Manager does 'reset' as if something has connected as well, although I can't find the device.
Most other similar issues have an LED or some type of display and generally are responsive to flashmode.

Note1 boot partition is the XZ's SBL3 (bootloader) partition. So you have effectively flashed a Note1 boot.img to your bootloader. Phone will never boot again once bootloader is hosed. Sorry about your loss
Sent from my C6603 using xda app-developers app

Shoey is right, your Z is toast now, sorry; the only solution here is to replace the MoBo, and that costs a pretty penny.
But why did you download stuff from the n7000 forum? Didn't everything said there sound unfamiliar and therefore suspicious enough for you
to double-check which forum you were in exactly?

I thought as much. I dun goof'd
Thanks for your help.
@chasmodo: Well I started in the N7000 thread and downloaded all the stuff and copied it to my SD card. I then realised I was in the wrong forum and switched to the relevant thread. All the stuff for the N7000 and the Z were both on my SD card, so it was just a stupid mistake really. Everything on both forums sounded a little unfamiliar. As I mentioned I was a bit cofused on the TWRP section. I should done more research before proceeding.
Do you think there is any use for the phone now? Do you know of anywhere/anyone I can donate it to for spare parts or something?

Nightstaar said:
Do you think there is any use for the phone now? Do you know of anywhere/anyone I can donate it to for spare parts or something?
Click to expand...
Click to collapse
As I said, you can get it fixed by replacing the MoBo, but I don't know how much that costs in your country. Google a little, contact someone, get the info and then decide what to do.

chasmodo said:
As I said, you can get it fixed by replacing the MoBo, but I don't know how much that costs in your country. Google a little, contact someone, get the info and then decide what to do.
Click to expand...
Click to collapse
I did have a look around and had trouble finding a main board in particular. I contacted Sony as well and they said it was quite expensive to replace.
I contacted my carrier and it appears getting a new phone is a lot cheaper than anything I've looked into so far.
Thanks for your help.

The next time you decide to flash your phone , make sure your in the correct forum. Lesson learned
Sent from my C6603 using XDA Premium 4 mobile app