dear, sorry the English, but I need a help from you.
I made the installation of IMG extracted the KDZ and did flash the recovery, however, now my machine not the sign of life, the computer does not detect the device, the device does not turn on, not of any sign of life. already tried in various corners anything to help me have some solution. I did the procedure based on the stock rom flash D405 with img extracted files. After that the only active device the display if I put to load without the battery, which displays the battery with a question mark. The device does not enter download mode, does not go into recovery, does not display anything, as if completely dead. Does anyone have aware and know any solution to the problem? Note: I've tried the LG flahs tools, it does not detect the device.
You have probably the worst case of them all. I suggest you to take your phone to warranty and see if they can replace it (because there probably isn't any way to fix it). If your warranty is void, then, I'm afraid, you will have to get a new device. I have had this issue myself, and it was solved only by replacing whole internals of the phone. Good thing that I still had my warranty, so it didn't cost anything. Good luck.
linasj said:
You have probably the worst case of them all. I suggest you to take your phone to warranty and see if they can replace it (because there probably isn't any way to fix it). If your warranty is void, then, I'm afraid, you will have to get a new device. I have had this issue myself, and it was solved only by replacing whole internals of the phone. Good thing that I still had my warranty, so it didn't cost anything. Good luck.
Click to expand...
Click to collapse
but this happened to you because of flash ROMS? How long on average it took for you to get the unit back?
wmosquini said:
but this happened to you because of flash ROMS? How long on average it took for you to get the unit back?
Click to expand...
Click to collapse
Yes. I tried to flash a ROM (which requires an unlocked bootloader), but for some reason the bootloader wasn't actually unlocked, and flashing a ROM caused the device to be bricked. This is probably what you would call a hard-brick.
In my case, replacement took a little more than a week. But this could differ from country to country.
linasj said:
Yes. I tried to flash a ROM (which requires an unlocked bootloader), but for some reason the bootloader wasn't actually unlocked, and flashing a ROM caused the device to be bricked. This is probably what you would call a hard-brick.
In my case, replacement took a little more than a week. But this could differ from country to country.
Click to expand...
Click to collapse
But in time to take the assistance, you said what about it? The unit stopped working alone?
wmosquini said:
But in time to take the assistance, you said what about it? The unit stopped working alone?
Click to expand...
Click to collapse
Exactly. Since the device cannot be turned on, I don't think they have any way of checking if it was rooted or tampered with in any way. So your best bet is to just play dumb and tell them your phone doesn't boot up. That helped me to get it fixed for free.
linasj said:
Exactly. Since the device cannot be turned on, I don't think they have any way of checking if it was rooted or tampered with in any way. So your best bet is to just play dumb and tell them your phone doesn't boot up. That helped me to get it fixed for free.
Click to expand...
Click to collapse
Legal, tomorrow I will even take the guarantee to solve as fast as possible. Really the device not the sign of life at all. I will inform you that the device was carrying at night and just when I catch him in the morning, he was like that.
Thank you for your help. : D
My first L90 didn't have a functional GPS, was brand new (1 week), problem was I rooted in the first day
Factory reset, hid superuser app, got a new l90
Gud luck
bacitoto said:
My first L90 didn't have a functional GPS, was brand new (1 week), problem was I rooted in the first day
Factory reset, hid superuser app, got a new l90
Gud luck
Click to expand...
Click to collapse
hard reset does not remove all traces of root. There is RCT checking. u can be sure that have no traces of root when RCT was reset. On kit kat we have chance to reset it without reflashing. But on 5.0 only reflash
---------- Post added at 11:17 ---------- Previous post was at 11:11 ----------
wmosquini said:
dear, sorry the English, but I need a help from you.
I made the installation of IMG extracted the KDZ and did flash the recovery, however, now my machine not the sign of life, the computer does not detect the device, the device does not turn on, not of any sign of life. already tried in various corners anything to help me have some solution. I did the procedure based on the stock rom flash D405 with img extracted files. After that the only active device the display if I put to load without the battery, which displays the battery with a question mark. The device does not enter download mode, does not go into recovery, does not display anything, as if completely dead. Does anyone have aware and know any solution to the problem? Note: I've tried the LG flahs tools, it does not detect the device.
Click to expand...
Click to collapse
Did u flash it from 5.0 or 4.4? This problem may have solve without service center. But if u have warranty, it must not worry u.
@linasj
Hello, I just want to know that while booting, did your phone show the message "Secure booting error"?
I am getting this message at the LG logo and then device just shuts off.
No, I don't think I ever got this message.
Sent from my LG-D405N using XDA Free mobile app.
pick.orion said:
@linasj
Hello, I just want to know that while booting, did your phone show the message "Secure booting error"?
I am getting this message at the LG logo and then device just shuts off.
Click to expand...
Click to collapse
In my case, the device did not care and neither carried, gave no sign of life. I sent him for assistance in less than one week they made the repair by warranty.
Related
The story so far...
Bought a new Optimus Black and gave it to my girlfriend for her birthday a couple of days ago. After playing with it for about an hour she put it down, I picked it up and decided to have a tinker. I installed Cyanogen mod 3.5.1 after rooting it with Gingerbreak. So far so good but I didn't really like the look of the ROM and the absence of a Market seemed like hassle so I used ClockworkMod to restore the backed up stock ROM.
It's still working fine but now I see there is an official update from inside the phone. I presume it's the upgrade to Android 2.3 so run it and reboot the phone. That's when it all goes wrong. I'm now stuck in the CWM recovery screen. I try all the options, following any online guides I can find that were supposed to have worked for people. I try restoring the backup, restoring cyanogen, clearing the cache, dalvik, everything but nothing happens and I keep booting back into the CWM recovery screen.
Next day I try the LGUnitedMobileDriver and the phone recovery option but despite trying several times I can get no further. A friend tried to use Odin to restore it but got no success. Finally, we tried restoring with a KDZ file with
KDZ_FW_UPD_EN, Windows Enabler and LG B2CTool and now the phone got stuck in yet another loop - a black screen with 'updating firmware'. The LEDs flash for a minute and it reboots and does the same again.
What's more, the phone will now no longer charge or turn on without being connected to the mains.
What are my options here?
Follow the tutorial given below.
http://forum.xda-developers.com/showthread.php?t=1275315
Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.
pickarooney said:
Thanks, but I've already tried that and it doesn't work. I'm forever stuck in the firmware update screen.
Click to expand...
Click to collapse
have you tried the CS_EMERGENCY option in R&D TOOLS? Wait I'll find the link..
Here >>> http://forum.xda-developers.com/showpost.php?p=18841596&postcount=8
http://forum.xda-developers.com/showpost.php?p=18740082&postcount=45
The CS_EMERGENCY is the only thing worked, he used a german V10A ROM. If you managed to unbrick it, you can flash it again with your desired KDZ, or use CS_EMERGENCY and flash directly your desired KDZ. TRIAL AND ERROR.
Emergency c-section... nope, I will try that now!
Said that it will get stuck at 4% but it is still flashing. Just wait for the phone to reboot by itself.
It just crashes with a fatal error as soon as it gets to the second tab (downloading) on both PCs I tried it on. I tried several KDZ files with the same result.
Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?
pickarooney said:
Does anyone know if it's possible to physically change the ROM on this phone and if it would be worth trying that before binning the thing?
Click to expand...
Click to collapse
Does it have warranty? Why not RMA it, I think it has a hardware problem now since you mentioned it doesn't charge anymore. Also, have you tried a different USB cable?
The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.
pickarooney said:
The warranty gets voided as soon as you root or mod a phone and it's probably as expensive to get it fixed outside of warranty as to buy a new one.
Click to expand...
Click to collapse
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.
gabwerkz said:
Most of the time they change the board right away if it can't boot (as many as I've read) board was changed and none just revived the OS. So they won't know you rooted it. Just specify that they should contact you first before making any changes.
Click to expand...
Click to collapse
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..
darkzorn said:
true.. you can just tell them that you received an update and upon getting it the phone wont boot anymore.. just dont tell them that you rooted it or tinkered it in any way.. i'm sure you'll be able to get your warranty that way..
Click to expand...
Click to collapse
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
Fingers crossed for you !!!
pickarooney said:
Well, that's exactly what I did so we'll see in two weeks if I get a fixed phone free of charge
Click to expand...
Click to collapse
IT will mostly work..Good luck though and please do reply here and let us know if it worked..
I'm a complete noob in dire need of help. I wanted to root my phone, and read the 3 procedures mentioned in the sticky thread. The 2nd one (nvflash) seemed very well explained and was sure to work with 2.3.4 so I decided to use that. As I was in my friend's house I used his pc and installed the drivers while my phone was connected in apx mode. Then I double clicked the "install internal xp" batch file which resulted in a black window with some texts, but seeing this my friend freaked out and closed the window before the process was finished. I told him he shouldn't have done that. I then disconnected the phone and switched it on. It seemed to switch on properly. So I then switched it off again and pressed and held the power and vol down switches to see if I got cwm. This showed LG screen for a few seconds and then the screen went off.
Now whatever I try to do I can only see the LG screen for a few seconds and then the screens goes off. No power on, no recovery, no nothing. And I can only attempt to even power on once, after the screen goes off I must remove the battery before the power button does anything again.
I tried to freshly nvflashing the recovery many times, but it made no difference. Does this mean my phone is bricked? Please tell me how I can solve this as I'm really worried.
NVFlashing the recovery again *should* have worked. So we first need to make sure you're trying to start CWM the correct way.
1) Unplug phone
2) Remove battery for 10 seconds.
3) Insert battery
4) Hold volume-down, do not let go, keep pressing it.
5) Press power button, keep it pressed.
If/when you get the second LG-logo, bluish halo, you can release both buttons, not before.
Nope, that was exactly what I was doing to access the recovery. I tried it again just now and it didn't work.
It just displayed the regular LG logo and then the screen went off. I'm not sure the phone completely shuts down 'cause if I keep it like that it gets quite hot and I can't use the power button again to try to power up. Only removing and re-inserting the battery gives me another attempt.
Is there any chance this is a hardware issue?
Hardly any chance this is hardware related if it was working before the first NVFlash.
Good, next step will be to NVFlash a complete stock ROM. You will unfortunately lose any data you might have on it, but that's the price to pay.
Go here, follow the instructions precisely, skip installation of apx-driver. Report back.
http://www.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
sean8000 said:
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
Click to expand...
Click to collapse
It works, yes, but is the original Froyo. This is just a way to get the phone up and running again.
Later you have a few choices. Either install CWM, then install you ROM of choice, or upgrade it to the latest for your region by using the LG Update tool.
EDIT. Oh, and btw, it is better to open a command-window and type the flash.bat command. If there are any errors you will still have them on-screen.
Thank you for all the help and support. I didn't get a chance to flash the rom till now (being on a vacation without a smartphone sucks). But I'll try it asap and report back.
So, how did it go?
TrymHansen said:
So, how did it go?
Click to expand...
Click to collapse
I haven't flashed it yet. I've decided to do it after I return home. I'm at my friend's house for 2 more days.
Ok, bad news. I flashed the stock rom you linked. The process went pretty smoothly. After the window got closed and the lg logo on the phone was visible 2 times, I unplugged it and installed the battery. But switching it on wasn't fruitful. It just displayed the LG logo for a couple of seconds and then the screen went off (just like before, only faster). I tried repeating the whole process, even tried to nvflash cwm once again, but nothing happened.
So is it a hardware issue? My phone is no longer in warranty period, so a hardware problem would be really bad...
So is it a hardware issue?
Click to expand...
Click to collapse
I don't know.
What would be helpful is to get a copy of the output you get when you NVFlash, it's simply the only way to verify that the flash process went ok. If you have an aborted flash it of course won't work, and may display the behaviour you describe.
EDIT: Btw, early on there were some ROMs which refused to boot properly unless the baseband was of an early variety as well.
If you feel confident the NVFlash has been successfull, smartflash an old baseband as well, see if it boots then.
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
gabriel2anjos said:
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
Click to expand...
Click to collapse
Now what's this "Jtag service"? (edit- I googled it and it seems to be a method of un-bricking stuff with specialized hardware or something, but I'm not sure I can have that done where I live)
Is there any way to fix the bootloader by myself?
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
sean8000 said:
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
Click to expand...
Click to collapse
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
TrymHansen said:
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
Click to expand...
Click to collapse
Ok, I'll try that when I have the time.
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
sean8000 said:
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
Click to expand...
Click to collapse
If it is you're only the second person in this forum to ever brick his phone. Anything's possible I guess. Some flash cells may have been damaged the first time the power was yanked. But then we should presumably get some verification errors during flashing.
Anyway, I'm at my wits end, and I really do hope you get it up and running, but I don't have anything more to contribute. Good luck.
Corrupted bootloader means that your cellphone simply don't know what to do when you hit the power button, due to the damage. As the cell phone can't turn, the pc can't recognize it. If your cell phone were a samsung, you could try to use a jig to have acesso to the download mode. But I don't know if it would work for a LG. You could try anyway.
And if you live at big city, usually it's common to have some jtag services.
Please, dont be afraid of hitting thanks
Please, dont be afraid of hitting thanks
Ok, so I took the phone to the service center today. The guys there said its battery terminals are messed up. They said replacement terminals are not easily available, but they'll try to find some. And of course I'll have to pay for it. I guess it's still better than using the phone as a paperweight.
What do you guys think?
Good luck I managed to mess up my phone like you too. I'm from India. But the difference was that I was covered by warranty. I managed to get a bunch of hardware replaced and was up and running again.
So my phone's not yet fixed since the 25th of December due to sudden death - http://forum.xda-developers.com/showthread.php?t=2585068
We had it checked again last Thursday, January 3rd. The technician said that the replacement of motherboard is not yet clear to be the best solution as the technicians from the Sony Service Center hadn't opened the phone yet. He said that it might have been a cause of a dead or death boot. Has anyone heard of it? He says not only Sony phones are experiencing this dead or death booth, even other brands. Kind of random.He said that the phone somewhat hangs, the screen isn't on but the system is still running which causes the phone to become warm or hot. And he also said that this lead to the battery getting totally drained. As per him, once the battery is totally drained it won't get charged even if I try to charge the phone for a number of hours. So what he will do when I get back to him on Monday is he will first try to shock the battery to see if it will be revived (which I hope this is just the case) and then dload some firmwares or softwares to fix the unit.
I hope this ordeal will be solved this following week as it's been so inconvenient on my part and I terribly miss my phone.
One of possibility is that they will open the back cover, pull out the battery and charge it to full, then they put it back and flash the stock firmware. With battery charged they have enough time for flashing and the phone should turn on. If it's Sony Center to do that they will also seal the phone as original to get fully working waterproof.
eclyptos said:
One of possibility is that they will open the back cover, pull out the battery and charge it to full, then they put it back and flash the stock firmware. With battery charged they have enough time for flashing and the phone should turn on. If it's Sony Center to do that they will also seal the phone as original to get fully working waterproof.
Click to expand...
Click to collapse
I really, really, really hope it'd work. For the waterproofing it would be fine to take it to the Sony service centre just to have the full waterproofness back.:good:
Just flash kernal from,any firmware by flash tool,and put your cell phone on charge.,it will charge... The same thing happen to me
Sent from my C6903 using xda app-developers app
shahzaib.khan said:
Just flash kernal from,any firmware by flash tool,and put your cell phone on charge.,it will charge... The same thing happen to me
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Flashmode not working and fastboot too the deviice is HARD BRICKED !!!
Meni30 said:
Flashmode not working and fastboot too the deviice is HARD BRICKED !!!
Click to expand...
Click to collapse
Have you managed to find a way to fix it?
I think my phone is hard bricked becuase its stuck on the Sony logo and my pc wan't detect it and none of the buttons work
SpawnCube said:
Have you managed to find a way to fix it?
I think my phone is hard bricked becuase its stuck on the Sony logo and my pc wan't detect it and none of the buttons work
Click to expand...
Click to collapse
Hey guys, do the devs a favour: NOT EVERY SIMPLE BOOTLOOP IS A BRICKED DEVICE!!!
Just go to recovery and wipe everything, it then should boot without problems.
if it doesn't, first check yourself (e.g. did you flash a 4.4 kitkat without flashing a new kernel for it?)
the answers for nearly all problems are here on xda-developers ... just read, read and read and understand ... if you don't know, what you do with flashing your device, what the partitions data / cache / system are for, what a kernel is or what the differences between stock roms, custom rom releases and nightly builds is, you simply SHOULD NOT flash your device.
If you understand what you are doing and if THAT ALL doesn't help you and you think you have a problem noone else have (i allready had such a thing with my defy+, it got bootloop and it was a dead memory chip) THEN (and just then) post your problem here. The devs simply don't have the time to help everyone who simply can't read the existing threads.
Thanks (and dont get angry on me, just saying so you can do it better the next time)
DJ_Synergy said:
Hey guys, do the devs a favour: NOT EVERY SIMPLE BOOTLOOP IS A BRICKED DEVICE!!!
Just go to recovery and wipe everything, it then should boot without problems.
if it doesn't, first check yourself (e.g. did you flash a 4.4 kitkat without flashing a new kernel for it?)
the answers for nearly all problems are here on xda-developers ... just read, read and read and understand ... if you don't know, what you do with flashing your device, what the partitions data / cache / system are for, what a kernel is or what the differences between stock roms, custom rom releases and nightly builds is, you simply SHOULD NOT flash your device.
If you understand what you are doing and if THAT ALL doesn't help you and you think you have a problem noone else have (i allready had such a thing with my defy+, it got bootloop and it was a dead memory chip) THEN (and just then) post your problem here. The devs simply don't have the time to help everyone who simply can't read the existing threads.
Thanks (and dont get angry on me, just saying so you can do it better the next time)
Click to expand...
Click to collapse
Thanks, you just said what I wanted to say.
Hello,
I was using Cyanogenmod 11 and suddenly (possibly after an update) my phone wouldn't charge anymore. I tried many different scenarios and it turns out that the phone only charged when my phone was either off or just booted and the screen not locked yet. From the second I locked my screen, my phone would stop charging.
Naturally, I assumed that this was a problem with the last CM update, so I flashed a new ROM (SkyDragon GPE). And now, it charges only when turned my phone is turned off. Very weird.
Is anyone familiar with this problem? Do I need to return it to the store? And if so, is it best to return to stock ROM etc before returning it?
IanWinz said:
Hello,
I was using Cyanogenmod 11 and suddenly (possibly after an update) my phone wouldn't charge anymore. I tried many different scenarios and it turns out that the phone only charged when my phone was either off or just booted and the screen not locked yet. From the second I locked my screen, my phone would stop charging.
Naturally, I assumed that this was a problem with the last CM update, so I flashed a new ROM (SkyDragon GPE). And now, it charges only when turned my phone is turned off. Very weird.
Is anyone familiar with this problem? Do I need to return it to the store? And if so, is it best to return to stock ROM etc before returning it?
Click to expand...
Click to collapse
Do not return it! I am not entirely sure wheter the Recovery is responsible for charging or not.
If you don't fear losing all your data or if you've already backed them up, do a full RUU. This works that way:
http://forum.xda-developers.com/showthread.php?t=2632736 and go to this section : "You want to have stock software again? No Problem" it is the last one before the first post ends.
This will get you to stock bootloader, recovery and OS. But pay attention you need a Win7 PC!
This way we can test wheter the issue also exists with stock software. if yes -> returning to the seller is an option. But for now you shouldn't do that.
LibertyMarine said:
Do not return it! I am not entirely sure wheter the Recovery is responsible for charging or not.
If you don't fear losing all your data or if you've already backed them up, do a full RUU. This works that way:
http://forum.xda-developers.com/showthread.php?t=2632736 and go to this section : "You want to have stock software again? No Problem" it is the last one before the first post ends.
This will get you to stock bootloader, recovery and OS. But pay attention you need a Win7 PC!
This way we can test wheter the issue also exists with stock software. if yes -> returning to the seller is an option. But for now you shouldn't do that.
Click to expand...
Click to collapse
Thanks for your reply LibertyMarine,
I'm afraid I already returned my phone. I couldn't even do anything with my phone anymore: the battery was dead and there was no way to charge it.
IanWinz said:
Thanks for your reply LibertyMarine,
I'm afraid I already returned my phone. I couldn't even do anything with my phone anymore: the battery was dead and there was no way to charge it.
Click to expand...
Click to collapse
That's ok. If the battery was really dead and you can't turn it on again, then the chances that the repairteam from HTC won't be able to turn it on again either are high. So if you get lucky they make the decision that replacing the device is cheaper than repairing it and in that case they may not find out that it has been rooted.
Otherwise they may charge your for having to replace your motherboard as it's against HTCs policy to send back an altered motherboard. Just hope they don't find it out.
Good luck!
So here's my problem. I think I've bricked my device. Don't know if it's softbrick or hardbrick, but either way my phone just does not boot up. The only instance it works is when I remove the battery and try to charge the phone, it shows a picture that it didn't find a battery. All of this occurred while trying to unlock the bootloader. Something similar already happened to me like a month or two ago, but I was able to flash stock KDZ using the online LG Support Tool. Anyway, the part where it all messed up is probably the aboot.bin file, although I'm quite certain I flashed the right file for my device. Also, installed CWM recovery, and after restarting the device it just won't boot at all, not even the software upgrade mode or anything. So my guess is that something is wrong because of either a wrong aboot.bin file for my D405N or the custom recovery. I tried flashing stock KDZ, but I couldn't get my phone into software upgrade mode. Also, tried doing a hard reset, but an LG logo didn't even come up. The battery is at least half full. So is there anything I can actually do in this case? Any help is appreciated.
P.S. Yeah, I did post in another thread (though I didn't create it), but I'm quite desperate with this. Either I fix it myself somehow, or I'll have to take it to the warranty.
EDIT: Took it to a repair. Should be done in around a week. Got an old Samsung Galaxy Mini as a replacement.
linasj said:
So here's my problem. I think I've bricked my device. Don't know if it's softbrick or hardbrick, but either way my phone just does not boot up. The only instance it works is when I remove the battery and try to charge the phone, it shows a picture that it didn't find a battery. All of this occurred while trying to unlock the bootloader. Something similar already happened to me like a month or two ago, but I was able to flash stock KDZ using the online LG Support Tool. Anyway, the part where it all messed up is probably the aboot.bin file, although I'm quite certain I flashed the right file for my device. Also, installed CWM recovery, and after restarting the device it just won't boot at all, not even the software upgrade mode or anything. So my guess is that something is wrong because of either a wrong aboot.bin file for my D405N or the custom recovery. I tried flashing stock KDZ, but I couldn't get my phone into software upgrade mode. Also, tried doing a hard reset, but an LG logo didn't even come up. The battery is at least half full. So is there anything I can actually do in this case? Any help is appreciated.
P.S. Yeah, I did post in another thread (though I didn't create it), but I'm quite desperate with this. Either I fix it myself somehow, or I'll have to take it to the warranty.
EDIT: Took it to a repair. Should be done in around a week. Got an old Samsung Galaxy Mini as a replacement.
Click to expand...
Click to collapse
Remember Next time Unlock Bootloader before Installing CWM.