Database Info

Imei problem

Dear friends
I used lg updater but after that I lost the signal
When I checked *#06# it didn't show me the imei
When I go to about imei it show 0
I searched the problem on 3d I didn't found any one have this problem
But I found some 2x have it and they solve it by baseband flashing
So did any one have the same problem before and how dix you solve it ?
Thank you all
Sent from my HTC FLYER using Tapatalk

any one can help me please

very similiar problem, imei empty, id not found.
is not detecting the sim card
and the only way to switch it up is with charger of the wall conected imposible to do with the usb

You should see the IMEI under Settings -> About Phone -> Status

Att flashed kz with lg update
I am having the same issues as you guys.. I flashed the KZ file with lg update software as explained in the XDA thread but I could not get the process to work right. My phone kept disconnecting at 28% and it would not turn on no matter what I did. It would only make a short vibrate as if it was turning on, and the computer would notice it but only for a short time. And never once did a light on the screen, or LG logo, or anything at all ever appear.
I figured I had really screwed it up, but when I plugged it into the wall it booted up perfectly. All my data was in tact and the rom i had flashed through cwm was still there, not the kdz file that I flashed with the lg software.. I noticed that my sim card did not come up as being in the phone at all. I looked in system setting status and noticed that all info related to my imei said unknown. I opened up the mfg app (277634#*# from the phone app).. Under "version info" then "factory version" my phone now says xmm6260.. It always used to say p925..etc... Even after flashing the zip to debrand from at&t this never changed from p925 even when every other aspect of my phone has.. I was hoping maybe once I put in an activated sim card everything would be fine and my phone would be unlocked which is why i flashed through lg software.. But seeing as how other people are having this similar issue and their phones not seeing the sim card, well im looking for some advice.. Should I try and re flash kdz file through lg software again? if i do, im going to do it on my XP computer this time, not Windows 7..
Just wanted to add that I did try wiping data and cache from cm and no dice.. Root and CMW work fine but no matter what I do, if my phone is turned off, i cannot boot up or boot to cwm or boot at all unless i plug the phone into a wall carger and then once its on it stays on and i can unlug.. SORRY ABOUT THE LONG POST, THANKS IN ADVANCE FOR ANY HELP..

Hello, I am having the same problemws as you.. Have you found anything out yet? I'm trying to get some answers.. Did you try re flashing kdz with lg update?
Sent from my SPH-D700 using xda premium

Hi guys
I'm getting exactly the same thing aswell!! I wonder what the problem could be? I can boot the phone up if I plug it into the wall charger, but have no signal at all.

Anybody got a solution, please?

WesleyR said:
Anybody got a solution, please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1244490
try this with the correct cable.

No IMEI/GSM Radio
Im having same problem, has anyone found a solution?
Im attaching some screen shots of the errors I get.
Thanks

imei missing
Is there any soltion? Please.

Reflash the phone.
Take out battery. hold down the up key, plug in cable to computer.
Wait till it installs or activates the necessary drivers. eg usb protocol etc.
Then run the recovery via lg tool by entering your imei number in the application.
This will install the latest stock version based on your imei (including baseband)

thealgorithm said:
Reflash the phone.
Take out battery. hold down the up key, plug in cable to computer.
Wait till it installs or activates the necessary drivers. eg usb protocol etc.
Then run the recovery via lg tool by entering your imei number in the application.
This will install the latest stock version based on your imei (including baseband)
Click to expand...
Click to collapse
Thanks, I tried but it did not work.
I tried everything possible. KDZ flashed about 20 times. Flashed bin and fls files many times. I do not know what more to try. When I put androuid 2.2 After a while the cell phone turned on appears IMEI and IMESV, but disappeared again after reboot.
I put the phone in the CP - USB (3845#*920# port settings cp-usb) mode and I connect with hyper terminal when I type AT%IMEI my modem gives me IMEI. When I type AT%IMEI=? back to me is: [IMEI part1 [7] + IMEI part2 [8]] but I do not know how to write it. I tried all possible combinations and I still write IMEI write error. (AT%IMEI=xxxxxxxx + xxxxxxx AT%IMEI= x, x, x, x, x, x, x, x, x, x, x, x, x, x, x, ......) I found [LGFlash Tool 1.0]LGP920_20120213_Download_WriteIMEI.dll at the CSMG server and I tried with LG flash tool so that instead of stock dll I put this dll but it failed. It gives me an error not read IMEI. There may be a BIN file that is used whit it??? Here's the dll if anyone wants to try.
All this hapend after simple reboot. I found service manual for LG internal use it says that this could happen becouse of fault in firmware, and that after write IMEI firmware should be updated to V21A to prevent this to happen. So some early firmware cause it.
I dont have warranty.
sorry for bad english.

Interesting.
When you run the official recovery tool and it asks you to enter your Imei, does it go ahead with the process and fully complete 100% with the flashing?
Do the problems then still occur? If you can get your phone to turn on at anytime, have you tried a full factory reset after that?

thealgorithm said:
Interesting.
When you run the official recovery tool and it asks you to enter your Imei, does it go ahead with the process and fully complete 100% with the flashing?
Do the problems then still occur? If you can get your phone to turn on at anytime, have you tried a full factory reset after that?
Click to expand...
Click to collapse
Yes it completes at 100% everything is ok I can turn it on, off, go into recovery and everything. Device is working perfect but android cant see IMEI, that is writen in eeprom. I tried factory reset numeros times, no help. When i start lgupdate official tool, tool also reads correct IMEI from device.

Seems an issue with the baseband updating/corrupted, although the lg tool flash recovery should have updated this as well. Have you tried the other flash methods (try one of the kdz roms in this forum. eg v21a for europe gingerbread) and use this flashing method (you would need to block the lg updater from accessing the net) There is a tutorial on this in this forum. it works via forcing a rom update and redirecting it into the lg flash program

thealgorithm said:
Seems an issue with the baseband updating/corrupted, although the lg tool flash recovery should have updated this as well. Have you tried the other flash methods (try one of the kdz roms in this forum. eg v21a for europe gingerbread) and use this flashing method (you would need to block the lg updater from accessing the net) There is a tutorial on this in this forum. it works via forcing a rom update and redirecting it into the lg flash program
Click to expand...
Click to collapse
I did that metod too. There is any metod here on this forum that I didnt try. Thanks for help. I dont know is it baseband or CP chip problem.

This may be guesswork, but if the baseband is flashed in a specific area of the phones nand space, perhaps the nand blocks there are corrupt which causes it to fail. Perhaps with some additional tools, it may be possible to format this area, marking the bad blocks as bad preventing the baseband data from writing to these area's. Just guesswork here.
Have you tried flashing other baseband versions seperately

thealgorithm said:
This may be guesswork, but if the baseband is flashed in a specific area of the phones nand space, perhaps the nand blocks there are corrupt which causes it to fail. Perhaps with some additional tools, it may be possible to format this area, marking the bad blocks as bad preventing the baseband data from writing to these area's. Just guesswork here.
Have you tried flashing other baseband versions seperately
Click to expand...
Click to collapse
Yes i did! No help!

Hi,
I have the same problem and tried almost everything written in this topic but didn't worked.
hyperterminal seems to be working for most of the optimus models but doesn't work with p920. I tried all the port settings and everytime got "IMEI WRITE ERROR" message.
any new suggestion?

[Q] Is there a way to pull information from an old backup?

I haven't been able to find anything specific in the threads, so this may be an odd request.
I recently needed to pull some texts from an old backup from CWM. I can see it saved on my external storage, but something messed up in the memory(?) and I kept getting error messages in Odin mode telling me I needed to use the Software Repair Assistant.
Everything I found and tried on here would fail in Odin, no matter what file I was trying to install or which directions I followed.
The phone ended up not booting at all, just going to the repair assistant screen whether it was a normal or download mode boot.
I got frustrated the other night and just used the Samsung emergency repair tool. Now it is back to working properly, but everything I read on here is saying nothing is really going to work on 4.4.2 with the VRUDNE1 baseband.
Before I mess it up again and try rooting and restoring back to an older version (4.3 I think) which will probably mess up, is there any way I can go in to the save files and pull the texts?

nebbernoo said:
I haven't been able to find anything specific in the threads, so this may be an odd request.
I recently needed to pull some texts from an old backup from CWM. I can see it saved on my external storage, but something messed up in the memory(?) and I kept getting error messages in Odin mode telling me I needed to use the Software Repair Assistant.
Everything I found and tried on here would fail in Odin, no matter what file I was trying to install or which directions I followed.
The phone ended up not booting at all, just going to the repair assistant screen whether it was a normal or download mode boot.
I got frustrated the other night and just used the Samsung emergency repair tool. Now it is back to working properly, but everything I read on here is saying nothing is really going to work on 4.4.2 with the VRUDNE1 baseband.
Before I mess it up again and try rooting and restoring back to an older version (4.3 I think) which will probably mess up, is there any way I can go in to the save files and pull the texts?
Click to expand...
Click to collapse
I haven't seen a way to do it yet. If your already on 4.4.2 you can't revert back to an older version. Doing so will cause a soft brick
Sent from my Nexus 5

ShapesBlue said:
I haven't seen a way to do it yet. If your already on 4.4.2 you can't revert back to an older version. Doing so will cause a soft brick
Sent from my Nexus 5
Click to expand...
Click to collapse
Would I be able to flash it onto another device that hasn't been updated to 4.4.2? On say a Motorola RAZR M? Or would it have to be a pre 4.4.2 Galaxy S3?

nebbernoo said:
Would I be able to flash it onto another device that hasn't been updated to 4.4.2? On say a Motorola RAZR M? Or would it have to be a pre 4.4.2 Galaxy S3?
Click to expand...
Click to collapse
It would have to be a S3. Flashing the software intended for an S3 to another device won't work, I am not saying that this will 100% work
Sent from my Nexus 5

Tribute 5/Kingroot/No Command Screen

So following the instructions here I rooted my LG Tribute 5 when I got it with Kingroot. And everything was fine for months. Until System Updates started to pop up regularly but I could never get them to install(they would error out). After a quick search I learned the updates won't install cuz the device was rooted. And a quick unroot would get the install to work.
I just unrooted through the kingroot app and started the updated. Before, when I tried the update it would error out about a quarter of the way through. This time the bar made it all the way to the end and then error'd out. I didn't think much of it. So since the device was stuck I took my battery out and back in. The device went through the boot process, then a No Command error popped up. Never saw that before.
So I tinkered with it a bit and kept getting the error. So I got into the Recovery Menu to do a full wipe and factory reset. I did that, but the No Command still popped up.
I know I can put a custom rom file on my external sd card and install that through recovery, right? The thing is I would like to install Slimrom, but there are a ton of downloads on the sites download page. So I'm asking for a little help on directions on a slimrom that will work on the LG Tribute 5.
And if there isn't a custom rom that works with a tribute 5,can I get a recommendation of one a custom rom that does? I'm into lightweight and minimalistic. By the way, I didn't have a custom rom on my phone, just had it rooted.
Thank you so much in advance for any and all help

No-one has any advice for me?
A little more info, the phone was on Android 5.1.1 before it started erroring out.

No-one has any advice for me?
A little more info, the phone was on Android 5.1.1 before it started erroring out.

Do you have a custom recovery as well? If it is only the stock recovery, which blocks most zips, your very option may be to use LG UP and the stock dz file and return the device to stock. The process to update can be done from that point.

I'm pretty sure I only have the stock recovery. I knew i should have installed TWRP...
So just search for LG UP and the stock firmware and they should be easily accessible?
Thanks for the reply xanscorp.

https://drive.google.com/folderview?id=0B0KV4b0_G1PQZW95ZmloejU5dFk
The LG UP program and .dz file are in there.

That's awesome! Thank you very much for linking the files for me.
I'm gonna do this in a couple hours when I get home and I'll let you know how it went.
Much appreciated xanscorp

One last stupid question... Just the LG Up and.dz files are the only two I need right?
I'm guessing so, but just wanna be sure.

Yes. It'll put you back to stock.
Unfortunately I haven't yet found how to get the ZV5 firmware fully rooted (i.e. a custom recovery) but it can be partially rooted with KingRoot. (http://www.kingroot.net/wap)

I just finally got around to giving this a shot. Sheesh....
Anyways I downloaded the files, put them on my external SD card, popped my SD card into my phone, then booted my phone to recovery. I went to install update from SD, and the phone didn't find any files. Hmmm....
I'm definitely doing something wrong. The .msi file looks like an executable. So I hopped onto Windows to install it. It installed, but when I run the program it can't find my phone when I plug it in.
I'm about to just give up, trash this thing, switch to a different provider and get another new phone. This time I won't mess with Kingroot. I'm pretty positive that's the app that screwed things up. I've had three different phones, rooted all three through different methods, and never had a problem.

Things files are to restore from a pc using LG Up for Windows... that's why it's a Microsoft Installer (.msi) file.

Yeah I figured that. But when I plug my phone into the computer my phone isn't recognized. I'm assuming because it boots straight to a No Command screen.
So since the computer doesn't recognize it neither does LG Up. Any trick to get around this?

Still haven't gotten this phone back to working. This is the first time I've really been stumped after a brick.
Please...anymore help?
Sent from my KFFOWI using Tapatalk

You find annything cause my same phone did the same thing

Sure haven't bud.
I've tried the help in the thread with no success

Warning: Do not flash the google assistant

I flashed the Google assistant some time ago and everything was fine but yesterday I decided to do some minor build prop edits and accidentally bricked my phone. Now that's fine because they have multiple ways of unbricking the T-Mobile LG v20. But when I tried to unbricking it using LGup nothing works because it registers my phone as a pixel and now my phone can't be restored. So take it from me..Don't do it!!! It isn't worth the loss. I have a brick now. An official lg v20 brick. Sigh
EDIT:
IM EDITING THIS TO ADD WHAT I DID.
Here's the story
I was trying to revert to stock with the build prop so I could upgrade my phone. so I edited the prob and removed the lines I added to get Google assistant in the first place but it crashed and when I entered TWRP to push the build prop. When that didn't work I flashed the stock tot file which got my phone working but I wanted to upgrade so I found the page in XDA to flash the kdz with LGup which I was doing but half way through it failed and Twrp was gone which started this snow ball effect.

Do you not have TWRP you can reboot into, and re-flash a backup or new ROM?

CharlzO_2000 said:
Do you not have TWRP you can reboot into, and re-flash a backup or new ROM?
Click to expand...
Click to collapse
Nope, the only thing my phone does it boot into the mode where it says "Firmware update" mode. I really think I destroyed my phone.

remix435 said:
Nope, the only thing my phone does it boot into the mode where it says "Firmware update" mode. I really think I destroyed my phone.
Click to expand...
Click to collapse
Take it to the store and tell them it happend when the phone was updating.

slayerh4x said:
Take it to the store and tell them it happend when the phone was updating.
Click to expand...
Click to collapse
That's actually a pretty good idea. I'm going as soon as TMobile opens.

I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps

Leonarddale said:
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Click to expand...
Click to collapse
This.

remix435 said:
I flashed the Google assistant some time ago and everything was fine but yesterday I decided to do some minor build prop edits and accidentally bricked my phone. Now that's fine because they have multiple ways of unbricking the T-Mobile LG v20. But when I tried to unbricking it using LGup nothing works because it registers my phone as a pixel and now my phone can't be restored. So take it from me..Don't do it!!! It isn't worth the loss. I have a brick now. An official lg v20 brick. Sigh*
Click to expand...
Click to collapse
That is very strange, I recently bricked my phone to the point where I didn't have a system at all on it. When you boot to firmware update mode (power + volume up) and pluged it in LGUp recognized it instantly. You have the correct DLL for your device right?

shadowxaero said:
That is very strange, I recently bricked my phone to the point where I didn't have a system at all on it. When you boot to firmware update mode (power + volume up) and pluged it in LGUp recognized it instantly. You have the correct DLL for your device right?
Click to expand...
Click to collapse
My issue was that when I flashed the assistant mod it turned my device name into " google pixel" so when I hooked it up to lgup it read it as a pixel and failed the restore every time. That was the issue I couldnt change the name of my devixe back to the v20.

Leonarddale said:
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Click to expand...
Click to collapse
I disnt have anything on my phone. No twrp and I couldnt install it. The assistant mod changed my device name to PIXEL and when id connect it to the pc it read as a pixel and failed every update I LG V20 I pushed to it..that was a new type of brick lol. But I told t mobile that if I what happened and I got another one.

These old assistant mods would be taken down. The only thing needed to enable it without spoofing a phone as a Pixel is adding "ro.opa.eligible_device=true" to build.prop, and the Google app updated via Play Store.

remix435 said:
My issue was that when I flashed the assistant mod it turned my device name into " google pixel" so when I hooked it up to lgup it read it as a pixel and failed the restore every time. That was the issue I couldnt change the name of my devixe back to the v20.
Click to expand...
Click to collapse
That's the thing my phone didn't have a system on it at all and LGUp read it as what it was. When you on the firmware screen it should read based on hardware ID right? Have you tried using LG bridge? Are you on the T-Mobile variant?

This is a contributing factor in why these companies lock bootloaders. People do stupid things because they don't know what they're doing and then others encourage them to just return it and get a new one and lie. Not cool at all. How about don't root your phone if you don't know what you're doing.

markbencze said:
This is a contributing factor in why these companies lock bootloaders. People do stupid things because they don't know what they're doing and then others encourage them to just return it and get a new one and lie. Not cool at all. How about don't root your phone if you don't know what you're doing.
Click to expand...
Click to collapse
WTF! With your logic no one would learn anything.
My phone was rooted just fine. How was I suppose to know that after I flashed the stock build prop my phone was going to stay as a pixel device?? That wasn't stupid of me that was trial and error. Something stupid is if I did it again. No one specified that my phone would stay as a pixel device, go read the instructions and tell me where it says that. Also, I have "Jump on demand" so I used one of my jumps to get a brand new phone..So I paid a price for it. It wasn't just "me lying and getting a free phone" I still paid for it I paid for my mistake and Yes initially I lied but still paid and am still paying for this phone. Plus I have an s7 edge and a Huawei honor note 8 all rooted and have never ran into any issues. Why?? Because I never did what people instructions told me not to do. I always follow instructions. I've been rooting phones since I was a milk drinker all the way back to the G1 days. I'm very careful but if instructions don't cover all the basis then what?? PEOPLE, including me should continue to root and try new things. But you can't blame them if YOU(not you in particular but in general) as a developer make something and can't catch all the bugs(it isn't The developers/modders fault either)..Modding is a giant community of trial and error. The only people at fault are idiots who don't read and do some ****. Other than that we are all out here finding our way with these new devices. So yes, I have a new v20 that I paid for with MY "Jump on demand" plan that is now rooted and unlocked. Now am I going to use the Google assistant mod again?? No, because that would be stupid of me. Now get off my post.
I was just warning people so they wouldn't make the same mistake as me.

Whats the stupid part is how you managed to erase TWRP and lose access to fastboot on your device. Not that your changed something in build.prop. His logic is not flawed, whatever you did to lose access to the two essential parts of having a rooted phone is the flaw here.
Also simply doing build.prop edits should not make you lose access to TWRP nor being able to access fastboot - or did you relock your bootloader?

twistedvip said:
Whats the stupid part is how you managed to erase TWRP and lose access to fastboot on your device. Not that your changed something in build.prop. His logic is not flawed, whatever you did to lose access to the two essential parts of having a rooted phone is the flaw here.
Also simply doing build.prop edits should not make you lose access to TWRP nor being able to access fastboot - or did you relock your bootloader?
Click to expand...
Click to collapse
In stead of assuming what happened with my device how about y'all ask me the details first. But coming off the bat assuming that I just did foolishness is asinine.
I was trying to revert to stock with the build prop so I could upgrade my phone. so I edited the prob and removed the lines I added to get Google assistant in the first place but it crashed and when I entered TWRP to push the build prop. When that didn't work I flashed the stock tot file which got my phone working but I wanted to upgrade so I found the page in XDA to flash the kdz with LGup which I was doing but half way through it failed and Twrp was gone which started this snow ball effect.
So once again where's the stupidity on my part when I didn't know that my phone was still going to be labeled a a pixel after a factory reset? Please, both of you have several seats in the back.
All I'm doing is warning people about what could possibly happen. Y'all can miss me with your unnecessary opinions and comments.

No I appreciate you wanting to warn the community, but you most certainly did not post that story. You posted saying you got bricked from doing edits to your build.prop and then because of using a Google assitant mod you are hard bricked. Post that entire story as a warning because even having your phone appear as a Pixel won't do any harm - but flashing a .kdz and having it fail midway may indeed cause harm. Lack of details causes much misinformation to spread around quickly

twistedvip said:
No I appreciate you wanting to warn the community, but you most certainly did not post that story. You posted saying you got bricked from doing edits to your build.prop and then because of using a Google assitant mod you are hard bricked. Post that entire story as a warning because even having your phone appear as a Pixel won't do any harm - but flashing a .kdz and having it fail midway may indeed cause harm. Lack of details causes much misinformation to spread around quickly
Click to expand...
Click to collapse
My bad I'll edit it. And apologies for the response tone.

It's called taking responsibility. You had a phone with root and did something stupid. Instead of taking responsibility you lie and tell them the phone is defective. That is 100% your fault. I bet it worked fine before you started messing with it. Whatever man I'm gonna let this be but you can bet that when these companies look at the supposed drfrctive returned phones and see they have been tamperred with and that people are being dishonest to get a new phone when they're the sole reason the phone stopped working, eventually they will all say screw it and just lock everything down.
Hopefully you learned from this.

markbencze said:
It's called taking responsibility. You had a phone with root and did something stupid. Instead of taking responsibility you lie and tell them the phone is defective. That is 100% your fault. I bet it worked fine before you started messing with it. Whatever man I'm gonna let this be but you can bet that when these companies look at the supposed drfrctive returned phones and see they have been tamperred with and that people are being dishonest to get a new phone when they're the sole reason the phone stopped working, eventually they will all say screw it and just lock everything down.
Hopefully you learned from this.
Click to expand...
Click to collapse
Actually the phone had a few random rebootsa and use to freeze on stock. I decided to keep it because of the note 7 fiasco and I was too frustrated and pissed to return it and then they ran out. So this was well over due. But once again you know nothing Jon snow. And yes I did lie but this device already had issues. Soooo???

S6 G920F stuck on boot logo

Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew

andrew88 said:
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
Click to expand...
Click to collapse
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.

I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
TerribleChoices said:
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
Click to expand...
Click to collapse

andrew88 said:
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
Click to expand...
Click to collapse
Oh dear.
Yeah it does sound like something got deeply ****ed up in this case. I had the luck to somehow get past the smart switch error when the phone died of low battery. As I attached it to the charger I quickly boot it into download mode before the screen would become a bootloop again and that's where I was able to reinstall the latest version of TWRP recovery. After that, I was able to flash a stock ROM of Nougat that didn't have a ****ed up bootloader like I had. Specifically the one from this thread: https://forum.xda-developers.com/galaxy-s6/help/device-5-binary-3-s6-sm-g920f-t3706025
by forumber2.
It's the Netherlands stock-ROM. Not sure if you're from the US and the carrier would be wrong with that CSC, but it was a good bet for me. I got my phone back to working normally now.
Worst case scenario I'd say see if you have a phone repair shop nearby and ask them an opinion on what could be wrong. I'm just an amateur like you.
Still, I wish you the best of luck with it. Maybe there's still some hope. :/