Related
I need some major help.
My Verizon Note 3 was rooted but nothing else special. Recently, it started locking up when I turn it on in the morning, had to remove the battery and restart. Sometimes the power button would stop responding. And finally, after a phone call, it restarted itself and gave me a message "Could not do normal boot." Please see pictures.
It would not go into the recovery mode, but would always go to the Fastboot mode (Download mode). I tried Odin but no success. I talked to Samsung and the rep said that's what happens when you root (standard BS), but still allowed me to send it in. I got it back a week later, not fixed, but with paperwork saying Warranty Void due to Root.
I've been searching everywhere to see if I can find some information on how to recover from this, to no avail. I've installed the correct USB drivers many times, but neither ADB Devices nor Fastboot Devices commands will find anything attached. Odin continues to fail, sometimes with a message saying "Erasing Userdata partition" or something like that. It wouldn't show when I was taking pictures to post here.
Any suggestions or ideas? Again, no access to Recovery. Odin failes with or without the PIT file.
Thank you in advance.
FreaKaDroidXYZ said:
I need some major help.
My Verizon Note 3 was rooted but nothing else special. Recently, it started locking up when I turn it on in the morning, had to remove the battery and restart. Sometimes the power button would stop responding. And finally, after a phone call, it restarted itself and gave me a message "Could not do normal boot." Please see pictures.
It would not go into the recovery mode, but would always go to the Fastboot mode (Download mode). I tried Odin but no success. I talked to Samsung and the rep said that's what happens when you root (standard BS), but still allowed me to send it in. I got it back a week later, not fixed, but with paperwork saying Warranty Void due to Root.
I've been searching everywhere to see if I can find some information on how to recover from this, to no avail. I've installed the correct USB drivers many times, but neither ADB Devices nor Fastboot Devices commands will find anything attached. Odin continues to fail, sometimes with a message saying "Erasing Userdata partition" or something like that. It wouldn't show when I was taking pictures to post here.
Any suggestions or ideas? Again, no access to Recovery. Odin failes with or without the PIT file.
Thank you in advance.
Click to expand...
Click to collapse
Sounds like the flash memory may have failed in some manner. Two words: Warranty replacement. Getting a replacement through Verizon is usually fairly simple once they realize they can't try and fix it by pressing factory reset in the settings. Did you try Verizon first or go straight to Samsung?
Edit: Nevermind, I just realized it says you are "Custom." My reading skills suck tonight. Maybe you can convince someone at Verizon that you tried some stuff on the internet to fix it and then it said custom. I don't know if a JTAG would help or not in this case. Maybe someone can chime in on that...
FreaKaDroidXYZ said:
I need some major help.
My Verizon Note 3 was rooted but nothing else special. Recently, it started locking up when I turn it on in the morning, had to remove the battery and restart. Sometimes the power button would stop responding. And finally, after a phone call, it restarted itself and gave me a message "Could not do normal boot." Please see pictures.
It would not go into the recovery mode, but would always go to the Fastboot mode (Download mode). I tried Odin but no success. I talked to Samsung and the rep said that's what happens when you root (standard BS), but still allowed me to send it in. I got it back a week later, not fixed, but with paperwork saying Warranty Void due to Root.
I've been searching everywhere to see if I can find some information on how to recover from this, to no avail. I've installed the correct USB drivers many times, but neither ADB Devices nor Fastboot Devices commands will find anything attached. Odin continues to fail, sometimes with a message saying "Erasing Userdata partition" or something like that. It wouldn't show when I was taking pictures to post here.
Any suggestions or ideas? Again, no access to Recovery. Odin failes with or without the PIT file.
Thank you in advance.
Click to expand...
Click to collapse
Have you tried factory reset from Android Recovery (vol up, home, pow)?
I haven't run into anyone yet who couldn't undo soft brick from Odin... My only suggestion would be to start from scratch and follow the link in my sig...
I know you said you d/l sammie usb drivers a few times, try uninstalling ANYTHING on your pc from control panel>uninstall programs that says Samsung... THEN download and install newest drivers...
If following the guide in my sig doesn't bring you back, you'll be the first! Best of luck!
I'll try those things. I cannot go into recovery unfortunately. It just says "Recovery Booting" to get my hopes up, and then says "Could not do normal boot." Next line "ddi : mmc_read failed". Then goes into the ODIN Mode.
I'll report back after I try your suggestions... Thank you.
az_biker said:
Have you tried factory reset from Android Recovery (vol up, home, pow)?
I haven't run into anyone yet who couldn't undo soft brick from Odin... My only suggestion would be to start from scratch and follow the link in my sig...
I know you said you d/l sammie usb drivers a few times, try uninstalling ANYTHING on your pc from control panel>uninstall programs that says Samsung... THEN download and install newest drivers...
If following the guide in my sig doesn't bring you back, you'll be the first! Best of luck!
Click to expand...
Click to collapse
Unfortunately it did not work. Same message on the phone "MMC: mmc_read fail", and in ODIN:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried it with and without the PIT file and both the same result. Do you think this may be an actual hardware flash memory failure? Is there a way to format around the bad portion of the flash memory? I wish I could try some adb or fastboot commands but it does not show in either.
Any other thoughts or suggestions would be very much welcomed and appreciated. There's gotta be a way...
FreaKaDroidXYZ said:
I'll try those things. I cannot go into recovery unfortunately. It just says "Recovery Booting" to get my hopes up, and then says "Could not do normal boot." Next line "ddi : mmc_read failed". Then goes into the ODIN Mode.
I'll report back after I try your suggestions... Thank you.
Click to expand...
Click to collapse
FreaKaDroidXYZ said:
I'll try those things. I cannot go into recovery unfortunately. It just says "Recovery Booting" to get my hopes up, and then says "Could not do normal boot." Next line "ddi : mmc_read failed". Then goes into the ODIN Mode.
I'll report back after I try your suggestions... Thank you.
Click to expand...
Click to collapse
Pull battery in between attempts, and try diff usb ports on pc too
Notorious 3
No success...
az_biker said:
Pull battery in between attempts, and try diff usb ports on pc too
Notorious 3
Click to expand...
Click to collapse
If you can't even get to odin without mmc read, maybe it is your memory. Sorry I couldn't help, can't beat hardware failures. .Best of luck
Notorious 3
not sure it would help but will it safe boot
power plus hit the menu button
Thank you for your inputs. I wish Samsung would've done a bit more than to just reject it with a Fail Description as "Device Rooted." I've been a loyal Samsung fan til now.
az_biker said:
If you can't even get to odin without mmc read, maybe it is your memory. Sorry I couldn't help, can't beat hardware failures. .Best of luck
Notorious 3
Click to expand...
Click to collapse
Unfortunately it goes straight into the Download mode no matter what I try...
NinCaptain said:
not sure it would help but will it safe boot
power plus hit the menu button
Click to expand...
Click to collapse
try the pit file by itself??
lol @ Samsung. That's NOT what usually happens when you're rooted. There's quite a large percentage of us that are rooted with zero issues...shame on them for not replacing it.
Anyway, are you sure you were *only* rooted? You didn't try to flash a ROM or mess with partitions?
And it's vol down + home + power for recovery. Did you pull the battery first before going into recovery?
PS - don't bother with fastboot, this device does not have fastboot enabled, only Odin. You're not gonna get a response that way regardless.
Yes. Tried that. There's only 1 Verizon PIT file I found anywhere. Would a different PIT file work?
oneandroidnut said:
try the pit file by itself??
Click to expand...
Click to collapse
I know, I've been rooting for years, many Samsung S3, S4, Note 2 and 3's. But I wasn't gonna argue with the low-tech rep when she was gonna let me send it in. I was hoping for a motherboard replacement but that did not happen.
Yes, I "only" rooted. I was just about to do some more because of other issues (like the power button and the locking up first thing in the morning) when this happened. I never expected anything I couldn't undo via recovery or ODIN or something I can find on XDA...
I've tried VolUp+Home+Power, VolDown+Home+Power, VolUpDown+Home+Power, just about all combinations, always with a battery pull. It always goes to the Download mode... I cannot get into Recovery. Tried all 4 of my USB ports with a few different USB cables. Tried my Windows 7 laptop and my iMac.
siciliano777 said:
lol @ Samsung. That's NOT what usually happens when you're rooted. There's quite a large percentage of us that are rooted with zero issues...shame on them for not replacing it.
Anyway, are you sure you were *only* rooted? You didn't try to flash a ROM or mess with partitions?
And it's vol down + home + power for recovery. Did you pull the battery first before going into recovery?
Click to expand...
Click to collapse
FreaKaDroidXYZ said:
I know, I've been rooting for years, many Samsung S3, S4, Note 2 and 3's. But I wasn't gonna argue with the low-tech rep when she was gonna let me send it in. I was hoping for a motherboard replacement but that did not happen.
Yes, I "only" rooted. I was just about to do some more because of other issues (like the power button and the locking up first thing in the morning) when this happened. I never expected anything I couldn't undo via recovery or ODIN or something I can find on XDA...
I've tried VolUp+Home+Power, VolDown+Home+Power, VolUpDown+Home+Power, just about all combinations, always with a battery pull. It always goes to the Download mode... I cannot get into Recovery. Tried all 4 of my USB ports with a few different USB cables. Tried my Windows 7 laptop and my iMac.
Click to expand...
Click to collapse
Looks like you've done everything I would do. Maybe list it on Craigslist or swappa as 'dev project' or 'for parts' and get something out of it? Sorry to see you stuck like this.
Notorious 3
I had the same issue, try the steps below:
If your able to go into recovery factory wipe everything (if not go to the next step)
Flash the pit file by itself,
After flash is successful reboot and go straight into recovery, wipe everything
go into download and flash the stock firmware
If this doesn't work also re-download the firmware and pit using a windows PC, I've had issues with Macs download the correct file... Hope this helps, I had the same issues as you, in the end I had to re-download the software and follow the steps above, took me two days to fix the problem but it ended up positive.
---------- Post added at 10:45 AM ---------- Previous post was at 10:41 AM ----------
2swizzle said:
I had the same issue, try the steps below:
If your able to go into recovery factory wipe everything (if not go to the next step)
Flash the pit file by itself,
After flash is successful reboot and go straight into recovery, wipe everything
go into download and flash the stock firmware
If this doesn't work also re-download the firmware and pit using a windows PC, I've had issues with Macs download the correct file... Hope this helps, I had the same issues as you, in the end I had to re-download the software and follow the steps above, took me two days to fix the problem but it ended up positive.
Click to expand...
Click to collapse
Also delete and reinstall your drivers, from time to time they get screwed up on PC. If you want feel free to send me your phone and I will test for you, I've been around the android world for a long time and have f up my phones/tablets many times but never had a hard brick.
Have you tried restoring using Samsung Kies? If you are in stuck in Download mode, this may work. Give it a shot.
Kies 3 is telling me that the device is not supported. It looked so hopeful for a little bit. Trying to find a workaround but haven't found one yet.
ryanbg said:
Have you tried restoring using Samsung Kies? If you are in stuck in Download mode, this may work. Give it a shot.
Click to expand...
Click to collapse
My internal memory was getting full and so I was trying to clean up some junk. Well, I must have deleted too much!!! After trying to reboot, I received error message "Could not do normal boot"and it goes into odin. I tried to use odin to flash it back to stock, but no luck. It appears like I need a bootloader in order to solve this issue. Any suggestions? Thank you so very much.
If you need a bootloader,
give a look in this thread
http://forum.xda-developers.com/showthread.php?t=2732110
(second or third o fourth post)
many110 said:
My internal memory was getting full and so I was trying to clean up some junk. Well, I must have deleted too much!!! After trying to reboot, I received error message "Could not do normal boot"and it goes into odin. I tried to use odin to flash it back to stock, but no luck. It appears like I need a bootloader in order to solve this issue. Any suggestions? Thank you so very much.
Click to expand...
Click to collapse
Your phone is not bricked if you are getting system error messages or able to boot to download (Odin) mode. Bricked means that a phone responds the same as a brick does. So unless you have a red clay brick that also boots to download mode..
To fix your phone, go to download mode and flash the full stock firmware image for your model /carrier. You should do this in conjunction with the correct PIT file for your phone. Many people skip the PIT file and still prevail. But it's an unnecessary risk to skip it and you would do so at your own peril.
You say that flashing stock didn't work, but you provided no details whatsoever. You don't need a new bootloader, you need to use Odin correctly. To help spot where you are going astray, you need to describe step by step how you are using Odin, the name of the stock firmware file you are flashing, your phone model and verbatim, what you see on the Odin screen. A screen shot or photograph of the download mode screen on the phone would help too.
.
fffft said:
Your phone is not bricked if you are getting system error messages or able to boot to download (Odin) mode. Bricked means that a phone responds the same as a brick does. So unless you have a red clay brick that also boots to download mode..
To fix your phone, go to download mode and flash the full stock firmware image for your model /carrier. You should do this in conjunction with the correct PIT file for your phone. Many people skip the PIT file and still prevail. But it's an unnecessary risk to skip it and you would do so at your own peril.
You say that flashing stock didn't work, but you provided no details whatsoever. You don't need a new bootloader, you need to use Odin correctly. To help spot where you are going astray, you need to describe step by step how you are using Odin, the name of the stock firmware file you are flashing, your phone model and verbatim, what you see on the Odin screen. A screen shot or photograph of the download mode screen on the phone would help too.
.
Click to expand...
Click to collapse
I tried using the "u1_02_20110310_emmc_EXT4.pit" along with "CF-Auto-Root-kltemetropcs-kltemetropcs-smg900t1.tar.md5", on "Odin3-v3.07" and I get, what looks like the download mode, except it states in the upper right hand corner (in red letters) "Could not do normal boot". The only way out is to do a battery pull. It will allow me to go into "Download mode", as the second picture indicates, and Odin states stays on "Reset". The message it states is as follows: D:0/006> NAND Write Start!!, <ID:0/006> cache.img.ext4, <ID:0/006> RQT_CLOSE !!, <ID:0/006> RES OK !!, <ID:0/006> Removed!!, <ID:0/006> Remain Port .... 0, <OSM> All threads completed. (succeed 1 / failed 0), <ID:0/006> Removed!!. Then I once again get the "Could not do normal boot" error message.
Any Suggestions? I greatly appreciate your help. Thank you.
Can you boot into recovery?
Sent from my SM-G900F using XDA Free mobile app
many110 said:
Any Suggestions?
Click to expand...
Click to collapse
You aren't following the suggestions made earlier. You are taking shortcuts that you think won't matter and introducing all kinds of variables. And failing. If you really want to get your phone working, you should follow the advice rather than taking liberties and winging it.
Flash a stock firmware image, not a modified image intended for rooting. First you need a stable system - you can root afterwards. Make sure it is a 100% stock tar for your carrier and use Odin 3.09 instead of the older version you have. Flash the firmware .tar file and PIT file at the same time, with the PIT, F. reset and auto reboot checked in Odin. If the Odin flash fails, try a different USB cable and port. A different computer if you need too.
Also you gave no details about the PIT file, other than the file name. We cannot tell if that is the correct file for your phone. The PIT file needs to match your phone model, ROM size and carrier. There is a XDA thread that should have the correct file. Probably the one that I uploaded here.
As well, if you get an Odin flash failed message, do not close or reset Odin. Instead pull the battery on your phone, replace it and then boot to download mode (press and hold volume down, then home, then the power button). Then try flashing again. The flash will inevitably succeed the second time, even though it failed at first.
.
fffft said:
You aren't following the suggestions made earlier. You are taking shortcuts that you think won't matter and introducing all kinds of variables. And failing. If you really want to get your phone working, you should follow the advice rather than taking liberties and winging it.
Flash a stock firmware image, not a modified image intended for rooting. First you need a stable system - you can root afterwards. Make sure it is a 100% stock tar for your carrier and use Odin 3.09 instead of the older version you have. Flash the firmware .tar file and PIT file at the same time, with the PIT, F. reset and auto reboot checked in Odin. If the Odin flash fails, try a different USB cable and port. A different computer if you need too.
Also you gave no details about the PIT file, other than the file name. We cannot tell if that is the correct file for your phone. The PIT file needs to match your phone model, ROM size and carrier. There is a XDA thread that should have the correct file. Probably the one that I uploaded here.
As well, if you get an Odin flash failed message, do not close or reset Odin. Instead pull the battery on your phone, replace it and then boot to download mode (press and hold volume down, then home, then the power button). Then try flashing again. The flash will inevitably succeed the second time, even though it failed at first.
.
Click to expand...
Click to collapse
What am I doing wrong????
I followed your advise and still no luck. You claim that my phone is not "bricked" but yet I did everything that you recommended and I'm still in the same place. I downloaded your "PIT.tar" file and had to change the name, because "Odin3 v3.09" would not recognize it. I put the pit file and AP file (AND YES, it is a full STOCK image) at the same time, tried it with "re-partition checked" and it failed! I tried it with out and it went through, but I am not able to get any further. Still getting "could not do normal boot"
"You state that I am taking short cut". Could you let me know what I am missing or at least direct me to a tutorial that does not show any short cuts? I get as far as seeing the "red android" figure, with and eye patch and it states that it will restart in 10 seconds. After reboot, I get the same message "Could not do normal boot". :crying:
By the way, would it matter that the pit file that you directed me to is for tmobile and this is a Metro pcs phone? Thank you.
I tried to give you good advice in my first post. Do you recall what I said?
Answer:
fffft said:
To help spot where you are going astray, you need to describe step by step how you are using Odin, the name of the stock firmware file you are flashing, your phone model and verbatim, what you see on the Odin screen. A screen shot or photograph of the download mode screen on the phone would help too.
Click to expand...
Click to collapse
And you still aren't doing so. You are not describing what you are doing step by step. You are not giving us file names so that we know which version of stock firmware you tried to install. Or whether it was really stock. You didn't paste the Odin log - what you saw onscreen. You pepper us with a summary and a few details and expect us to divine what has happened. It doesn't work that way. No one can help you constructively if you refuse to provide abundant information about your situation.
The best you can hope for is drive by guesses or perhaps someone patient that might try to cajole information out of you. We'd all like to help you, but you're making it difficult. It would be in your best interests to provide exhaustive detail because those details are the key thing that will enable people to help you. If you change your mind and provide the detail, someone in the forum will try to help you.
Good luck.
.
fffft said:
I tried to give you good advice in my first post. Do you recall what I said?
Answer:
And you still aren't doing so. You are not describing what you are doing step by step. You are not giving us file names so that we know which version of stock firmware you tried to install. Or whether it was really stock. You didn't paste the Odin log - what you saw onscreen. You pepper us with a summary and a few details and expect us to divine what has happened. It doesn't work that way. No one can help you constructively if you refuse to provide abundant information about your situation.
The best you can hope for is drive by guesses or perhaps someone patient that might try to cajole information out of you. We'd all like to help you, but you're making it difficult. It would be in your best interests to provide exhaustive detail because those details are the key thing that will enable people to help you. If you change your mind and provide the detail, someone in the forum will try to help you.
Good luck.
.
Click to expand...
Click to collapse
Well, I am not too sure how much more can be described from all of my last post, but here goes:
I power up the phone and I get a quick flash, before what looks like the download screen, appears and up at the top left hand corner the message reads "Could not do normal boot" and the under the green android figure are the words "Downloading... Do not turn off target!!"
I then continue to do a battery pull and I proceed to go into download mode (Holding vol. down button, home button and power button at the same time. I get Warning message and at bottom it states "Use volume up: continue, volume down: Cancel(restart phone). I push the volume up button. I am now in down load mode. If you look at the sceen at this point, this is how my SM-G900T1 is booting up, EXCEPT for those little red words at the top. In normal download screen, it states "ODIN"MODE". When I boot up my SM-G900T1, those little red words at the top say "Could not do normal boot" instead of ODIN.
Once I am in download mode, I proceed to use the files that you recommended (the .pit file and the AP file). I load up the files into Odin and I click, start. It begins to work and it then says, "RESET" while it is blue. My phone restarts and I see the red android figure with an eye patch and at the bottom it says, restart in 10 seconds.
the phone proceeds to restart and it goes back to that error message, which looks like the download mode, with the words up at the top , in red letters state "Could not do normal boot. ODIN MODE"
in white letters:
Product Name: SM-G900T1
Current Binary: Custom
System Status: Cusatom
Knox Warranty void: 0x1 (4)
Qualcomm Secureboot: enable (CSB)
RP SWREV: S1, T1, R1, A1, P!
UDC START
my phone goes no further than this and have kept it connected to odin. Now I look up at ODIN and it shows PASS!! in a green box with a time of 02:10. But my phone will not boot up. I restart and I get the message once again"Could not do normal boot"[/LIST
Hopefully someone could help. Thank you.
Well the important thing is that you can get to download mode (aka Odin mode) one way or the other.
Odin is well known for being fussy with cables, USB ports and other details, so don't panic if you get a failed Odin write or two. I also explained how to get around that in most cases.. leave Odin open on your PC screen and pull the phone battery again, go back to Odin mode on the phone and then press start on the Odin screen to try flashing a second time.
many110 said:
Well, I am not too sure how much more can be described from all of my last post
Click to expand...
Click to collapse
You are getting better with details (thanks) and I'm sure that this is frustrating to you. But you are nowhere near telling us step by step what you are doing. for a start, you didn't name the stock firmware image file that you were using, something that I specifically requested. So without meaning to offend you.. you aren't paying attention to details.
By "step by step", I meant a description of each step you took. For example listing each button you press in Odin.. telling us exactly what you type into each box and so forth. You may not see the point of that, but remember that we are not standing over your shoulder. And one wrong action can ruin your write. So that kind of step by step detail is extraordinarily valuable in troubleshooting.
Anyway, there are many ways to go about anything. Since you can get to download mode and your Knox bit is 0x1, I'd suggest installing or reinstalling TWRP, so that you can reliably boot to a stable recovery mode. From there you can look at almost anything, fix things, install custom ROMS, etc.
If you want to continue with Odin instead, then make sure that you are using a real stock .tar or .tar.md5 image, use a different USB cable and try again. If you are persistent, it will work.
.
fffft said:
You aren't following the suggestions made earlier. You are taking shortcuts that you think won't matter and introducing all kinds of variables. And failing. If you really want to get your phone working, you should follow the advice rather than taking liberties and winging it.
Flash a stock firmware image, not a modified image intended for rooting. First you need a stable system - you can root afterwards. Make sure it is a 100% stock tar for your carrier and use Odin 3.09 instead of the older version you have. Flash the firmware .tar file and PIT file at the same time, with the PIT, F. reset and auto reboot checked in Odin. If the Odin flash fails, try a different USB cable and port. A different computer if you need too.
Also you gave no details about the PIT file, other than the file name. We cannot tell if that is the correct file for your phone. The PIT file needs to match your phone model, ROM size and carrier. There is a XDA thread that should have the correct file. Probably the one that I uploaded here.
As well, if you get an Odin flash failed message, do not close or reset Odin. Instead pull the battery on your phone, replace it and then boot to download mode (press and hold volume down, then home, then the power button). Then try flashing again. The flash will inevitably succeed the second time, even though it failed at first.
.
Click to expand...
Click to collapse
any idea where i can get the PIT files for a metro s5?? i found the TAR file and used that in ODIN and it wont get past the metro splash screen. sits there for hours and gets REALLY hot. I tried doing a factory reset in recovery but it fails and reboots. Im hoping maybe a PIT file/repartition would do it i cant find a damn pit file anywhere. model number is G900T1. I used the stock firmware from the site below.
http://samsung-updates.com/details/26200/Galaxy_S5_SM-G900T1/SM-G900T1/TMB/G900T1UVU1ANCI.html
For future reference or anyone else reading this post. If you are running a stock ROM on a SM-G900T, even with root "memory low" alerts can be ignored becouse internal storage has a memory partition to act as emulated memory. In addition, android automatically unloads the oldest unused items from memory. I get these messages all the time, "internal memory usage exceeds maximum limit" or some such. They appear in the status bar without toasts, so their not too annoying. Yes you can clear a lot of stuff out with root,... But first understand your device AND what you intend to remove. If you don't understand it yet then leave it until you research it. Also, I recommend that you research your device before you buy it. I did, thats why my SM-G900T1 is a recent purchase, instead of going for the S6. Now if I could just find out how to root it without a computer when the kernel is dated Nov 10 2014.....
"The power of accurate observation is frequently called cynicism by those who don't have it."
Please delete. Wrong thread.
my phone LG G2 D802 International Version was running perfectly fine i tried to flash another rom by LG FlashTOOL and in the first i got soft bricked on that fastboot screen i recoverd it by ADB (fastboot.exe)
fastboot erase recovery
fastboot erase laf
fastboot flash laf laf.img
and then i tried to reflash it then i got this mesg on screen
---------------------------------------------------------------------------
Critical Error!
---------------------------------------------------------------------------
DemiGod Crash Handler : Critical Error!
Press Key to Choose Dload Mode or Reboot
1) Volume up : Dload Mode.
2) Volume Down: Reboot.
If u choose Dload Mode.
please do following action.
1) Dload Mode. please Connect USB
2) Get the Ram Dump image using QPST Configuration.
-------------------------------------------------------------------------
Board Info
Rev. : 1.1 speed.pvs : 1.1 Serial : 01e862cf934fc622
Please Help me somebody ... i cant afford to buy new phone i just bought this phone a week ago ..
Having same issue ! XDA forum experts always helped me with every situation with my phones. Expecting help this time as well from you experts.
Same here, enyone can help, i stuck with the sam message, presing vol- just rebots, and vol+ sends message "jump to download mode" but i cant flash stock firmware
i have the same problem any help ??
I have the same issue too, can anyone help?
I heard that this can help you guys. Use the search option there and try to fix it. Actually i had the same problem few months ago, but for me mew motherboard was the solution... If you're device is under warranty send it saying it failed while taking OTA. Good luck...
lg g2 critical error
I have done a flash to my g2 32gb d802 and it suddenly entered into critical error not going into any of thefastboot mode or download mode even though it is giving me options.....please any one help me out to get my phone back to normal ........
PM me if you guys need help.
I had the exactly same problem, and I had to go to afterservice center to repair. Engineer told he would wipe everything and install new rom. but He failed to write rom so he simply changed mainboard.
At first I had thought about open my g2 and makes it go into qualcomm download mode by short-circuit.
the reason I didn't was my warranty was still available.
I tried every method to make it boot into recovery or download mode but I failed. In my opinion, you may try short-circuit method for last solution. In this situation, even linux doesn't mount rom's storage section. Only if you can make G2 recognized in Linux, G2 will revive.
good luck.
xmayhemreturnsx said:
PM me if you guys need help.
Click to expand...
Click to collapse
i still don't know what to do HELP
yassou92 said:
i still don't know what to do HELP
Click to expand...
Click to collapse
The best way to go if you do not have a warranty is to short circuit the board and get into Qualcomm ... 9006 mode. However, when you get the demigod error plug in you usb and click up and it should start download mode even though it doesn't show it.
xmayhemreturnsx said:
The best way to go if you do not have a warranty is to short circuit the board and get into Qualcomm ... 9006 mode. .
Click to expand...
Click to collapse
How do you short the pins? There's a guide here on xda but it's so difficult to undestand. I need to know how can I short the pins.
it should start download mode even though it doesn't show it.
Click to expand...
Click to collapse
No, it doesn't. I try to use flashtool but it doesn't recognize the phone. No download mode in any method I tried
I got into this error after I had previously recovered into qhs_usb9006_bulk mode from a hard bricked D801, by shorting the capacitors on the main board. After entering qhs_usb9006, I used srk tools 2.1 for my phone, and after they finished, I tried entering download mode, only to get into this error. I really don't know what it is to say about this. Everything turned wrong with this phone, it went from simply failing a .kdz, to stock .tot, to hard brick, and now to this error, whereas it should've just enter the download mode, as for the 99,99% of the others. Any help would be really appreciated. Thanks.
L.E. I shorted the capacitors again (the one i the middle, like I did the first time, when i got into 9006 mode. 5000 and 5004 didn't work for some reason). This time I got into dload mode, which is 9008. I'll try to recover the phone from here, with this method:
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
i had this problem while trying to return to stock. Fixed it by following this guide http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404 . it needs some hardware tampering though. i tried and tried but i cant flash the phone any other way. the way i understand this is due to bootloader being corrupt.
I installed autorec from playstore solved all the problems
Than you! autorec worked for me too
Can someone post a KK baseband for D801 (T-Mobile)? I'm on D80120a software version with unknown IMEI and baseband (the phone is a D801 refurbished into D802, I more than hardbricked it by flashing wrong .kdz, got it recovered through shorting pins, 9008 mode, got download mode, D80120a stock, root, twrp, after a very long and painful process of about 1 month). Now I have to make use of QPST, but I have to obtain a valid baseband first. Of all links I've stumbled upon, only 5% or less of them are still working, so I only have one flashable modem, in twrp recovery, which corresponds to D801 jb version.
http://downloads.codefi.re/autoprime/LG/LG_G2/G2_modems
cloudyfa kk_baseband_D801 only make my phone restarts like crazy.
I'm simply stuck and pray for some devine help.
Thank you.
Weird enough, I flashed a canadian modem and I got both baseband and IMEI. Why did I do that in the first place? Because I remembered that before all these things happened to my phone, the baseband was M8974A-AAAANAZM-1.0.190082, which corresponds to D803. So I said to myself what can happen by flashing the wrong modem? Boot loop, easily fixable with the phone in it's current state. But again, after 1 month of trouble with the phone, I'm back to what exactly started it in the first place: phone seem to work OK but it has 2 huge problems: WiFi extremely weak (2 meters away and a wall or 5 meters away and no wall a and I lose the signal in both cases; the 2nd is wit the GPS - 20-30 meters error). No idea how should I adapt the radio to Europe region (by keeping the canadian one and change the settings, if it's even possible/fixable this way or if this even does make any sense).
I had to do a hard brick fix to get it into the QSUSB mode to flash TOT.
Have you tried using LG Support tool to put it back to stock?
Sent from my LG-F350K using XDA Free mobile app
Felt slight stupid as I saw my s5 going round the washing machine, thought I'd have a play after it's dried out.... I like learning but don't really know phones.
It was encrypted but was stock firmware.
Currently:
- It powers on
- I can get to the download in boot ok (vol. down)
- It resets when trying to get into recovery mode
- Kies see's something trying to connect but times out. Heimdall detects it but throws errors upon trying to flash , I'm yet to try Odin, just getting stock firmware as I write this.
(Heimdall error - libusbx: error [winusbx_submit_bulk_transfer] ReadPipe/WritePipe failed: [22] Th
e device does not recognize the command.)
I've got some more playing around to do but it feels like, at least, the storage is screwed but that's a complete guess.
1) I was hoping someone would know if it's worth playing further?
2) Whether anyone could take a guess of whether replacing the mother/logic board would be a *possible* fix
3) Could anyone point me to any resources explaining the how the phone works- I'm initially trying to understand what components sit on the logic board and the boot sequence. e.g. could the CPU/ storage be fried but it still boot this far?
Many thanks in advance for any help.
OK, I'm a little further along with this now.
I'm using various versions of odin (3.0.7,9,12.3). Various computers (all windows 10 now but did try heimdal on a 2 nix machines) and a whole lot of leads. Just getting Odin to recognise the phone was fun.
Tried using the AP part to install the BTU UK version of firmware from sammobile
Tried getting the hidden .img.tar from it and flashing that
Tried flashing a twrp recovery
But all come up with
Code:
GetPIT for Mapping
There is no PIT Partition
So I got a couple of Pit files for and tried them with the Re-partition ticked
Code:
Set PIT file...
DO NOT TURN OFF TARGET!!
Complete (Write) Operation failed
OSM All threads completed (succed 0/ failed 1)
So a few questions:
1) How do I uploda photos here? Or do they have to be inserted links. May be my low post count? Or I'm blind
2) Is it normal that odin stops recognising the phone the moment there's an error like the one's I'm having. Odin's ID:COM part goes blank and I have to remove/ insert the USB again.
I just want to check that's not some other reason.
3) Is there anyway to test whether the NAND's working/ can be accessed without pressing that scary NAND erase all button?
Many thanks
Why not just get it fixed from service center?
beardedfool said:
OK, I'm a little further along with this now.
I'm using various versions of odin (3.0.7,9,12.3). Various computers (all windows 10 now but did try heimdal on a 2 nix machines) and a whole lot of leads. Just getting Odin to recognise the phone was fun.
Tried using the AP part to install the BTU UK version of firmware from sammobile
Tried getting the hidden .img.tar from it and flashing that
Tried flashing a twrp recovery
But all come up with
Code:
GetPIT for Mapping
There is no PIT Partition
So I got a couple of Pit files for and tried them with the Re-partition ticked
Code:
Set PIT file...
DO NOT TURN OFF TARGET!!
Complete (Write) Operation failed
OSM All threads completed (succed 0/ failed 1)
So a few questions:
1) How do I uploda photos here? Or do they have to be inserted links. May be my low post count? Or I'm blind
2) Is it normal that odin stops recognising the phone the moment there's an error like the one's I'm having. Odin's ID:COM part goes blank and I have to remove/ insert the USB again.
I just want to check that's not some other reason.
3) Is there anyway to test whether the NAND's working/ can be accessed without pressing that scary NAND erase all button?
Many thanks
Click to expand...
Click to collapse
Yeah that sounds like water damage alright. I'm sorry to tell you it sounds like your NAND is semi-corrupted in that part of the BL seems to have survived but basically everything else is kaput.
If the PIT partition is missing that is a flag right there to a likely NAND corruption.
Sorry to be the one to have to tell you this but at this point you're best bet is to take it as a total loss and try to sell any undamaged parts (ex. Digitizer, LCD) to raise the cash for a new phone.
Been using an old.... make that, ancient SCH-I500 for a few years on Page Plus Cell with no problems. Today, it got stuck in a weird boot loop. Tried booting into recovery mode and that's when it totally died. Right now, I can hook it up to my PC and have the yellow Android icon up and I'm guessing it's in Download mode. I've followed guide after guide after guide here and nothing is working. A lot of the factory ROM links are dead but I found a stock GingerB rom I think and when flashing with Odin, it gets towards the end and I see, "MOVINAND" in yellow but after 5-10 minutes, it dies out with an error about 'write operation failed'.
I'm close to just tossing in the towel and getting a new phone. Because money is tight, I'd like to just reload the factory ROM on this thing and see if I can keep using it. But if I need to buy a new phone, I guess I will.
To save you as long as it is not hard bricked, follow these steps.
Get this file.
https://gofile.io/?c=tJd0Pd
Then get odin v1.85
https://gofile.io/?c=WHkZHO
Launch odin with admin powers (sudo/su for linux, or whatever).
Then click PDA and select the tar.md5 file and start.
And please make sure you got the drivers and that a COM port does show up in odin.