Hey what's up all. I was listening to music in the car today and my G4 just turned off for no reason. Seems like it is completely hard bricked. I can only get the LG logo and Download Mode. No recovery or even a boot loop. Any options on recovering my data thru ADB or something similar? Can I re-flash the rom over ADB?
I'm really in a tough spot with this, never even heard of a random hard brick happening with this phone or any Android phone. Apparently it is a known issue, I haven't flashed anything in months. I was running stock rooted. Thanks for the help!
you can send it to data recovery lab, ask them to fix it for you. But it may cost you money.
Fix here http://forum.xda-developers.com/tmobile-g4/help/how-to-recover-data-boot-loop-defect-t3297766
- Sorry mods for the second thread, but since it's a solution that worked for me, I figured it deserved its own thread.
Related
Hey guys its been a while since I've even tried to fix my phone cause everyone was saying its dead. But I've been reading stories of people coming back from the G1 logo. So i could really use your help.
Heres the problem, A while back I dropped my old G1 and had to get a new one. Upon looking for the video I used last time to root my phone, I couldn't find it. I searched high and low but to no avail. I figured any video would work as long as it rooted me. So I started up the video. however once i was "done" with it i noticed nothing had changed. So i figured the video was garbage and found another one and started it up. I know, STUPID. Well when i booted my phone after wiping and flashing. It stayed on the G1 logo. I knew the worst had happened. So now i don't know what to do. There have been one or two occasions that I've gotten it to boot loader. So i know i can get there. but what do i do when I get it?
Also, no, I never got to flashing raido's or anything like that. I thought I wasn't rooted so i didn't move on.
I know it was long but I'm getting all the info out there. Please help, I think its possible, and if it is I want my phone back!!!
What were you installing by the way?
EDIT: Made a mistake, thought you were able to boot into recovery.
He does not get to recovery, but into bootloader mode (cam + power on). This is good, as there is a good chance to recover from that.
Try the first section of this guide:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
You have to flash the correct dreamimg.nbh via bootloader. You might need a Goldcard to do so, in certain countries, but lets just hope that is not the case (would be more work...)
€: Some more Info on Bricking your device with Radio/SPL updates, so take care: http://forum.xda-developers.com/showthread.php?t=655097
The guide on cyanogens wiki is considered dangerous at the optional update to HardSPL
hi everyone. i've been following the forum here for awhile and finally decided to root my brand new NC. i autorooted from 1.1. i saw some things weren't working so i quickly decided to unroot back to factory settings. i unrooted by unregistering the device and turning off the power 8 times. my NC boots up fine, but it gets stuck on the "Registering your Device" page and just remains there with the circle spinning. i think i left it there for more than 30 minutes and nothing happens. has anyone experienced this before? if so, how did you fix it? any help would be appreciated.
sorry if this topic has already been asked - i tried searching but didn't find anything on this specific issue. if there's already a thread, please feel free to share the link with me. thank you!
EDIT: really need some help here... i tried to fix it myself (i know i shouldn't have) and might have made it even worse. i tried to re-autoroot my NC but just completely failed. it was not loading anything anymore, so i tried to unroot again by powering off 8 times. when i restarted, everything looked normal, except the bootloader screen was not stock. it brought me back through the normal tutorial and same thing with it getting stuck on "registering your device". could someone please provide a thorough walkthrough on how to reset to factory settings? i'm seeing all these threads throwing around all these acronyms that i don't understand. seems like i need to try running some clockwork rom but not even sure how to do that. please help!!
Bump, i have just encountered this problem and i need help as well.
Update:
actually just figured it out and heres what fixed my problem, i wasn't doing the factory reset part only the 8 reboot interruptions.
hxxp://nookdevs.com/Flash_back_to_clean_stock_ROM
Thanks for your post, even though no one ever helped. I was having the same problem and doing a clear data/factory reset from Clockwork Recover booted from an SD card did the trick for me.
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.
Hi all,
I downloaded the latest TWRP from https://dl.twrp.me/i9305/ - twrp-2.8.7.0-i9305.img.tar 8.1M
I installed it with ODIN. The flash was a success and when the phone rebooted the touchscreen was unresponsive.
I have tried another version of twrp for this phone and I can get into twrp, but the touchscreen doens't work. I tried replugging in the ribbon lead for the digitiser and that made no difference.
Do you think its a software problem or that I have fried something?
Many Thanks
Andrew
Hi,
there are plenty of issues with TWRP and 2.8.7.0. I'm actually surprised you could even boot up your phone. The new recovery messes up with partition sizes and some other things.
I hope you have a backup of the current ROM as I suggest you to install Stock ROM again and stay on TWRP 2.8.5.0 and see if your phones works normally again
Hi,
thanks so much for replying. I still have the stock rom. All I have done is install twrp. I have tried doing a factory reset and it made no difference. I can still use the buttons on the phone, but the touchscreen remains unresponsive.
So if I download the stock rom for the phone and install you think it might make a difference?
Andy
Update:
Downloaded and installed stock rom from samsung (4.4) ... installed with success via odin. The phone boots and the screen is still unresponsive. I just cant believe I have broken the digitiser by installing twrp?!
Andy
Hi,
sorry for the late reply. I didn't get a notification via tapatalk. But anyway to come back to your issue: it's the first time I hear that a "corrupted" recovery could break the digitizer. I did the same mistake with the broken recovery but fortunately no issues afterwards. But apparently it's possible judging by some google search results.
I never had such issues and I don't know how to help you. Maybe there is a possibility to fix it.
Thanks for your reply
I hope there is a way of fixing it. It doesn't seem economical to fix this phone? The digitiser kit is around £60 ... Plus because I can't be 100% why this happened in the first place, it might happen again with a new digitiser?
Thanks
Andrew
I was looking here in Germany right now what I would have to pay for fixing the digitizer - between £50 and £60 as well, some even charging a little more. For £80 I could get a decent looking used S3 4G.
If I were you I'd rather buy another S3 again (or any other device) instead of trying to fix the broken one.
Did you tried to Flash stock recovery
Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?
Seems different?
Well I would try Odin and an official ROM anyway, no pain no gain right?
What exactly were you doing before this occured?
You try the old delete usb driver, restart computer, install usb driver then restart computer and restart phone and try again.
SirDigbyCC said:
Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?
Click to expand...
Click to collapse
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something
flairepathos.info said:
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something
Click to expand...
Click to collapse
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.
To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.
SapphireEX said:
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.
Click to expand...
Click to collapse
Oh I see the issue now you need to wipe all and re-flash full firmware when flashing the device using Odin
if that doesn't work flash the partitions with the kernel drivers and system partition
I had a similar issue with my current mtk phone and it was because the boot/preloader partition bilieved i had flashed the wrong firmware for my device(it was just a different firmware release for my phone
Just to be safe some ota updates break wehn the bootloader is not unlocked (when updationg from say android 8(oreo) -9(pie)...)
especially because of code errors in the update, cache/vendor partition being too full after downloading update
SirDigbyCC said:
To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.
Click to expand...
Click to collapse
If you're telling the truth, and it wasn't a bad module / firmware / etc, it is possible your eMMC got too hot and melted some solder. I've seen it happen before.
You'll want to diagnose everything you can. If you're on Windows, does it recognize a USB device or a COM device? If linux, does lsusb return anything useful about it?
If it's not being detected, and multiple wires doesn't change anything, are you able to access sahara mode / download / DFU? If so, go to those and try again.
If you are lying, and this is a bad firmware flash / OTA brick, you'll need to tell us otherwise we'll be going in circles.
So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?
SirDigbyCC said:
So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?
Click to expand...
Click to collapse
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.
SapphireEX said:
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.
Click to expand...
Click to collapse
I appreciate the vote of confidence, I don't think it was an OTA update that did it this time, it usually requests to do updates which I highly doubt I would have pocket approved through a flip case only short after pressing play on Spotify.
So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!
SirDigbyCC said:
So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!
Click to expand...
Click to collapse
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!
shriom_manerker said:
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!
Click to expand...
Click to collapse
It was free, turned out to be a hardware issue internally so I think covered by warranty as I have Care+ which has an excess of £40 which they didn't make me pay. They also replaced the screen due to some dead pixels, and the battery! Happy days!
Thanks all for your suggestions!