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
Related
So i am a complete idiot and just bricked a phone yesterday and luckily managed to get it exchanged at att.
The new one is having tons of trouble getting into download mode using the button combinations. I wanted to load the I9000 euro roms as I had successfully done to my previous phone. I did the first step in loading the csc and pda files and accidently forgot to uncheck autoreboot. Anyways... I pulled the battery out before it could reboot. I still couldnt get it into download mode so I booted into the android without applying the second step of the pit fil and the modem file. I am not used to using the sdk so was planning to root and intall a terminal program to "su reboot download"... I tried using the oneclick root to complete the job and it rebooted me into recovery, but apparently since i didnt flash the pit file, my power button doesnt work to access the menu..(volume rocker does).
Now it wont boot into anything except into recovery and I cant do anything about in it.... i have tried everything on oneclick odin instructions and can not get there... is there anything i can do from the sdk to get into download mode... it kind of appears that my phone is recognized when i plug it in cuz windows beeps saying that it recognizes the device...
HELP ME PLEASEEEEE
I THINK I DESPERATELY NEED TO GET INTO DOWNLOAD MODE SOMEHOW!!!
I HAVE TRIED EVERY WAY LISTED ON
http://forum.xda-developers.com/showthread.php?t=731989
use method 3
Wrong forum, but how in the world did you "brick" your last phone? These phones from what lots of smart people say are not brickable, and these guys on here have tried. And if you did in fact brick your old phone why would you decide to put another ROM on?
First calm down. If it boots you are ok.
You can do what Akachay said. Or pull the battery unplug the usb. Start odin put the battery back in hold down both volume keys then plug in the usb cable it should boot into download mode.
It is very hard to brick this phone
IllegalOpcode said:
First calm down. If it boots you are ok.
You can do what Akachay said. Or pull the battery unplug the usb. Start odin put the battery back in hold down both volume keys then plug in the usb cable it should boot into download mode.
It is very hard to brick this phone
Click to expand...
Click to collapse
Do this. The phone has to be off. Hold both volume buttons and plug in the usb. It will into dl mode. No power button necessary.
Sent from my SAMSUNG-SGH-I897 using XDA App
IllegalOpcode said:
First calm down. If it boots you are ok.
You can do what Akachay said. Or pull the battery unplug the usb. Start odin put the battery back in hold down both volume keys then plug in the usb cable it should boot into download mode.
It is very hard to brick this phone
Click to expand...
Click to collapse
I second this method. Calm down and take your time. It WILL work trust me ive used it a few times on both my captivate and vibrant.
Sent from my SGH-T959 using XDA App
I third that the volume button method.... I pull the battery, reinstall it, plug in usb, hold down volume buttons. Works every time. Any other method is a total crap shoot.
If using Odin make sure its open before you do this so that it will recognize the connection.
If you can talk to the phone with adb you can also try "adb reboot download".
Good luck.
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks so much to the help and support... seriously the buttons for download mode did not work... had to learn the adb sdk method
Sent from my SAMSUNG-SGH-I897 using XDA App
xmarkx88 said:
Thanks so much to the help and support... seriously the buttons for download mode did not work... had to learn the adb sdk method
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Its always a good skill to know
This is not the Q&A section of the captivate...please next time UTFS of this lovely forum, and post it on the right section.
Rafyvitto
flashman2002 said:
Wrong forum, but how in the world did you "brick" your last phone? These phones from what lots of smart people say are not brickable, and these guys on here have tried. And if you did in fact brick your old phone why would you decide to put another ROM on?
Click to expand...
Click to collapse
Why do people say its impossible to completely brick the phone? Unfortunately I did it due to stupidity, and it bricked quite easily.
Coriolis3ffect said:
Why do people say its impossible to completely brick the phone? Unfortunately I did it due to stupidity, and it bricked quite easily.
Click to expand...
Click to collapse
People say that because the word "brick" is thrown around quite liberally. These phones have been nearly impossible to legitimately brick. About the only way I can think of is spontaneous hardware failure
OP, I thought I bricked it yesterday but d/l method works, don't worry...
moving my own issue here as i think i really HAVE bricked the phone. did alot of reading but apparently still did it wrong. flashed the PIT file only to the phone and now ive got a lovely and not very heavy paperweight. does not even turn on using the power or volume combo even after i pulled the battery for 5 minutes. Any clues? im pretty sad about this.. read that its pretty hard to brick these phones but im not so sure that is the case
ill also mention i was being dumb and didnt realize i was on the i9000 page reading instructions at the time. i was using the instructions from here http://forum.xda-developers.com/showthread.php?t=765032 and the problem occured after i flashed the pit successfully and then was resetting the battery when i found out it was completly dead
bamonkey said:
ill also mention i was being dumb and didnt realize i was on the i9000 page reading instructions at the time. i was using the instructions from here http://forum.xda-developers.com/showthread.php?t=765032 and the problem occured after i flashed the pit successfully and then was resetting the battery when i found out it was completly dead
Click to expand...
Click to collapse
Seems lately over on the odin3 page alot of people are doing dumb things just like me. looks like ill be able to return it in the next few days but i just want to stress that while people are stating its really hard to brick these phones i would NOT recommend doing any kind of firm flashes unless you are totally comfortable with exact instructions or turning your phone into a complete brick and getting a warranty exchange. I hate to say it but im a little unsure of myself on these firmware upgrades now. its not really a click-and-be-done process yet so i think ill just hold out and hope the froyo upgrade fixes the gps issue because otherwise i still love this phone
First, thanks for the look.
Second, I have read the related threads to this, but none are like my special situation.
Twice I've had to get a warranty replacement for my Captivate after trying to restore from ODIN. Both times, the restore starts, then freezes mid-process. I've let it sit for an hour both times and nothing changes. Frozen. I have no choice but to unplug the USB cable, and remove the battery. The phone is then dead. I mean DEAD. Powered off & completely unresponsive. No power on. Screen doesn't light. "USB device is not recognized" when plugged into a PC w/ drivers. NODA. KAPUT.
I've successfully flashed w/ ODIN before, so I have no idea why certain times it decides to stop.
I'd like to use Clockworkmod to flash in between roms, but after re-flashing I always get the boot loop (AT&T screen is as far as it gets.) I try re-flashing to the original ROM, a backup of the stock ROM. Nothing works.
I REALLY don't want to try and get a 4th warranty phone if this happens again.
I know Clockworkmod requires a compatible ROM, but I've never seen one (Perception, Cognition etc.) that says it is. I know you need a backup of the nanroid, but isn't Clockworkmod supposed to do this?
Can someone straighten me out so I don't get yet another bricked phone?!
Thanks.
EDIT: Basically, I can flash a custom ROM just fine using Clockworkmod. Except when ODIN decides to be a *****, I can flash the stock ROM back, then another custom ROM. I want to flash from one custom ROM to another (or a backup of the stock ROM) without having to rely on a program that's bricked my phone twice!
Thanks again.
had this happen to me one night while trying to change roms. I used ROM Manager to flash back to a stock backup I made and stuck at ATT logo. got the phone into download mode and it would go a little then the screen would turn green or blue or orange, sometimes black and freeze running odin. I just kept at it, leaving the battery out for different intervals, holding volume keys with usb plugged in and then inserting battery. took about 30 tries but it finally took and odin flashed me back to stock. Just don't give up, try try again...you may get lucky
Development, I think not
Sent from my SGH-T959D using XDA App
bulletproof1013 said:
Development, I think not
Sent from my SGH-T959D using XDA App
Click to expand...
Click to collapse
Well, i figured since it was about ROMS it would belong here.
If there's a better place then move the thread.
bulletproof1013 said:
Development, I think not
Sent from my SGH-T959D using XDA App
Click to expand...
Click to collapse
NOTHING like throling auseless thread int he wrong section ... except we ve been politely asked by the admins to stop doing it so I will refrain from doing it ..
to answer you question , it seem like
the usb port/ card or even motherboard , ( might also be a bad usb cable) is at fault here , if you have a jig ( witch I advise you to build one asap if your into flashing roms ) I would never leave my phone plugged in to my pc when somethign is not responding . for example when flashing a kernel or even back to stock I know exatly how long thisi suppose to take and if its hanging I will unplug it and use the jig to go back in download mode and restart again , if your more cautious ten me then dotn , but nothing takes longer then 5 minuttes to flash on your phone so if by 10 minutes i dont work then your screwd so not worth letting your phone drain its battery ..
btw any questions belong in q&A no matther how relevant they are .
Without meaning to be rude, have you consider how reliable the computer you're flashing from is?
If you've seen the same behaviour twice, flashing two separate phones, then it seems likely that there's something specific either to the PC hardware (cables, ports), software (Odin, downloaded ROM, USB drivers) or method (human error of some kind) you're using.
Is there anything about your setup which might interrupt data on the USB line to the phone as it's being flashed?
Hope this helps,
AoN
i read on another forum somewhere that you cannot flash a stock backup from rom manager over a custom rom. that rom manager does not back up the kernel/modem etc...not sure how true it is, but I know the only time this ever happened to me was when I flashed a stock backup from ROM manager over a custom ROM.
DAGr8 said:
NOTHING like throling auseless thread int he wrong section ... except we ve been politely asked by the admins to stop doing it so I will refrain from doing it ...
Click to expand...
Click to collapse
For every non-development thread that is posted, one actual relevant thread gets bumped to page two. It hurts development, our at least slows it down.
Of course, that doesn't mean you should be rude or anything.
Sent from my GT-I9000 using XDA App
Also, if you're not doing it already, make sure you plug your USB cable into a USB port that is directly attached to your motherboard. Like the ones in the back. Many people have had issues using the front side USB ports or even going through a USB hub.
Also I guess it's worth it to reinstall drivers and do the normal windows type troubleshooting.
Ok guys, I feel this is just the end of the games... I was flashing back the Roto JME fw with the swype keyboard issue fixed that I have just made, when I accidentally unplugged the tab while starting flashing and in downloading mode.
Now all I get is a logo with a phone an alert symbol and a computer .
Windows as well as Odin see it, but I can't do anything, as Odin hangs on waiting for connection, or something like that.
Is there anything I can do?? Or do I really have to take it to the warranty? And if I will have to take it to the warranty will they see I have previously flashed a beta rooted image on it??
Here's what I am talking about
Please I need some help..
Thanks
Is there no recovery mode by buttons like the captivate? I hate seeing all the bricks
Sent from my SPH-P100 using XDA App
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...
Segnale007 said:
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...
Click to expand...
Click to collapse
Ops, it was the driver... damn windows ...
Solved btw.. I just realized I have lots of things to learn ... I have almost died of heart attack when I saw my tab stucked on that logo.. and now its back again..
Thank u falks
You need to make sure samsung kies are not running for sure unistall it and try it again
use odin. that is still download mode. might take you a couple of tries but works. i was in your shoes the other day
Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Segnale007 said:
Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
I've heard plenty of goofy stories about bricking devices over the years. You must conclude the following:
1.Flash your device in a locked room to avoid your wife/ child pulling cables or pressing buttons.
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
3.Read instructions carefully and write the procedure out in your own words if its your first time.
I've been flashing for years and haven't had a brick yet. Not crossing my fingers either because it has little to do with luck and much to do with care. In this way its a lot like making babies...
ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Good advice.
My only semi-bricks (that involved an hour or two of trial and error to unbrick) resulted from some manner of overzealous cable unplugging.
zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
This is what I have done
Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse
ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Well, first of all thanks for ur nice words. Let me just say that I was about to disconnect another device from the hub where the GTAB was attached and flashing at that time, and yea, I accidentally unplugged the GTAB instead of the other device. I may be a moron, thanks, and thankfully not everyone believes themselves as god, which is a good reason to not help other people who are in troubles, even if for stupid things sometimes... If everyone were thinking like u we were probably still at the age of 1400 ...
Mate it wasn't a barb directed at you personally, but you weren't exactly careful were you?
I'm no god... but I've never bricked a device either, and I've been flashing for over five years now. To top it off I've almost never owned a device which could be taken back to the shop (90% of them come from other countries, not my local retailers). Perhaps this has taught me to be careful.
In any case, what I said holds true, and if you ask around I'm certain you find most will agree.
Dude, you have the best avatar! I can't keep my eyes away! Good luck, and don't worry about mistakes - that is one reason this forum exists.
Cannot start my Gtab after trying update JMC
...Hello everybody,
I am really worry about the fact my Gtab doesn't want to switch on after trying to flash it. I tried all process to put it on download mode or recovery but nothing work.
Do you have any idea about it ? Is there a specific procedure to switch on (eg : press power for 1 minutes + blablabla).
My provider doesn't want to take my Gtab in warenty before my contract is activated (the 4th of february).
Thank you for your answer
HELP, I have same problem, please explain how Hemidall can fix it?
Thanks
[email protected]
zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
I also had a semi-bricked VZW Tab, with the phone-triangle-computer warning graphic at start up. (I flashed a new boot loader, and failed to read the instructions closely enough. Either the file was incorrect for my device, or the drivers were not loaded correctly, but my tablet was borked.)
Using heimdall 1.3.2 (with the correct drivers, on a 32-bit windows system), I clicked the "close pc screen" option to clear the warning.
I then held the power button until it turned off, then held vol+ and power to re-enter download mode. Once in download mode, I used heimdall 1.1.1 to flash the zImage from SCH-I800-Stock-Rooted-2.3.5. My tablet (still unrooted, and still stock?) booted, but sat at the SAMSUNG logo for ten minutes or more. (It announced its progress, telling me periodically "five minutes remaining", etc.)
Once it finished, my tablet was revived. I will now follow the above advice and read all instructions very carefully, re-writing them in my own words to ensure I understand what I'm doing, before I try this again.
One year old thread......do you guys ever watch posting dates???
Sent from my GT-P1000 using Tapatalk 2
...like REALLY bricked
bumping this old thread in hopes that someone can point me in the right direction...
Got my p7510 (10.1" wifi retail) stuck pretty badly when trying to restore stock ROM coming from Overcome (it came rooted from ebay). From what I gather from the forums, seems like my bootloader is still locked.
whenever I attempt to flash a BOOTLOADER, PIT, or PDA using ODIN it connects, initializes, and gets stuck on "Flashing boot.img"
I think the recovery partition is damaged. When I boot using Power + Volume Down, I can get to the screen where you select recovery mode or download mode but recovery mode will not load. The screen flickers when I select recovery, but goes nowhere. Download mode works.
I tried using nvflash to force the right software onto it but I get error 0x4 (usb write failed).
There has to be a way to restore the stock bootloader and get this thing running again. Tablet will not boot android at this point. I have been searching the forums for about a week now, anyone have any ideas?
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.
I am running Infected's CM12.1 ROM on my Yuga, and it's been working great, but just yesterday, my phone restarted without warning and optimised all the apps (200 of them), right when it says "starting apps", it restarts again and did this until the battery drained out.
I cannot enter recovery at all. I have TWRP installed on the FOTA partition, but I cannot access that. When I'm holding the volume down key on the reboot, it just skips straight to the CM logo.
While it's optimising apps, I can see the phone in adb, but it's unauthorised, so I cannot run any commands to it.
I can reboot the phone into fastboot, but apart from reflashing the boot.img (which I already did) I don't know what else to try.
I think all the buttons are working, but I saw that the water pads are red underneath two of them. I think there may be water damage, but am not sure.
I'm out of ideas and would very much appreciated if anyone can help me bring my beloved phone back.
Lohot said:
I am running Infected's CM12.1 ROM on my Yuga, and it's been working great, but just yesterday, my phone restarted without warning and optimised all the apps (200 of them), right when it says "starting apps", it restarts again and did this until the battery drained out.
I cannot enter recovery at all. I have TWRP installed on the FOTA partition, but I cannot access that. When I'm holding the volume down key on the reboot, it just skips straight to the CM logo.
While it's optimising apps, I can see the phone in adb, but it's unauthorised, so I cannot run any commands to it.
I can reboot the phone into fastboot, but apart from reflashing the boot.img (which I already did) I don't know what else to try.
I think all the buttons are working, but I saw that the water pads are red underneath two of them. I think there may be water damage, but am not sure.
I'm out of ideas and would very much appreciated if anyone can help me bring my beloved phone back.
Click to expand...
Click to collapse
Have you tried flashing stock FTF ?
You would need FTF from general section and also flashtool which you can get from here. Make sure the FTF is device specific or your would end up bricking up your phone
http://www.flashtool.net/index.php
You can search xda for how to use it. If you still have questions, quote me and I would be glad to help
Hi,
Thanks for helping me out. I tried reflashing a few different ROMs using flashtool, including stock, but nothing helped.
In the end, I bit the bullet and gave it up for dead. The good news was, since the cause seemed to be water ingress, it was covered by my insurance, and so I was given a replacement!
Thanks again for your help.
Hnk1 said:
Have you tried flashing stock FTF ?
You would need FTF from general section and also flashtool which you can get from here. Make sure the FTF is device specific or your would end up bricking up your phone
Click to expand...
Click to collapse
Lohot said:
Hi,
Thanks for helping me out. I tried reflashing a few different ROMs using flashtool, including stock, but nothing helped.
In the end, I bit the bullet and gave it up for dead. The good news was, since the cause seemed to be water ingress, it was covered by my insurance, and so I was given a replacement!
Thanks again for your help.
Click to expand...
Click to collapse
There's nothing sweeter than using a phone for a long time and getting a brand new !
Enjoy mate. No trouble. Just quote me again in case you have any query for me.