Database Info

[Q] nexus s 4g bootloop help

i have a nexus s 4g i havent used in awhile because it is stuck on a cm7 bootloop. any think i can do? i havent been on here in awhile since i told myself i wouldnt root another phone. now i want one i can play with so im going to reuse my old one. i dont care if it gets reset considering it hasnt been used.

i4g3t143 said:
i have a nexus s 4g i havent used in awhile because it is stuck on a cm7 bootloop. any think i can do? i havent been on here in awhile since i told myself i wouldnt root another phone. now i want one i can play with so im going to reuse my old one. i dont care if it gets reset considering it hasnt been used.
Click to expand...
Click to collapse
First this is the wrong section for this. Second just restore the phone back to stock.
Click HERE !!!!!
Before you do this turn off your device, press volume up and power at the same time !! That should take you to Bootloader Menu !!
I recommend you to stay stock, if you have no experience rooting, flashing or unrooting don't try again BEFORE educating yourself more.

Try going into clockwork mod mount USB in advanced menu download a new rom put it on your SD card and flash it. Just so u know this belongs in q/a not development.
Sent from my Nexus S 4G using xda premium

it doesnt allow me to do anything. and isnt recognized by the computer. and i realized its in the wrong section but its kind of late now.. i just plugged it to let it charge. its doing something it hasnt done before.. its stuck on bootloop but when i unplug it it flashes the lockscreen with status bar searching for media then turns off

i4g3t143 said:
it doesnt allow me to do anything. and isnt recognized by the computer. and i realized its in the wrong section but its kind of late now.. i just plugged it to let it charge. its doing something it hasnt done before.. its stuck on bootloop but when i unplug it it flashes the lockscreen with status bar searching for media then turns off
Click to expand...
Click to collapse
Install the drivers on your computer. U cand find them here somewhere and hold volume up + power and try to use fast boot to flash cwm
Sent from my Nexus S 4G using xda premium

Can you access recovery by holding volume + and power? If so, just wipe everything and reflash the rom on your sd.

Thread moved to Q&A.

I think I'm bricked, what should I do?

I flashed a Jellybean touchwiz rom for Verizon GS3, and went to reboot and now nothing, zero zip nada. No charging led light, no way to get into recovery and no response.
Anything I can do?

what happens when you do vol up + home+power button?

Absolutely nothing. I tried to get back into the recovery to see if I could restore my backup and nope.

did you try leave it pluged in for 30mins ?
does it vibrate once when you try to turn it on?

No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.

NickTheMajin said:
No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.
Click to expand...
Click to collapse
leave it plugged in for a while to make sure its not drained battery
do you have a usb jig?

I don't have a USB jig but this is possibly good news. I removed the battery and SD card and plugged it into my computer and it tried to install drivers (failed but tried) and the led light comes on red.

if your gettin led now you more then likely need to let it charge

It doesn't give me the led with the battery in

Plug it into a wall charger for at least 30 or even better if you can get a battery from someone.
Sent from my sexy white Eclipsed galaxy S3

I think its gone still nothing.

red led means qualcomm download mode. sounds dead to me

Yeah, haha. I saw it and mentally prepared myself for it. Literally just got the phone today so Verizon had no qualms with just sending me a new phone. Guess I'm reactivating my Rezound in the meantime. Thanks for the help guys.

you know
I am surprised. That also happened to me the first time i flashed that very same rom (touchwiz) with twrp . I have done this so many times , i literarily can flash a rom on the way to work .
I was in shock , i still dont know how the heck can i flash a rom and brick .
I plugged mine into windows and i got the device manager driver error from hell . and my phone never came back up again
I stayed away form twrp and touchwiz and i still cant possibly comprehend how a simple rom flash can brick my phone .

Which ROM did you flash?
Sent from my SCH-I535 using xda premium

you could probably send it to get Jtag'ed for around $60 if your warranty is invalid (ie used device)

You just hard bricked it. I did the same thing. Check here - post 5 shows the same symptoms :http://forum.xda-developers.com/showthread.php?t=1770341
And here: http://forum.xda-developers.com/showthread.php?t=1791721
I was pushing a copy of root66 that I hadn't md5'd. Took a JTAG to bring me back (twice) .
Sent from my SCH-I535 using xda app-developers app

So, in the future, md5 checksum absolutely everything since I'm assuming now that that is why this happened? (Since I made doubly sure I was flashing a rom for my phone).

If you still have the file you downloaded, you can check it. That would answer that question. If it checks out fine, then we have to look elsewhere for the problem.
BTW, MobileTechVideos.com can bring you back - based on my experience with them, I highly recommend.
Sent from my SCH-I535 using xda app-developers app

Please share exactly what you did so others can benefit from your unfortunate experience.
What ROM did you flash?
Did you use ODIN or a recovery?
If recovery, which one - CWM or TWRP?
Was there any unusual condition you can think of ... low battery, USB connected to computer or to charger, etc?

[Q] Nexus S - can't mount anything! - stuck on Google Logo

Hello!
Okay, so the weirdest thing has happened with me. My Nexus S (i9023) was working absolutely fine till last evening when it ran out of battery. After I came back home, I put it for charging and switched it on.
For the first few time, nothing would show except the USB connected/ disconnected screen which appears everytime you plug your phone in. I thought maybe it was just being weird, so I took out the battery and booted it up again. This time I am just stuck at the Google Logo! It is not going ahead.
I can enter CWM Recovery. However, I cannot mount sd card or usb storage or anything for that matter. If I try and install through .zip it says 'e can't mount sd card'. I can't format my sd card either, same problem of can't mount. I thought if I tried pushing a ROM in by ADB that might work.. It did transfer the file it showed that in the cmd window. However, CWM refuses to mount my sd card or my usb storage.
So basically, in essence, I'm locked out of my Nexus! Please please help. I'm really lost and confused now.
Thanks so much.
Alex

Similar problems below in this thread with solutions.
Let your phone sit for an hour with the battery out, Download Wug's Nexus Toolkit from the development section, download drivers from there and install stock boot img then re-root.
I have never seen it before but seems like this prob is coming up a lot lately. It can be fixed. Good luck.
Sent from my Galaxy Nexus using Tapatalk 2

Nexism said:
Similar problems below in this thread with solutions.
Let your phone sit for an hour with the battery out, Download Wug's Nexus Toolkit from the development section, download drivers from there and install stock boot img then re-root.
I have never seen it before but seems like this prob is coming up a lot lately. It can be fixed. Good luck.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your reply. I'm starting now. I have a doubt, how do I install stock? Since I can't seem to be able to mount anything..
"It can be fixed" - few words have given me this much hope in my life! Thanks a lot!
EDIT: I guess you mean flash through ADB right? Okay, let me try that. I really hope you are right. Some of those other problems lead to paying up! Ouch.

Hey! I just tried using WUGS.. for some reason it does not make the final boot and instead says: 'Fastboot Status - FAILWrite Fail' -- oh god.. I'm trying it again now..
Is there any other way out? :/

Okay, so now my recovery is also gone after using WUGS.. oh man. And the phone isn't starting up. Please please please help? I'm getting really desperate now.
EDIT: And it sucks that I can't post in the WUGS thread (http://forum.xda-developers.com/showthread.php?t=1766475) because I have less than 10 posts! fml.

can you boot into fastboot? If so then itnwasnthe same prob I had when I wiped my phone and SD in recovery. If you can boot into fastbootnthen makensurenyou leave the batt out format least an hour. If you installed Wug's drivers the bottom left corner ofnfastboot should give a message.
Sent from my Galaxy Nexus using Tapatalk 2

Nexism said:
can you boot into fastboot? If so then itnwasnthe same prob I had when I wiped my phone and SD in recovery. If you can boot into fastbootnthen makensurenyou leave the batt out format least an hour. If you installed Wug's drivers the bottom left corner ofnfastboot should give a message.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, I can get into fastboot - i'm leaving the battery out now - do you think i should try
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and then flash everything again?
There is always a way to recover the nexus right? Even if it is hardbricked, right?
I really really appreciate your help.

I too have this problem but after a lot of battery pulls it does eventually start up. It just started happening all of a sudden. Ive heard that heating it up with a hair dryer or heatgun can help and also re-locking and un-locking the boot loader can help as it wipes the card. Could be worth a try.

Any luck Someone? I know it sux big time to feel like your phone is bricked. I am not a dev or expert but it sounds like the prob I had last week, when I posted no one replied so I ordered a GNex thinking all was lost. Before I activated my new phone I felt like I had to fix my nexus before getting started on my new phone and that's my situation. I don't want you to feel like the community has forgot you and thats why I'm trying to help. Were you able to get Wug's Toolkit to recognize your phone after leaving the batt out? I don't know why but I think that's the key. I had to leave mine overnight 'cause I don't have a PC and the next day at my friends house when I plugged the USB in I got that message at the bottom of fast boot "system normal" or something to that effect. Once recognized the stock boot IMG is what you need.
ANY ONE ELSE WHO HAS HAD THIS OR A SIMILAR ISSUE PLEASE GIVE SOME ADVICE. LET'S NOT LEAVE A COMMUNITY MEMBER WITH A LIFELESS PIECE IF PLASTIC. THANKS FORUM.
To set your mind at ease yes, I believe as long ad you have access to fastboot your nexus can be saved.
Sent from my Galaxy Nexus using Tapatalk 2

sounds to me like a hardware issue, since you haven't changed software and it seems like a brick. try flashing stock rom via fastboot, you should be able to google around how you can do that.

Blo0dyyy said:
sounds to me like a hardware issue, since you haven't changed software and it seems like a brick. try flashing stock rom via fastboot, you should be able to google around how you can do that.
Click to expand...
Click to collapse
Hi, if I'm not wrong essentially what WUG does automatically is what you do by fastboot (erase bootloader, cache, system.. and then flash all of them back) in both system fails to wipe and refuses to be flashed again (flashwrite error).
I don't want to lock it and then unlock it again because I read in other threads that it might lead to a permanent lock with an error for subsequent unlocking - that would leave me completely out.
Anyway, let's see - I've given it to someone to check it up. I'll keep you guys posted. He said he wanted to repartition the sd card.
My intuition says: hardware problem!

So I tried Odin today - and that also did not work it refused to flash the ROM. In the process I somehow managed to mess up the bootloader such that the phone would have some two lights on randomly when I switch on. It doesn't go into download mode either. I next plan to use JTAG to get the bootloader back and then reflash everything. Hopefully, that should sort things out. The Resurrection tool is amazing! I'll keep you guys posted.

Get it going someone?
Sent from my Galaxy Nexus using Tapatalk 2

I have the same problem as you, with the added difficulty of my phone not being recognized by anything other than fastboot. No ADB commands will function. It was charging, rebooted itself into a bootloop, and I have been struggling with it ever since. It is currently a worthless piece of plastic, my favorite phone ever, gone.
I can wipe and re-write recovery all that I want, but it seems as if the sdcard partition that /system and some other stuff writes too is either corrupted or physically damaged. Every time I flash it all via fastboot it all goes as stated, but gives me a fail message on the last two partitions and never allows me to actually write a new ROM or boot image. I wanted to try ODIN but can't seem to get it to recognize my phone in download mode...
Let me know if you have any success or progress!

someone. said:
So I tried Odin today - and that also did not work it refused to flash the ROM. In the process I somehow managed to mess up the bootloader such that the phone would have some two lights on randomly when I switch on. It doesn't go into download mode either. I next plan to use JTAG to get the bootloader back and then reflash everything. Hopefully, that should sort things out. The Resurrection tool is amazing! I'll keep you guys posted.
Click to expand...
Click to collapse
I myself am experiencing the same problem.... Did your cell got fixed.....?? Did JTAG worked kindly keep us posted em really concerned about it... coz your solution might get me some where or else i hav completely lost my phone ;(

Get it going someone?
Click to expand...
Click to collapse
Hey Nexism! Sorry for the late reply - things've been busy.
The JTAG is giving an internal voltage for some reason - so I've sent it for repair. It'll be repaired by tomorrow or so.. I'm then going to set it back up. It's all already soldered and all, just waiting for the JTAG. I think I've understood how this thing works now. So yeah, I'm hoping it's all sorted. Thanks a lot for your concern man.
I have the same problem as you, with the added difficulty of my phone not being recognized by anything other than fastboot.
Click to expand...
Click to collapse
Well my phone went blank - no fastboot mode - no download mode - no nothing - when i'd put the battery in randomly two of the four front lights would come on.. JTAG is going to solve the problem hopefully.

someone. said:
Hey Nexism! Sorry for the late reply - things've been busy.
The JTAG is giving an internal voltage for some reason - so I've sent it for repair. It'll be repaired by tomorrow or so.. I'm then going to set it back up. It's all already soldered and all, just waiting for the JTAG. I think I've understood how this thing works now. So yeah, I'm hoping it's all sorted. Thanks a lot for your concern man.
Well my phone went blank - no fastboot mode - no download mode - no nothing - when i'd put the battery in randomly two of the four front lights would come on.. JTAG is going to solve the problem hopefully.
Click to expand...
Click to collapse
So ladies and gentleman, JTAG also failed - apparently something was wrong with the sd card only. I got my motherboard replaced - luckily the guy I went to knew someone and Samsung and charged me Rs. 4,000 as opposed to the Rs. 8500 quoted by the Samsung Service Centre. Oh well.
Back on my Nexus now. XD

someone. said:
So ladies and gentleman, JTAG also failed - apparently something was wrong with the sd card only. I got my motherboard replaced - luckily the guy I went to knew someone and Samsung and charged me Rs. 4,000 as opposed to the Rs. 8500 quoted by the Samsung Service Centre. Oh well.
Back on my Nexus now. XD
Click to expand...
Click to collapse
I am with the same problem here... I cant turn off my phone or it get stuck in pre-boot phase. Acess recovery and cant mout sd card. Using last stable cm 10.
I think my sdcar is dead.

Same problem here. Around 8 out of 10 times I get stuck on the Google logo, 8 out of 10 times in recovery I can't mount SD card as well. And if I successfully boot, Media wakelocks and my battery drains in sleep as fast as if the screen were on. Please help.

For me I first noticed that my apps weren't using the SD partition. Tried to mount normally (fully loaded ROM) (ROM is SlimBean Beta2), but it would not mount. Went into CWM and tried to mount in there, but it would not work. tried to "Format /sdcard" but "Error mounting /sdcard". My phone still boots and runs fine, but I just don't have access to the SD partition. I don't want to do anything because I need my phone for business. Is there any PROVEN way to fix this yet?

[Q] Droid 3 stuck in bootloop

I realize there are multiple threads like this but throughout all of them I have not found any that relate to my issue or a combination of them. If I have missed one I apologize in advance and please direct me to that thread then. I was running steel droid what I thought was 5.5 ICS but it looks like it is 5.1 according to the forums. I was previously running steel droid 4.5 GB. I was switching back to 4.5 because I could not get wifi hotspotting to work. I forgot to wipe my cache and went to install 4.5 and I am stuck in bootloop. X+Power gives me the android error screen, M+Power allows me into the main menu but I cannot use AP fastboot, SBF motorola will not pick up my phone and the screen will show a connection to the USB cable. I've never had a problem before but also have never forgotten to wipe the cache so any thoughts would help.

m3schz8! said:
I realize there are multiple threads like this but throughout all of them I have not found any that relate to my issue or a combination of them. If I have missed one I apologize in advance and please direct me to that thread then. I was running steel droid what I thought was 5.5 ICS but it looks like it is 5.1 according to the forums. I was previously running steel droid 4.5 GB. I was switching back to 4.5 because I could not get wifi hotspotting to work. I forgot to wipe my cache and went to install 4.5 and I am stuck in bootloop. X+Power gives me the android error screen, M+Power allows me into the main menu but I cannot use AP fastboot, SBF motorola will not pick up my phone and the screen will show a connection to the USB cable. I've never had a problem before but also have never forgotten to wipe the cache so any thoughts would help.
Click to expand...
Click to collapse
Not wiping cache won't give you boot loop lol just go back into recovery wipe everything and flash a working ROM solved :thumbup:
Sent from my SCH-I500 using Tapatalk 2

bbrad said:
Not wiping cache won't give you boot loop lol just go back into recovery wipe everything and flash a working ROM solved :thumbup:
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I would but I get android error screen with exclamation mark each time regardless of how I access recovery X+Power or vol +,- and Power then going to recovery, I wouldn't have thought that not wiping the cache would have been the cause but it was the one step I didn't do that I normally always do so I was just adding it in for information but thanks for the know how that it wasn't the cause. Any other thoughts since I cant even get into my backup ROM or recovery, I have another SD card not sure if my SD card has become fried for some reason, I will be trying that to see if maybe that is all it is.

m3schz8! said:
I would but I get android error screen with exclamation mark each time regardless of how I access recovery X+Power or vol +,- and Power then going to recovery, I wouldn't have thought that not wiping the cache would have been the cause but it was the one step I didn't do that I normally always do so I was just adding it in for information but thanks for the know how that it wasn't the cause. Any other thoughts since I cant even get into my backup ROM or recovery, I have another SD card not sure if my SD card has become fried for some reason, I will be trying that to see if maybe that is all it is.
Click to expand...
Click to collapse
Well I'm on a Samsung device but we have a program you load files in and you can flash your device back to stock do you have something like that?
Sent from my SCH-I500 using Tapatalk 2

Droid 3 stuck in bootloop'
bbrad said:
Well I'm on a Samsung device but we have a program you load files in and you can flash your device back to stock do you have something like that?
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Yep but phone isn't picking up my data cable and how ever many issues that have come about here, I think I am SOL but gonna try an SD card hoping that it is just a bad SD card or something like that. May end up having to use part of that great tax return also, thanks for the help, I'm going samsung next, that whole fore sight wasn't there two years ago.

In it's current state, is it in any way possible to tell that it is rooted? Is the boy animation stock or a different one? Motorola might repair it for you if you can't tell that it's been rooted
Sent from my HTC6435LVW using xda app-developers app

Droid 3 stuck in bootloop
dj2muchxx said:
In it's current state, is it in any way possible to tell that it is rooted? Is the boy animation stock or a different one? Motorola might repair it for you if you can't tell that it's been rooted
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Unfortunately you can easily tell that it is not stock ROM by bootloop

Well your computer should recognize your droid that's a common problem with Odin and Samsung one of these steps always work so try then and seen if we can't get your droid recognized NUMBER 4 WILL WORK 99% OF THE TIME BUT TRY THE OTHER METHODS FIRST 1. Use the stock cable or try a difrent port 2. If its possible on your program take out the battery and SD card as leaving them in course problems 3. Run the program as aminstrative 4. Plug the phone in and have it in download mode or whatever you call it WHILE THE COMPUTER IS BOOTING Up This will force the computer to recognize it not the best method but it always works
Sent from my SCH-I500 using Tapatalk 2

Droid 3 stuck in bootloop
bbrad said:
Well your computer should recognize your droid that's a common problem with Odin and Samsung one of these steps always work so try then and seen if we can't get your droid recognized NUMBER 4 WILL WORK 99% OF THE TIME BUT TRY THE OTHER METHODS FIRST 1. Use the stock cable or try a difrent port 2. If its possible on your program take out the battery and SD card as leaving them in course problems 3. Run the program as aminstrative 4. Plug the phone in and have it in download mode or whatever you call it WHILE THE COMPUTER IS BOOTING Up This will force the computer to recognize it not the best method but it always works
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Thanks step 4 ended up being the working method, happened again when loading gingerbread back on, so I walked through it again, removed ICS from memory card wiped phone completely and then loaded gingerbread back on and finally had success. Thanks for all the help

m3schz8! said:
Thanks step 4 ended up being the working method, happened again when loading gingerbread back on, so I walked through it again, removed ICS from memory card wiped phone completely and then loaded gingerbread back on and finally had success. Thanks for all the help
Click to expand...
Click to collapse
NP if you ever need anything just ask
Sent from my SCH-I500 using Tapatalk 2

Xperia L no longer works!

Hello guys I was wondering if anyone can help me with this issue. But first things first the details!
I have kitkat AOSPA 4.0 Beta-6 installed on my xl with thunderzap kernel 4.1 r2 with internal storage fix. I have been running this ROM and kernel on my phone for about 3 to 4 days max.
Now when the issue happened was this morning. The alarm went off my phone and was working fine. I then noticed the battery was at 20% so i decided to switch off the phone and plug it into the mains. I then went out for about 2-3hrs by the time I got back I noticed that the display did not light up with the charging logo when I pressed the power button. I tried to switch it on but nothing happens what so ever.
Things that I have already tried.
-Removed battery for 10mins
-Leave it on charge again for 3hrs
-Tried to enter into flash mode and fastboot.
I have connected the phone to the pc without the battery and the led just lights up green very briefly. My pc detects it as a Qualcomm HS-USB QDLoader 9008 (COM4).
I have run out of ideas and any help you provide will be very appreciated.

HatchetEgg said:
Hello guys I was wondering if anyone can help me with this issue. But first things first the details!
I have kitkat AOSPA 4.0 Beta-6 installed on my xl with thunderzap kernel 4.1 r2 with internal storage fix. I have been running this ROM and kernel on my phone for about 3 to 4 days max.
Now when the issue happened was this morning. The alarm went off my phone and was working fine. I then noticed the battery was at 20% so i decided to switch off the phone and plug it into the mains. I then went out for about 2-3hrs by the time I got back I noticed that the display did not light up with the charging logo when I pressed the power button. I tried to switch it on but nothing happens what so ever.
Things that I have already tried.
-Removed battery for 10mins
-Leave it on charge again for 3hrs
-Tried to enter into flash mode and fastboot.
I have connected the phone to the pc without the battery and the led just lights up green very briefly. My pc detects it as a Qualcomm HS-USB QDLoader 9008 (COM4).
I have run out of ideas and any help you provide will be very appreciated.
Click to expand...
Click to collapse
this happens to me before month (ill send it to RMA and got new motherboard) ive got accidental pc poweroff while flashing
at this moment theres no other way how to revive this state bcz nobody have proper data to program internal mlc via QPST and without this one it means you have dead motherboard, you need to send it to RMA
edit: before you shut off phone you maybe do something wrong, like formating whole internal memory or switching internal to external or something like that ... phone is now in download mode for qpst sw, so it looks like you have no bootloader so phone doesnt know how to boot to os

Flashing_Expert said:
this happens to me before month (ill send it to RMA and got new motherboard) ive got accidental pc poweroff while flashing
at this moment there no other way how to revive this state bcz nobody have proper data to program internal mlc via QPST and without this one it means you have dead motherboard, you need to send it to RMA
Click to expand...
Click to collapse
Thanks for your help. The strange thing is this is my 3rd xperia l because of the same issue it only seems to happen only when flashing another rom other than stock. When I had the same issue they told me there was nothing wrong with it.
I had a Samsung galaxy ace before Major difference in spec I know but I had never had any issues flashing a new rom.
Would they actually repair the phone? as it is rooted and unlocked bootloader?

Propably first ''Sudden Death'' noticed on Xperia L.. That's not funny, Sony.

HatchetEgg said:
Thanks for your help. The strange thing is this is my 3rd xperia l because of the same issue it only seems to happen only when flashing another rom other than stock. When I had the same issue they told me there was nothing wrong with it.
I had a Samsung galaxy ace before Major difference in spec I know but I had never had any issues flashing a new rom.
Would they actually repair the phone? as it is rooted and unlocked bootloader?
Click to expand...
Click to collapse
if mobo is dead they even cant read internal memory, so be calm they probably replace mobo to new one without any asking...
and this is not bcz flashing this is only bcz human factor...

Flashing_Expert said:
if mobo is dead they even cant read internal memory, so be calm they probably replace mobo to new one without any asking...
and this is not bcz flashing this is only bcz human factor...
Click to expand...
Click to collapse
Interesting well it wont be long until I have a new contract anyway. Hopefully I will get a new one. I just wont use a custom rom ever again.
Thanks for your support on this matter.
EDIT: Is there anyway to get the bootloader to work again if thats the reason to why it will not boot.
On the rom that I used for it. It had emulated the internal storage just to get the 4g back.

Try to flash a stock ftf, losing your data (I'm sorry) if you can enter flashmode. Then try to not install the Kernel, possibly the problem is there.
Luck!
Sent from my C2105 using xda app-developers app

HatchetEgg said:
Interesting well it wont be long until I have a new contract anyway. Hopefully I will get a new one. I just wont use a custom rom ever again.
Thanks for your support on this matter.
EDIT: Is there anyway to get the bootloader to work again if thats the reason to why it will not boot.
On the rom that I used for it. It had emulated the internal storage just to get the 4g back.
Click to expand...
Click to collapse
no theres no other way to get internal memory back, its gone, its erased (whole 8gb memory, even partitions or bootloader is erased) or memory chips are broken nothing more or less
theres a sw called QPST from qualcomm for programming internal memory (mainly for right partitions formating inside mmc and basic BL programming) without it theres no other option than get your xl to RMA and mobo change
---------- Post added at 10:19 PM ---------- Previous post was at 10:16 PM ----------
ArnauGonzalez98 said:
Try to flash a stock ftf, losing your data (I'm sorry) if you can enter flashmode. Then try to not install the Kernel, possibly the problem is there.
Luck!
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
OP said that in first comment that his xl is dead without flashmode/fastboot mode, and if it shows in pc after connection qhusb dload driver memory is broken or formated, mobo=dead
kernel surely cant broke your xl, only playing with memory like switch internal/external

Sorry Man, your phone is now at the heavens of mobile phones.
Buy another XL!
Sent from my C2105 using xda app-developers app