Database Info

Easier Root Method?

I know root is achieved with a tot file for the G5 but will there be a one script method like for the g3? I haven't rooted my phone yet because I dont want to risk bricking my phone.

RicardoSal24 said:
I know root is achieved with a tot file for the G5 but will there be a one script method like for the g3? I haven't rooted my phone yet because I dont want to risk bricking my phone.
Click to expand...
Click to collapse
there won't be a script for this as there are no instructions for the bootloader to flash any file. The reason they are using the TOT method is because we have no other way to write to the device. ADB is enabled but the actual command needed to copy everything over was left out.

fatapia said:
there won't be a script for this as there are no instructions for the bootloader to flash any file. The reason they are using the TOT method is because we have no other way to write to the device. ADB is enabled but the actual command needed to copy everything over was left out.
Click to expand...
Click to collapse
Is rooting the phone ASAP worth the time or is it best to wait awhile after a software update?

RicardoSal24 said:
Is rooting the phone ASAP worth the time or is it best to wait awhile after a software update?
Click to expand...
Click to collapse
if you haven't taken that 10d update I would just root now. Not sure if you've seen the thread where they are discussing the possibility of using the TOT method with the new 10d file, but once you update it trips something (qfuse I believe, Autoprime is the one who discovered this AFAIK) that prevents you from using the existing TOT on the forum and from downgrading.
once you root, you can update to 10d and as long as you flash supersu you will still have access to TWRP and root on the latest update. I recommend waiting updating to 10d even after rooting until they iron out all the issues though.
edit: have you done the OEM unlock through dev options yet? it will wipe your phone in the process FYI so make sure you have everything backed up.

Come on. It wasn't that hard to root it. Just follow the directions. Easy!

How do I know if I have the 10d update? I unlocked the bootloader, rooted it, then thought I had a quality control issue with the pain on the frame. So I flashed stock and locked the bootloader to prepare for a warranty exchange. Turns out the paint wasn't bubbling. It was the protective plastic adhesive I had never taken off. I'm stupid, I know, lol. Now I want to root again but I don't know about the 10d update.

rebelde80 said:
How do I know if I have the 10d update? I unlocked the bootloader, rooted it, then thought I had a quality control issue with the pain on the frame. So I flashed stock and locked the bootloader to prepare for a warranty exchange. Turns out the paint wasn't bubbling. It was the protective plastic adhesive I had never taken off. I'm stupid, I know, lol. Now I want to root again but I don't know about the 10d update.
Click to expand...
Click to collapse
about phone/software version

fatapia said:
if you haven't taken that 10d update I would just root now. Not sure if you've seen the thread where they are discussing the possibility of using the TOT method with the new 10d file, but once you update it trips something (qfuse I believe, Autoprime is the one who discovered this AFAIK) that prevents you from using the existing TOT on the forum and from downgrading.
once you root, you can update to 10d and as long as you flash supersu you will still have access to TWRP and root on the latest update. I recommend waiting updating to 10d even after rooting until they iron out all the issues though.
edit: have you done the OEM unlock through dev options yet? it will wipe your phone in the process FYI so make sure you have everything backed up.
Click to expand...
Click to collapse
I've had an understanding that updating android versions while being rooted may cause the phone to be bricked

i have software version 10a that is rootable right thats not 10d or are they similar.

RicardoSal24 said:
I've had an understanding that updating android versions while being rooted may cause the phone to be bricked
Click to expand...
Click to collapse
that may have been true at some point especially with OEM FW, but as far as custom I rooted then updated for my GS4, G3, and v10. Just because it worked for me doesn't mean it will for anyone else. I had the variants that once they were rooted you held on to it like dear life

fatapia said:
that may have been true at some point especially with OEM FW, but as far as custom I rooted then updated for my GS4, G3, and v10. Just because it worked for me doesn't mean it will for anyone else. I had the variants that once they were rooted you held on to it like dear life
Click to expand...
Click to collapse
So then its best to wait until something is done with the update?

RicardoSal24 said:
So then its best to wait until something is done with the update?
Click to expand...
Click to collapse
from what I've read the method is established now and there is "zero" risk as long as you follow the instructions, I haven't updated because I haven't experienced the issues others are having

fatapia said:
from what I've read the method is established now and there is "zero" risk as long as you follow the instructions, I haven't updated because I haven't experienced the issues others are having
Click to expand...
Click to collapse
I think I'll play it safe until its 100% or wait for a new android version with a root method

RicardoSal24 said:
I think I'll play it safe until its 100% or wait for a new android version with a root method
Click to expand...
Click to collapse
it's never 100% safe, hence the quotation marks. there's always a risk of something going wrong such as a power outage, or bad file download. As long as you verify the md5sum of your files you shouldn't have a problem with rooting, the only problems I've seen are people trying to use the wrong files on their device. up to you tho man, good luck with which ever you decide

This root method (compared to my old EVO 3D which needed juopunutbear and a wire)....ez pz.

lordodin912 said:
This root method (compared to my old EVO 3D which needed juopunutbear and a wire)....ez pz.
Click to expand...
Click to collapse
That sounds like fun, if you ask me. What was the wire for, if you don't mind me asking? Bypassing a fuse?

xanderin said:
That sounds like fun, if you ask me. What was the wire for, if you don't mind me asking? Bypassing a fuse?
Click to expand...
Click to collapse
It was needed for s-off, so not tech for root (if i remember correctly) but for being able to flash custom roms and such. Theres youtube videos about it.

[LG-H918 TMO] [TOTs]

As promised,
here above you have some TOTs just created and only for Development use
This image files are been created in Stock bootloader locked mode, but should be the same as unlocked mode for sure.
V 10d TOTs
Stock FULL TOT -----> LINK
Stock System and boot partitions TOT -----> LINK
Stock only Recovery TOT -----> LINK
Stock only Boot Partitions TOT -----> LINK

Sick! Do these flash correctly though? Have you tested on your device?

Honestly Annoying said:
Sick! Do these flash correctly though? Have you tested on your device?
Click to expand...
Click to collapse
Still not Bro.
Waiting @tungkick to have a way to always go back, but i'm pretty sure if you flash only recovery TOT for example, you don't have any risk of brick nothing

wolfgart said:
Still not Bro.
Waiting @tungkick to have a way to always go back, but i'm pretty sure if you flash only recovery TOT for example, you don't have any risk of brick nothing
Click to expand...
Click to collapse
Alright, I am going to attempt to make a TOT with TWRP. Just need the TWRP file from @jcadduono

Honestly Annoying said:
Alright, I am going to attempt to make a TOT with TWRP. Just need the TWRP file from @jcadduono
Click to expand...
Click to collapse
He already posted it on his website a few pages back. Check it out

arjuna_ said:
He already posted it on his website a few pages back. Check it out
Click to expand...
Click to collapse
Oh damn, I'll check that out! Totally missed that, my bad

Wait. Is there a TWRP for the T-Mobile V20??...

stanleyopar2000 said:
Wait. Is there a TWRP for the T-Mobile V20??...
Click to expand...
Click to collapse
There is a twrp recovery.img, but it's not yet flashable.

What is @tungkick website where I can find all of this stuff? Looking forward to flashing everything in the near future.

stanleyopar2000 said:
Wait. Is there a TWRP for the T-Mobile V20??...
Click to expand...
Click to collapse
Yes, there seems to be one already, but as far as i know it is not flashable yet.
Look on this thread:
http://forum.xda-developers.com/v20...-stock-tot-t3484982/post69308906#post69308906

I have a bricked v20 and I have tried flashing this .tot and the other posted in this forum and I keep getting error messages at 9% on all attempts on two windows machines. Any ideas on what this issue could be? I am using LGUP version 1_14_3. Is this the latest build or the build compatible with the V20? Drivers were latest I could find also using the LG common.dll which I needed for LGUP to recognize the V20. This is my only way out of brick I think. Any suggestions would be greatly appreciated. Thanks

bud951 said:
I have a bricked v20 and I have tried flashing this .tot and the other posted in this forum and I keep getting error messages at 9% on all attempts on two windows machines. Any ideas on what this issue could be? I am using LGUP version 1_14_3. Is this the latest build or the build compatible with the V20? Drivers were latest I could find also using the LG common.dll which I needed for LGUP to recognize the V20. This is my only way out of brick I think. Any suggestions would be greatly appreciated. Thanks
Click to expand...
Click to collapse
mate, as of today, i have read that there is no dll file for the v20. i.e there is no updated dll file to recognise the v20 in lgup.
u might want to wait a bit longer before u can unbrick your phone.

frostmore said:
mate, as of today, i have read that there is no dll file for the v20. i.e there is no updated dll file to recognise the v20 in lgup.
u might want to wait a bit longer before u can unbrick your phone.
Click to expand...
Click to collapse
Not good news.. it is just the dll? I mean i knew it had to be a missing piece because it was ready to flash. Every file failed at the same time. If anyone hears anything please post here or PM me just for a heads up. Im sure a few other desperate souls out there are anxiously waiting. Any reason the flash tools are incomplete? It doesnt seem like a big deal. Can someone here in the forum make one? Just couious.. i would gladly donate. Thanks for the info.

bud951 said:
Not good news.. it is just the dll? I mean i knew it had to be a missing piece because it was ready to flash. Every file failed at the same time. If anyone hears anything please post here or PM me just for a heads up. Im sure a few other desperate souls out there are anxiously waiting. Any reason the flash tools are incomplete? It doesnt seem like a big deal. Can someone here in the forum make one? Just couious.. i would gladly donate. Thanks for the info.
Click to expand...
Click to collapse
I don't think the flash tool is meant to be public, so they are probably leaked files.
I have a soft bricked LG V20 and have tried the LGUP DLL for every LG phone model I could find. The most progress I got was with the LG G5 dll and it only went to 10%.

bud951 said:
Not good news.. it is just the dll? I mean i knew it had to be a missing piece because it was ready to flash. Every file failed at the same time. If anyone hears anything please post here or PM me just for a heads up. Im sure a few other desperate souls out there are anxiously waiting. Any reason the flash tools are incomplete? It doesnt seem like a big deal. Can someone here in the forum make one? Just couious.. i would gladly donate. Thanks for the info.
Click to expand...
Click to collapse
not really sure as i am new to LG.
been reading up on xda relating to flashing and rooting (i came from samdung phones) this baby. i think being patient here is what you can do at the moment.also, not only the dll file is missing, i read twrp is not saving backup properly due to the new security protocols in place android 7.0.
take heart mate,i know it sucks to have a bricked phone.

all im getting is "Unknown Model"

Managed to soft brick my H918 as well, so if anyone working on this needs a tester, I'd love to get my phone back.

Perion said:
Managed to soft brick my H918 as well, so if anyone working on this needs a tester, I'd love to get my phone back.
Click to expand...
Click to collapse
Check here
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page13
Sent from my Pixel XL using Tapatalk

alane708 said:
Check here
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page13
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I appreciate it, wish I'd seen that the day before. I tried to go back to stock recovery to see if that would fix my boot loop issue, so, without access to TWRP, I'm hosed until we have a method to reflash recovery from Fastboot or Update modem connection..

I am screwed as well, I messed my phone up too, and when I turn my phone on it automatically goes the to the upgrade mode screen, I want to through away this damn phone, hehehe.

Can't find matched carrier. Check NT-code: FFFFFF : 84

I had 10ulm and flashed it with the G710AWM and now every time I boot my phone i get:
WARNING: Current version is not available for user. Can't find matched carrier. Check NT-code: FFFFFF : 84
The phone works fine since it was unlocked, but I am getting a ton of calls go straight to voicemail and this may be the issue? How can I fix this?
any help appreciated. Thanks

also wifi calling is nowhere to be found under call settings. It seems like I don't have the setting on this version? thoughts

Don't bother pal, stick with the official rom, I had this same issue best option is to just stick with the same variant as your phone, might not be latest but it works good. FYI I have g710emw and was using g710em rom

rash.m2k said:
Don't bother pal, stick with the official rom, I had this same issue best option is to just stick with the same variant as your phone, might not be latest but it works good. FYI I have g710emw and was using g710em rom
Click to expand...
Click to collapse
You are probably right. What a pain to have to flash again and go back?
How are you guys backing up so that you just restore to the same phone you had without having to set up everything again?

Brighter85 said:
You are probably right. What a pain to have to flash again and go back?
How are you guys backing up so that you just restore to the same phone you had without having to set up everything again?
Click to expand...
Click to collapse
I didn't restore, I tried out the rom first, and then just wiped it. What broke it for me was the wifi mac address somehow became lost while using it, maybe some software glitch only by flashing the same variant was I able to restore it.
Best to root and then backup and restore

Brighter85 said:
I had 10ulm and flashed it with the G710AWM and now every time I boot my phone i get:
WARNING: Current version is not available for user. Can't find matched carrier. Check NT-code: FFFFFF : 84
The phone works fine since it was unlocked, but I am getting a ton of calls go straight to voicemail and this may be the issue? How can I fix this?
any help appreciated. Thanks
Click to expand...
Click to collapse
Just reinstall the kdz with refurbish option

dapolicy said:
Just reinstall the kdz with refurbish option
Click to expand...
Click to collapse
Hey there, how do you do this KDZ with refurbish option? Will this mean flashing again anyways?
I was hoping that by now the official android 10 version from LG would be out for the unlocked 10ulm, but it seems that they will never update this phone for some reason. This was the Google Fi unlocked G7.
Suggestions please. Thanks

Brighter85 said:
Hey there, how do you do this KDZ with refurbish option? Will this mean flashing again anyways?
I was hoping that by now the official android 10 version from LG would be out for the unlocked 10ulm, but it seems that they will never update this phone for some reason. This was the Google Fi unlocked G7.
Suggestions please. Thanks
Click to expand...
Click to collapse
It means flashing the phone again but select refurbish option in lgup

dapolicy said:
It means flashing the phone again but select refurbish option in lgup
Click to expand...
Click to collapse
Thanks for replying.
I noticed you are the leader of the other thread I posted, so I will ask here so not to bug you too much
Will the choosing of refurbish option erase the serial or IMEI or anything else that I should be aware of?
Also, when you say flash again you mean using the canadian version correct? I was wondering about the Korean version vs the canadian and what advantage would there be in any.
If you could, please lead me to the instructions to flash again. When I did it, I used a guide from some dude on youtube and I can't find that again.
Also, read somewhere that the error at boot could be fixed by rooting and then changing something with the explorer app. Not sure if that is worth it. I just hate backing up and restoring to find I am logged out of most every app and all settings have to be set up again. It takes me hrs and I am not that technically savvy as you guys.
Thanks for your time and have a good evening.

Brighter85 said:
Thanks for replying.
I noticed you are the leader of the other thread I posted, so I will ask here so not to bug you too much
Will the choosing of refurbish option erase the serial or IMEI or anything else that I should be aware of?
Also, when you say flash again you mean using the canadian version correct? I was wondering about the Korean version vs the canadian and what advantage would there be in any.
If you could, please lead me to the instructions to flash again. When I did it, I used a guide from some dude on youtube and I can't find that again.
Also, read somewhere that the error at boot could be fixed by rooting and then changing something with the explorer app. Not sure if that is worth it. I just hate backing up and restoring to find I am logged out of most every app and all settings have to be set up again. It takes me hrs and I am not that technically savvy as you guys.
Thanks for your time and have a good evening.
Click to expand...
Click to collapse
Flash with the kdz you used before, Canadian firmware is better than Korean. In lgup select refurbish instead of partition dl. It won't tamper with your IMEI and you will loose all your data

Hi dapolicy,
I am done with the LG G7ULM since it will never be updated officially.
I really like having the fingerprint sensor on the back and it seems that the LG G8 is the last iteration of phones from LG with this feature and it is an upgrade from the G7.
It is cheap here in the US.
Which version of this phone should I look for? I will be using it on Mint Mobile, so an unlocked one sounds great and all, but then you see what happened to the G7 ULM that never got android 10 unless it was tied to a carrier.
So, what do you suggest I do so I can get the next couple of updates for android with the G8?
Thanks man!

dapolicy said:
Just reinstall the kdz with refurbish option
Click to expand...
Click to collapse
I get the sime problem with my LG WING and I don't know to solve it

Daoud ben said:
I get the sime problem with my LG WING and I don't know to solve it
Click to expand...
Click to collapse
If the firehose was available for the Wing/Velvet you can hex the FTM and fix the NT Code on the Wing.You can try the engineering service menu,but I highly doubt the IMPL is 0 under MID.

OnePlus 8 TMO Missing IMEI and can't unlock bootloader

Hey yall, I really need some help.
So some back story:
I started using a oneplus 8 TMO version and wanted to unlock the bootloader to get android 12 and root the phone. So I went through the process of getting an unlock token and when I finally got it, unlocked my bootloader, flashed the global version of oxygen os, and got it updated to android 12. Everything was working great. So then I wanted to root the phone so I downloaded twrp, booted into fastboot, and tried flashing it. The phone then booted into the system even though I told it to boot into recovery. After about a minute or so it froze and rebooted into a kernal panic. I unfortunately do not have what it said and cant repeat the process, but it booted into recovery and I clicked reason for boot and it said something about the kernal. So after a reboot it then went into crash dump mode. So I had to use the msm download tool (unfortunately I only had the tmo msm version and thought I could just repeat the process because I had slow internet and didnt want to download the global msm tool) to get the phone working again. So booted into edl mode, reflashed the phone, and it booted up. The problem now is that I do not have an IMEI number. I have a wifi address, bt address, and everything else that makes me assume that the efs partition is still ok (but I dont know enough to debate that) but it does not recognize my sim card. The phone also freezed and restarts approximately every 30 seconds.
And now my problem and what I have tried:
Because I have no IMEI I cannot enable oem unlocking in developer settings, cant flash anything in the bootloader - including the unlock token - and can barely do anything in the system because it only stays on for small amounts of time. I have tried many imei write tools such as qualcomm smartphone write imei, readnwrite tool, fastboot imei writer, miracle box, and I think some others but none of them recognize my phone. Ive also tried the oneplus debloat and oem unlock script to try and bypass the setting but it didnt do anything. I have dialed *#801# and was able to enable engineering mode and diag toggle but it still didnt do anything for me. So I really dont know what to do any more. When in the bootloader or recovery the phone does not reboot, so I can stay there as long as I need. Any help on this would be greatly, greatly, greatly appreciated.

Have you tried using the MSMTool again?

Xryphon said:
Have you tried using the MSMTool again?
Click to expand...
Click to collapse
Yeah unfortunately that hasn't worked... I've done it miltiple times with the T-Mobile one and can't use any other one because I don't have an unlocked bootloader... If I had a way to bypass the oem unlocking option in the settings then I might have a chance to fix it but don't know how to do that...

try using this version of msmtool(i use MsmDownloadTool V4.0_Win7 on windows 10). it's a bit newer version(5.2.89) i extracted from OP9Pro file. replace the version from whichever unbrick file you download. worked for me. but don't upgrade to android 12 again, the same issue will happen

gingerboy92 said:
try using this version of msmtool(i use MsmDownloadTool V4.0_Win7 on windows 10). it's a bit newer version(5.2.89) i extracted from OP9Pro file. replace the version from whichever unbrick file you download. worked for me. but don't upgrade to android 12 again, the same issue will happen
Click to expand...
Click to collapse
Thanks for the response! And I am so sorry but what do you mean by unbrick file? I just had to download the tmobile version of the msm tool. I mean to be fair it was uploaded by someone so they probably pre programmed it but I unfortunately dont have the knowledge for that. I am also using msmdownloadtool v4.0. Do you happen to have the links to what you are referring to?
Heres the link to the one that I have downloaded: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4093043/
Thanks!
EDIT: so once you said that I actually went to the link and there were various versions. So I tried another one and it didn't work but then tried one more and my IMEI was back! I have no idea why that happened but thanks for the idea! I was so happy.

shubbyshoes said:
Thanks for the response! And I am so sorry but what do you mean by unbrick file? I just had to download the tmobile version of the msm tool. I mean to be fair it was uploaded by someone so they probably pre programmed it but I unfortunately dont have the knowledge for that. I am also using msmdownloadtool v4.0. Do you happen to have the links to what you are referring to?
Heres the link to the one that I have downloaded: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4093043/
Thanks!
EDIT: so once you said that I actually went to the link and there were various versions. So I tried another one and it didn't work but then tried one more and my IMEI was back! I have no idea why that happened but thanks for the idea! I was so happy.
Click to expand...
Click to collapse
yeah, that's it. it's related to version of msmdownloadtool. some of them must have a newer version. i had the idea from someone else on this forum too. glad it helps. be careful not upgrade to android 12 for now. i think it's because of the way oos12 detects phone varient causing the modem to go crazy. not sure tho. would love to see someone figures it out

gingerboy92 said:
yeah, that's it. it's related to version of msmdownloadtool. some of them must have a newer version. i had the idea from someone else on this forum too. glad it helps. be careful not upgrade to android 12 for now. i think it's because of the way oos12 detects phone varient causing the modem to go crazy. not sure tho. would love to see someone figures it out
Click to expand...
Click to collapse
Yeah, OOS 12 messed up my phone for a bit until I was able to get OOS 11 back on both slots.

shubbyshoes said:
Thanks for the response! And I am so sorry but what do you mean by unbrick file? I just had to download the tmobile version of the msm tool. I mean to be fair it was uploaded by someone so they probably pre programmed it but I unfortunately dont have the knowledge for that. I am also using msmdownloadtool v4.0. Do you happen to have the links to what you are referring to?
Heres the link to the one that I have downloaded: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4093043/
Thanks!
EDIT: so once you said that I actually went to the link and there were various versions. So I tried another one and it didn't work but then tried one more and my IMEI was back! I have no idea why that happened but thanks for the idea! I was so happy.
Click to expand...
Click to collapse
which worked for you?

Question Desperately need assistance

Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.

psorincatalin87 said:
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
Click to expand...
Click to collapse
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.

V0latyle said:
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
Click to expand...
Click to collapse
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).

psorincatalin87 said:
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
Click to expand...
Click to collapse
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.

V0latyle said:
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
Click to expand...
Click to collapse
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!

psorincatalin87 said:
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
Click to expand...
Click to collapse
I downloaded the firmware with Frija and I get the same issue with Odin.

psorincatalin87 said:
I downloaded the firmware with Frija and I get the same issue with Odin.
Click to expand...
Click to collapse
What options do you have checked in Odin?

V0latyle said:
What options do you have checked in Odin?
Click to expand...
Click to collapse
I haven't touched any of the options, everything is on default.

While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.

nsfnd said:
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
Click to expand...
Click to collapse
OH.MY.GOD! Thank you very much, man! I love you! I could kiss you right now, stranger!

Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.

nsfnd said:
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
Click to expand...
Click to collapse
Nah, this is my last one.

psorincatalin87 said:
Nah, this is my last one.
Click to expand...
Click to collapse
don't be that way lol, it's fun, just do it on hardware you own. get a cheap phone off ebay to play with