T-Mobile G1 almost DEAD or what to do ? - G1 Q&A, Help & Troubleshooting

I was updating my G1 to Kingxkxlick ROM & it was just stuck at screen of X, I tried to re-update it via RECOVERY, & I don't know but it restarted when I click to HOME for update.
When it restarts, it showed G1 & X logo, stuck there for a while, but THEN I TOOK OUT THE BATTERY
& It's no more working, not charging, not turning on, BATTERY WAS 100% charged
Please help me out, I don't wanna lose my g1, i'm not even in US right now

If you get to the boot screen and you've past the G1 logo, your phone is fine. Its the ROM you're trying to flash.
Make sure before flashing any rom that you do a factory data wipe, dev wipe, and make sure you have 3 partitions, swap, ext2-3-4,and fat
once you have done this, make sure youre using kingklicks 6.1 first, then upgrade to the 7
Kings 7 rom is only minor changes to add to the base 6.1, if you're trying to flash the newest update alone, if you notice its only 6MB which is definatly NOT the correct size a ROM should be.
So download the older version 6+ then flash, then without rebooting, flash update version 7 over it, and then reboot.
Hope that helps!

To be more clear than the guy above me...
Assuming your talking about this King rom.
http://forum.xda-developers.com/showthread.php?t=622170
Download 1.7
Download 1.7.1
Flash 1.7
reboot
Flash 1.7.1
What recovery do you have? Stock? Amon Ra? What SPL?
Can probably fix your phone if you answer those questions.

G1ForFun said:
To be more clear than the guy above me...
Assuming your talking about this King rom.
xxxx
Download 1.7
Download 1.7.1
Flash 1.7
reboot
Flash 1.7.1
What recovery do you have? Stock? Amon Ra? What SPL?
Can probably fix your phone if you answer those questions.
Click to expand...
Click to collapse
I've already told phone is not charging, not starting recovery or fastboot screen
I had Amon RA recovery, just had CyanogenMOD Latest one
Was changing it to Kingxkxlicks latest ROM & got it all done
Any hope for recovery OR what else Option I have ?
PS: Not in US

rawfire said:
I've already told phone is not charging, not starting recovery or fastboot screen
I had Amon RA recovery, just had CyanogenMOD Latest one
Was changing it to Kingxkxlicks latest ROM & got it all done
Any hope for recovery OR what else Option I have ?
PS: Not in US
Click to expand...
Click to collapse
If its not turning on, then I'm pretty sure it's dead. Needs a new board all together, I had the same thing happen to me, pretty much the same exact way. It was taking way too long to boot (20+ mins) so I took out the battery and now won't turn on at all. If you find a way to fix it let me know so I can revive mine.

dcontrol said:
If its not turning on, then I'm pretty sure it's dead. Needs a new board all together, I had the same thing happen to me, pretty much the same exact way. It was taking way too long to boot (20+ mins) so I took out the battery and now won't turn on at all. If you find a way to fix it let me know so I can revive mine.
Click to expand...
Click to collapse
I contacted some local repairers, they just told that it need to get it's boot reset by putting some wires & stuff on board to make it work again.
It's costing me too much so I haven't done it by yet (almost 5,000 PKR)
If anyone here know the thing I told, do let me know, I can do it by myself (can take risk), but can't spend that much money lol

rawfire said:
I contacted some local repairers, they just told that it need to get it's boot reset by putting some wires & stuff on board to make it work again.
It's costing me too much so I haven't done it by yet (almost 5,000 PKR)
If anyone here know the thing I told, do let me know, I can do it by myself (can take risk), but can't spend that much money lol
Click to expand...
Click to collapse
They trying to rip you off.. Nobody has got JTAG working on the g1 yet, they can't do anything by "putting some wires and stuff on board". If it won't charge and won't turn on, there's nothing you can do except replace the board.

goldenarmZ said:
They trying to rip you off.. Nobody has got JTAG working on the g1 yet, they can't do anything by "putting some wires and stuff on board". If it won't charge and won't turn on, there's nothing you can do except replace the board.
Click to expand...
Click to collapse
what's the lowest price I have to pay for motherboard of G1, because it's not available in local market by now ?

You won't find the mainboard for sale anywhere, so your best bet is to search ebay for a g1 with a broken screen.. then you can swap in the board from that and keep the rest of the parts as spares:
http://cgi.ebay.com/T-Mobile-G1-Bro...Cell_Phones?hash=item2eabb4e988#ht_500wt_1182
edit: before you go swapping the board.. have you tried a different battery? it could be as simple as that.

Related

UK G1 bricked after installing Shop savvy - help please

Hi guys,
UK G1 (Dream) phone recently updated to the 1.6 build, all working fine.
Yesterday I tried installing the free app Shop Savvy. the phone resetted itself after install and sat on the G1 boot screen permanently.
Now phone will pass this boot screen (Tmobile G1)
Tried:
Recovery mode - will not work at all
Quick boot - brings up the multicolour screen but does nothing after.
**PHONE IS NOT ROOTED**
looks like I have had the phone JUST over a year, not looking good...
Any ideas?
You can boot in to the SPL/bootloader so thankfully you haven't bricked
If you're on a contract with tmo you could take it back to the store and they should give you a replacement, but where's the fun in that?
If you want to fix the problem yourself, all you need to do is downgrade to firmware 1.1, then accept the OTA update to 1.6.
Here's the procedure:
1)Put the phones SD card in to a card reader and format as fat32
2) Extract this file and copy it to your SD card as 'DREAIMG.nbh'
3) Put the card back in the phone and hold down power and camera to boot in to the bootloader.
4) Flash it. (Action button is the trackball).
It's a good idea to leave the charger plugged in and have a decent amount of charge in the battery (eg 40%+).
Afterwards the phone will restart and you will need to re-enter your google account info. All your apps and data will be gone, but there's not much we can do about. You can set things up and install apps while you wait for the prompt to update.
Thanks alot AdrianK,
Really appreciate the steps and info, nice one
I have done some flashing on other phones etc so I have no problem with this. However, I am wondering how a normal app such as Shop Savvy could corrupt my ROM and am wondering if it might not be better to get a new phone as this one could have hardware fault?
What do you think?
Silver.
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
SilverfoxUK said:
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
Click to expand...
Click to collapse
I think you can take the battery out restart the phone
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Once you get to RC7 use these to build back upto 1.6
http://code.google.com/p/official-android-firmware/downloads/list
SilverfoxUK said:
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Click to expand...
Click to collapse
Yeah that's the RC7 ROM, the UK ROM for 1.1. RC29 is 1.1 for US phones.
This is all very odd, especially that it was an app that caused it, or as you suggested possible hardward failure. Oh well, I guess all you can do now is take it back to tmo.

need confirmation of bricked g1 or not

ok so i got my hands on my sisters old G1 and it was unrooted and with rc30.
so i was able to downgrade it to rc29, flash it with RA recovery 1.7.0, and i was applying the the spl next. i booted into recovery and flashed the spl, and when i rebooted the g1 i just got suck at the tmobile g1 screen, i left it there for like 10 minutes thinking its gonna do its thing but it was still stuck there.
i pulled the battery out and pressed home and the power button, and it still didnt wanna go into recovery. so i pulled the battery again. so pressed and held the camera button and power button and it booted into the g1 screen instead!
so at this point i think i bricked it since im just stuck at the g1 screen and cant do nothing from there and i wanted a 2nd opinion to confirm it, or for a possible solution.
im thinking i messed up with the spl, but the one i have DL is the same one i used with my old G1 and its still kicking some (this one has a problem with the flex ribbon cable i believe, but completely usable.)
Im pretty sure when a phone is bricked, you cant even boot your phone, so im pretty sure ur phone is not bricked.
sorry, idk how to fix this, but im sure someone does.
You have to flash a rom, of coursebit would get stuck at g1 screen bcuz it had no direction(no rom)
Sent from my HTC HD2
the situation is you can get into hboot but not recovery nor system,right?
you could flash radio/spl via fastboot ,then flash recovery, rom at last.
read this thread:http://forum.xda-developers.com/showthread.php?t=532719,try to fix it
edward0119 said:
the situation is you can get into hboot but not recovery nor system,right?
you could flash radio/spl via fastboot ,then flash recovery, rom at last.
read this thread:http://forum.xda-developers.com/showthread.php?t=532719,try to fix it
Click to expand...
Click to collapse
no i cant access recovery, or hboot.
when i hooked it up to the computer hoping that it might recognize it, nothing happened either when i tried to boot into hboot, or recovery.
so ive been doin some more digging into the internet and yep i did end up bricking it.
looks like im gonna perform some phone operation between the two g1s to have a fully working one.
so pressed and held the camera button and power button and it booted into the g1 screen instead!
you said this last day,it doesn't work now?
edward0119 said:
you said this last day,it doesn't work now?
Click to expand...
Click to collapse
no it doesnt.
i have no access to hboot, or recovery. and it doesnt get recognized by my computer if i try to have it hooked up with the usb, so i cant even use adb or nothing.
so like i said, i could pretty much confirm myself that i bricked it. so right now im like phoneless because my original g1 has an issue with it not showing nothing if the keyboard is CLOSED (yes closed, not open! lol) and it ended up closing on me when i tossed it in my bed (doh!)
damm that sucks man.. sorry for your loss lol
ldrifta said:
damm that sucks man.. sorry for your loss lol
Click to expand...
Click to collapse
haha its alright, only option right now is phone operation with the two g1s i have, but i need to buy a torx screwdriver for it since the one i got is the wrong size.
but its not such a bad thing because ive been hearing that i might end up getting a new HTC phone as a graduation present. so heres to hoping thats true! lol
I guess it is bricked,maybe it can be fixed by a serviceman
Well seeing it's screwed lol try out JTAG used it before to unbrick a phone once ^^ that should be a solution for you
xillius200 said:
Well seeing it's screwed lol try out JTAG used it before to unbrick a phone once ^^ that should be a solution for you
Click to expand...
Click to collapse
yeah i was looking into that, but idk it seemed wierd for me.
but last night i opened up the g1s and replaced the motherboards from eachother. and now i got a working g1!

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

I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.
Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.
Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick
Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App
Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G
Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.
You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.
Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed

[Q] Optimus black stuck on firmware update screen

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..

[Q] Please help me, is my phone bricked?

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.

Categories

Resources