I can't get into my phone. It is stuck in ODIN mode.
I was trying to install cyanogenmod 11 on it and i messed up somehow.
danhvo1 said:
I can't get into my phone. It is stuck in ODIN mode.
I was trying to install cyanogenmod 11 on it and i messed up somehow.
Click to expand...
Click to collapse
post some screenshots and pics .
and describe what you were trying to do...
Be specific
Can you be more specific about what happened the first time, when you encountered error in Odin.
I think whenever you switch on the cell you get an error like "Firmware update encountered an error, use Kies{something like that}" huh?
There may be problems that may occur if the phone got disconnected while flashing with Odin.
I think Odin showed a FAIL when you flashed the first time.
Okay this might have caused because of the PIT partition might have damaged during flashing. This can be corrected.
But as far as we are not getting any Idea of what prblm you are facing..
BE SPECIFIC, and explain what happened.Because this may be a software brick and can be corrected. Everything in your hands
DMJoh said:
Can you be more specific about what happened the first time, when you encountered error in Odin.
I think whenever you switch on the cell you get an error like "Firmware update encountered an error, use Kies{something like that}" huh?
There may be problems that may occur if the phone got disconnected while flashing with Odin.
I think Odin showed a FAIL when you flashed the first time.
Okay this might have caused because of the PIT partition might have damaged during flashing. This can be corrected.
But as far as we are not getting any Idea of what prblm you are facing..
BE SPECIFIC, and explain what happened.Because this may be a software brick and can be corrected. Everything in your hands
Click to expand...
Click to collapse
Ya..I agree with DMJoh .. Describe the problem but please don't write an essay about it.. just the main points :angel:
jime1 said:
Ya..I agree with DMJoh .. Describe the problem but please don't write an essay about it.. just the main points :angel:
Click to expand...
Click to collapse
uff... n em sorry too!!
Related
My infuse atm is stuck in odin at the setupconnection while I was trying to install the kernel to root my rogers infuse. This is the link http://forum.xda-developers.com/showthread.php?t=1197248. It has been stuck like this for quite a while and I dont know what I should do. If anyone one is wondering, I did not check off re-partition while doing this.
apparently I am now soft bricked
I am assuming I'm supposed to use this method to unbrick my phone?
http://forum.xda-developers.com/showthread.php?t=1193927
Yes you are correct good job finding it...seems lots didn't...
{U.S.M.C.} "Fraternal Brotherhood of the Highest Order"
Just to make sure, my phone is soft bricked since it is saying firmware upgrade encountered an issue. Please select recovery mode in kies & try again
Nvm, got my phone to boot.
xinfinite said:
Nvm, got my phone to boot.
Click to expand...
Click to collapse
good was fixing to ask for a status check on you and your phone...
keep us updated and any more info needed...holler
Okay I had an L rom for about a month maybe less. Then Friday night, it just turns off and now all I see is flying colors.
In the ask any question thread I asked and some really awesome dudes were trying to help me but all of their solutions were in vain.
I used method 1 and 2 of the return to stock.
I made sure I followed EVERY step. Still nothing, it's been trying to boot for far far too long.
I really need my phone, and I'm not sure what else to do. I can't jump because I'm broke and that tamper flag is up.
Can someone help me? I have teamveiwer if it helps.
Also I should say I get several errors I think, like no recovery.sig or boot.sig when I clearly just flashed them.
Why do I get these errors? Is nobody else having the same problem as me? I'm getting really frustrated and to anyone who helps me solve my problem will get my oatmeal raisin cookie recipe (Not kidding, that's serious).
Please somebody help me. Ill be constantly refreshing this page so if you have any questions I will answer them.
Have you booted into the bootloader and used a Google bat file to flash the device completely clean?
Sent from my Android 5.0 Nexus 5
Yes
Follow http://forum.xda-developers.com/showthread.php?t=2513701
Download "15 second adb installer" if you're having issues with adb or fastboot commands
Ignore the .sig errors
Worst case scenario flash each file one by one if flash all.bat doesn't work
Post up what happens after you run flash all.bat too
Have you tried flashing the KitKat factory images instead of Lollipop?
RaggleFraggles said:
Yes
Click to expand...
Click to collapse
Then you must have corrupt hardware, can you not send it back to Google for fix/replacement?
Sent from my Android 5.0 Nexus 5
Either the op fixed the phone and is now celebrating by getting very drunk, or he smashed his phone out of frustration and doesn't care anymore lol.
Either way he's not refreshing this page constantly like he said
I didn't get the insurance or the warranty or nothing
No its still broken but I end up having to help my friend cause he car broke down all day.
No I didn't really want kitkat again, I really wanted to keep L. Ill try it when I can though.
I did both ways, flash all and flash manually but neither worked.
RaggleFraggles said:
No I didn't really want kitkat again, I really wanted to keep L. Ill try it when I can though.
Click to expand...
Click to collapse
Whether you want it or not, try flashing KitKat just to see if it will boot
jsgraphicart said:
Whether you want it or not, try flashing KitKat just to see if it will boot
Click to expand...
Click to collapse
Downloading it now
RaggleFraggles said:
Downloading it now
Click to expand...
Click to collapse
Any luck?
Neither worked in what sense? What happens when u flash? Errors? We can't really help much unless u give us info to go on lol
Sent From Bacon
Someone got to find a fix for this
So I have an AT&T G4 and I was attempting to root it, something went wrong, when I completed the rooting process I unplugged my phone and got an Authentication fail #11. So I decided I would flash the H810PR ZDK on to the phone hoping I could fix it using this guide (http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848) after I completed that I got nothing..... black screen. Now it wont turn on and when I plug it in hear a failed driver sound and this shows up http://imgur.com/EGgdiYL . I've read like two success stoires of people with my problem actually getting AT&T to replace their phone with my problem under warranty, what can I do?
LunaticHD said:
So I have an AT&T G4 and I was attempting to root it, something went wrong, when I completed the rooting process I unplugged my phone and got an Authentication fail #11. So I decided I would flash the H810PR ZDK on to the phone hoping I could fix it using this guide (http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848) after I completed that I got nothing..... black screen. Now it wont turn on and when I plug it in hear a failed driver sound and this shows up http://imgur.com/EGgdiYL . I've read like two success stoires of people with my problem actually getting AT&T to replace their phone with my problem under warranty, what can I do?
Click to expand...
Click to collapse
Its look like your device's hard brick, nothing can do except changing the device.
faizalotai said:
Its look like your device's hard brick, nothing can do except changing the device.
Click to expand...
Click to collapse
I'm under warranty still, do you think that I can exchange it with AT&T?
LunaticHD said:
I'm under warranty still, do you think that I can exchange it with AT&T?
Click to expand...
Click to collapse
I guess the phone are not booting, as long as there's no showing of leaking or damage..I think its possible to get new one..
Just says the phone not boot after charging or so..
faizalotai said:
I guess the phone are not booting, as long as there's no showing of leaking or damage..I think its possible to get new one..
Just says the phone not boot after charging or so..
Click to expand...
Click to collapse
Correct, it isnt booting at all, so I should just tell them it broke or somthing along those lines?
LunaticHD said:
Correct, it isnt booting at all, so I should just tell them it broke or somthing along those lines?
Click to expand...
Click to collapse
Yup, and pray..
faizalotai said:
Yup, and pray..
Click to expand...
Click to collapse
Okay thank you for the help! I'll probably contact them tomorrow and just tell them it stopped working and hopefully they will just replace it, after all its their fault for not giving us a proper ZDK to fix it ourselves
LunaticHD said:
Okay thank you for the help! I'll probably contact them tomorrow and just tell them it stopped working and hopefully they will just replace it, after all its their fault for not giving us a proper ZDK to fix it ourselves
Click to expand...
Click to collapse
What if I don't have a warranty on my phone?
Who's your carrier?
LunaticHD said:
Who's your carrier?
Click to expand...
Click to collapse
AT&T
I did the same I flash the wrong kdz files.All we need some one to uploads the complete eMMC IMAGE to try to revive the phone
The biggest error, is to not make a backup of your stock system.img before flashing.
I encountered the error #11, and fixed it by flashing back to stock, then flashing the correct rooted system image version.
It's caused by flashing a system image that doesn't match your current installed software version.
Ie- you have 10g installed but attempt to load a rooted 10o system image, or vice versa.
same happen to me but i have no opcion im outside the united states so im stuck with this bricked phone. theres a tool for the lg g3 called boarddiag that only works for g3 maybe in a future g4 is added
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
ebercon said:
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
Click to expand...
Click to collapse
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
TheMadScientist420 said:
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
Click to expand...
Click to collapse
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
ebercon said:
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
Click to expand...
Click to collapse
sounds the firmware u are flashing is older than what you have on the device hence the fail
try to find newer firmware and try flashing it
download
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
amol6630 said:
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
Click to expand...
Click to collapse
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Try with latest firmware + pit file + tick re-partition
ebercon said:
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Click to expand...
Click to collapse
Sorry to revive this thread but did this work cause its currently happening to me
If your phone is an original, S/N may be engraved in the back... it's a little bit hard to note but put a spotlight near it so that you can identify it better.
hhh ^^
I got a s6 that bootloops after the Samsung logo. I tried Odin flash firmware but failed after writing nand. Then used emergency recovery through their official application. It failed a bunch of times but succeeded in the end (after 10 retries or so). However the phone still bootloops even after a successful restore. And advice on anything else I can try?
Jo The Veteran said:
I got a s6 that bootloops after the Samsung logo. I tried Odin flash firmware but failed after writing nand. Then used emergency recovery through their official application. It failed a bunch of times but succeeded in the end (after 10 retries or so). However the phone still bootloops even after a successful restore. And advice on anything else I can try?
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s6/help/galaxy-s6-bricked-t3671754/post73762467
Try like that... With latest Odin, drivers and stock FW downloaded via SamFirm. If there are some errors with writing NAND - hardware issue (probably eMMC like in 95% cases). Something happened with phone before, some heavier falls or something?
rifek4 said:
https://forum.xda-developers.com/galaxy-s6/help/galaxy-s6-bricked-t3671754/post73762467
Try like that... With latest Odin, drivers and stock FW downloaded via SamFirm. If there are some errors with writing NAND - hardware issue (probably eMMC like in 95% cases). Something happened with phone before, some heavier falls or something?
Click to expand...
Click to collapse
Yeah, that was the first thing I tried that gave me the NAND error. And yes, the bootloops started happening at random after the phone fell and broke the digitizer as well, after a while the bootloop became permanent. I suspected a broken connection in the NAND bga, but what threw my hypothesis away was that it actually finished the emergency restore from Smart Switch. I guess that doesn't mess with the boot sector at all, and only restores the android OS. Oh well worth a shot, now I've got another expensive hi-tech brick.
Anyone buying those by any chance? Just checking.
Jo The Veteran said:
Yeah, that was the first thing I tried that gave me the NAND error. And yes, the bootloops started happening at random after the phone fell and broke the digitizer as well, after a while the bootloop became permanent. I suspected a broken connection in the NAND bga, but what threw my hypothesis away was that it actually finished the emergency restore from Smart Switch. I guess that doesn't mess with the boot sector at all, and only restores the android OS. Oh well worth a shot, now I've got another expensive hi-tech brick.
Anyone buying those by any chance? Just checking.
Click to expand...
Click to collapse
Some S6 are really sensitive like one fall down and broken eMMC. Repair is even more unprofitable than a completly broken display
EDIT:
Or if you know how to do it, you can change all motherboard your self if you found someone in you area or eBay or something like that, but be sure is from good source so 100% working and not from stolen phone Sometimes can buy for 40-60€.