Database Info

VZN locked, Pixel stuck at bootloader, recovery mode fails -- what now?

Hi all,
I have an OG Verizon Pixel that's now stuck at the bootloader. I haven't done any unlocking or ROM modifications. It was stock 8.1 and it broke pretty close to the January update.
Recovery mode says "Failed to boot to recovery mode".
Starting from the bootloader just loads back into it, but the screen gets off-centered (I can attach pics if it helps).
When the phone was working, I'd never done any of the in-OS tools to start the bootloader unlocking process. I'm not really sure what I should be trying, but nothing I have tried from fastboot seems to work because it's locked. I feel if I could reimage it all, maybe it would work again, but it doesn't look like I have that kind of access.
Verizon's only option was $150 to replace it out of warranty (and then only provided a 90-day warranty). I declined that and got a Pixel 2, but now I have the old phone. Is there anything I can do with it? Or is it just junk?
Thanks,
TBK

TromboneKenny said:
Hi all,
I have an OG Verizon Pixel that's now stuck at the bootloader. I haven't done any unlocking or ROM modifications. It was stock 8.1 and it broke pretty close to the January update.
Recovery mode says "Failed to boot to recovery mode".
Starting from the bootloader just loads back into it, but the screen gets off-centered (I can attach pics if it helps).
When the phone was working, I'd never done any of the in-OS tools to start the bootloader unlocking process. I'm not really sure what I should be trying, but nothing I have tried from fastboot seems to work because it's locked. I feel if I could reimage it all, maybe it would work again, but it doesn't look like I have that kind of access.
Verizon's only option was $150 to replace it out of warranty (and then only provided a 90-day warranty). I declined that and got a Pixel 2, but now I have the old phone. Is there anything I can do with it? Or is it just junk?
Thanks,
TBK
Click to expand...
Click to collapse
Try reflashing the same factory image ur on

If the bootloader isn't unlocked it is probably bricked. With an unlocked bootloader you could reflash a factory image and get it working but you cant do that with a locked bootloader.

shagbag913 said:
If the bootloader isn't unlocked it is probably bricked. With an unlocked bootloader you could reflash a factory image and get it working but you cant do that with a locked bootloader.
Click to expand...
Click to collapse
I could be wrong but I think u might be able to sideload like an Oreo preview build without bl unlock, idr though but yeah tl:;dw: your device is likely as bricked as a house so you should attempt to request and RMA

KittyRgnarok said:
I could be wrong but I think u might be able to sideload like an Oreo preview build without bl unlock, idr though but yeah tl:;dw: your device is likely as bricked as a house so you should attempt to request and RMA
Click to expand...
Click to collapse
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong

shagbag913 said:
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
Click to expand...
Click to collapse
Yeah that's what I'm thinking. OP test this and if anything breaks report back

That's pretty odd that it would just break like that. If he hasn't messed with anything software related it could be a hardware issue

shagbag913 said:
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
Click to expand...
Click to collapse
I can't even get into recovery mode. It errors (see OP for the message). Would it be different if I initiated recovery mode from fastboot or adb?

TromboneKenny said:
I can't even get into recovery mode. It errors (see OP for the message). Would it be different if I initiated recovery mode from fastboot or adb?
Click to expand...
Click to collapse
I don't think it would be different. This sounds like a hardware issue, not software.

Is this my fault or a hardware issue? (ERROR: Slot Unbootable: Load Error)

Okay, so my phone is bricked and there's no recovering it. RMA is already ordered and on it's way. Essentially I'm in the same situation as this poor soul (and many others, from the results of searching for this error in the forums).
What I want to know is if I did this or if this was something I couldn't have foreseen. The phone had an unlocked boot loader with the latest OS (Pie) & security updates (November). No custom ROM or kernel - stock everything, though I did have Magisk installed. Today I decided to re-lock my bootloader. While the device was in fastboot mode I issued the command "fastboot flashing lock" and followed the phone's on-screen directions. When it finished and tried to reboot, it would only go the fastboot mode with the message "ERROR: Slot Unbootable: Load Error".
I recognize that locking the bootloader may have been the last straw for some present flaw - like a weak engine finally giving out after long service. Is that the case here or is there some step I missed that would have prevented this from happening? I ask because I don't want to repeat a mistake in the future.

u found any way to unbrick your phone?

yuva_cool said:
u found any way to unbrick your phone?
Click to expand...
Click to collapse
Nope. The RMA was approved and I'm using a new (refurbished) device.

U had an unlocked bootloader and yet your RMA was approved? @computerslayer

yuva_cool said:
U had an unlocked bootloader and yet your RMA was approved? @computerslayer
Click to expand...
Click to collapse
The error showed up when I relocked the bootloader, so it was locked when I submitted the RMA. They approved it (and didn't demand a payment when they received the RMA'd phone), so I suppose they accepted that it was a warrantied issue.

computerslayer said:
The error showed up when I relocked the bootloader, so it was locked when I submitted the RMA. They approved it (and didn't demand a payment when they received the RMA'd phone), so I suppose they accepted that it was a warrantied issue.
Click to expand...
Click to collapse
Did you flash the stock boot image before you relocked? If not, Magisk was still installed and that's where you went wrong. You need to be completely stock when you relock the phone.
If you ever relock the phone you have now, to be on the safe side, I'd flash the factory image and leave the -w in the flashall batch file. Your phone will get wiped when you relock it anyway so you won't be out anything if you do so.

robocuff said:
Did you flash the stock boot image before you relocked? If not, Magisk was still installed and that's where you went wrong. You need to be completely stock when you relock the phone.
If you ever relock the phone you have now, to be on the safe side, I'd flash the factory image and leave the -w in the flashall batch file. Your phone will get wiped when you relock it anyway so you won't be out anything if you do so.
Click to expand...
Click to collapse
I am abashed to have to report that I did not flash the stock boot image. I wondered if Magisk was the cause, but assumed that the wipe caused by relocking would take care of that too.

computerslayer said:
I am abashed to have to report that I did not flash the stock boot image. I wondered if Magisk was the cause, but assumed that the wipe caused by relocking would take care of that too.
Click to expand...
Click to collapse
If that's the case, it's a certainty that that's the cause of your problem. You have to be completely stock when you relock it. Flashing the factory boot image should take care of that if all you have done is installed Magisk. That said, I'd still flash the factory image and let it do the wipe, just to be sure.

computerslayer said:
Okay, so my phone is bricked and there's no recovering it. RMA is already ordered and on it's way. Essentially I'm in the same situation as this poor soul (and many others, from the results of searching for this error in the forums).
What I want to know is if I did this or if this was something I couldn't have foreseen. The phone had an unlocked boot loader with the latest OS (Pie) & security updates (November). No custom ROM or kernel - stock everything, though I did have Magisk installed. Today I decided to re-lock my bootloader. While the device was in fastboot mode I issued the command "fastboot flashing lock" and followed the phone's on-screen directions. When it finished and tried to reboot, it would only go the fastboot mode with the message "ERROR: Slot Unbootable: Load Error".
I recognize that locking the bootloader may have been the last straw for some present flaw - like a weak engine finally giving out after long service. Is that the case here or is there some step I missed that would have prevented this from happening? I ask because I don't want to repeat a mistake in the future.
Click to expand...
Click to collapse
I have this issue and now my pixel 2 cant boot. It stuck. Cant enter fastboot. This is my last experience with pixel series devices. Its expensive phone, but its too sensitive to brick. I dont know why, an update or a flashing stock rom can make your phone totally unuseable. I just cant accept it

I had exactly the same issue. just keep holding the power button with or without the vol- for a good 30~ seconds or so (it will restart several times) but keep holding.
and make sure you are connected to the PC until you hear the ding that the phone got recognized, then the phone will accept fastboot commands.
This worked for me before I was going to throw the phone in the garbage!

Pixel bricked with locked bootloader

Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).

You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.

post-mortem said:
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Click to expand...
Click to collapse
That unfortunatly doesn't work. It's only for unlocked or at least unlockable deviced. I still tried it, but most fastboot commands require the bootloader to be unlocked. flashing unlock, flashing unlock_critical oem unlock, flash, format, boot, --set-active all don't work with a non-unlockable bootloader.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Click to expand...
Click to collapse
Also fails with 'oem unlock is not allowed'.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
Click to expand...
Click to collapse
Fails with 'Command is not supported. Please unlock device to enable this command.'

This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905

junglism93 said:
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
Click to expand...
Click to collapse
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.

Marvin0509 said:
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Click to expand...
Click to collapse
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Sent from my Pixel using XDA Labs

junglism93 said:
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Click to expand...
Click to collapse
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.

Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
Definitely seems a non recoverable scenario and happy days on getting it RMA'd for free :good:
Sent from my Pixel using XDA Labs

Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
It's over a year old right?? And they RMAed it for free?

aholeinthewor1d said:
It's over a year old right?? And they RMAed it for free?
Click to expand...
Click to collapse
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.

Marvin0509 said:
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Click to expand...
Click to collapse
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?

post-mortem said:
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
Click to expand...
Click to collapse
No, I told them the whole truth, that I rooted it, modified the system, and that it doesn't work at all anymore.

Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks

HeinrichSpy said:
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
Click to expand...
Click to collapse
I have a subscription for Google One, so I contacted support from one.google.com. They quickly talked to me, then added a Pixel support employee to the conversation. I think I could have also contacted Pixel support directly on this page: support.google.com/pixelphone/contactflow. However I'm not sure if this will work in your country, I'm from Germany and the page wants me to select my Pixel, then I could contact a support employee via chat or wait for a callback, but if I change the language to English, the page seems broken and is just blank.

Marvin0509 said:
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
Click to expand...
Click to collapse
i tried flashing a stock ota image...it was successful, but on reboot, nothing has changed. still the same. u know of a solution? i cant find it anywhere. thanks

Pixel 3 - unroot/lock bootloader

Hi,
Unfortunaltelly my magisk cant hide gpay (safetynet true). Im wondering about unroot my pixel3.
Please tell me, which way is the best to unroot/lock bootloader? If I flash blueline-image with - w in flash-all.bat, can i lock bootloader with any problems (bricks)? Sorry for my english.
Thx for advice.
Wysłane z mojego Pixel 3 przy użyciu Tapatalka

If you successfully flashed the factory image (no errors) without removing the -w flag you should be able to relock the bootloader, yes. I believe locking the bootloader will induce another wipe so be sure you have things backed up if you have used the phone since flashing the factory image.
I have not rooted my devices since Pixel 1 and things have changed since then so someone else can chime in to confirm, but flashing the full factory image should be a reliable way to return to pure stock.

I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.

jd1639 said:
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
Click to expand...
Click to collapse
Unrooted and unlocked will cause Google Pay not to work. I would suggest to just leave "Allow OEM unlocking" enabled.
'

83097markcynt said:
Unrooted and unlocked will cause Google Pay not to work. I would suggest to just leave "Allow OEM unlocking" enabled.
'
Click to expand...
Click to collapse
That's good to know. I don't use gpay so didn't know that.

Unlocking Verizon Bootloader
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.

jkday3 said:
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
Click to expand...
Click to collapse
I'm not sure what you're asking? Is what possible?

jkday3 said:
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
Click to expand...
Click to collapse
jd1639 said:
I'm not sure what you're asking? Is what possible?
Click to expand...
Click to collapse
You cannot unlock the bootloader on a Verizon device. It's software locked based on IMEI. The ones sold at Best Buy are Verizon versions and are fully locked.

Gpay works fine with magisk. If it's not working for you, I'd dig into why before unrooting and relocking.
If you don't want to do that, just flash the magisk uninstaller to get rid of root and then flash a custom kernel. Pretty much all custom kernels will hide an unlocked bootloader and allow you to pass safety net.

New here to this community.
I bought a pixel 3xl a few weeks ago and i wanted to root just to see what's new, but i now realize I don't need to root this almost perfect phone. I unrooted the phone with magisk. I have the factory img. File to use incase i did something wrong when rooting. I just want to be able to let my phone boot up normally again. Can someone please help me?

NightWingJbr said:
I bought a pixel 3xl a few weeks ago and i wanted to root just to see what's new, but i now realize I don't need to root this almost perfect phone. I unrooted the phone with magisk. I have the factory img. File to use incase i did something wrong when rooting. I just want to be able to let my phone boot up normally again. Can someone please help me?
Click to expand...
Click to collapse
I'm not sure what you mean by boot up normally? Do you mean the bootloader unlock warning when it first starts to boot? You can get rid of that by locking the bootloader but before I'd do that I'd flash the full factory image, including wiping the device with the -w not removed in the flash-all batch file.

jd1639 said:
I'm not sure what you mean by boot up normally? Do you mean the bootloader unlock warning when it first starts to boot? You can get rid of that by locking the bootloader but before I'd do that I'd flash the full factory image, including wiping the device with the -w not removed in the flash-all batch file.
Click to expand...
Click to collapse
Yes and thank you for your reply. J just want to know how to wipe the device" with the -w not removed in the flash-all batch file". That's the only thing i don't understand. If you could explain. So i can go back to boot up without the warning.

NightWingJbr said:
Yes and thank you for your reply. J just want to know how to wipe the device" with the -w not removed in the flash-all batch file". That's the only thing i don't understand. If you could explain. So i can go back to boot up without the warning.
Click to expand...
Click to collapse
See the "Factory reset via fastboot" section at https://forum.xda-developers.com/pixel-3/how-to/complete-pixel-3-how-to-guide-newbie-t3922269
This will not remove the warning at boot, but is a necessary step. To lock the bootloader, read all the posts (especially the ones that detail the consequences of relocking) at https://forum.xda-developers.com/pixel-3-xl/help/how-to-lock-bootloader-t3866074 and pick a method.
I strongly recommend against relocking the boot loader, though. It is easy to brick your phone during the relock process. Also, a locked bootloader severely limits your ability to recover a bricked phone. Just ignore the warning at boot message. Removing it may come at a high cost.

Thank you so much. I will ignore then..

what is -w..
jd1639 said:
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
Click to expand...
Click to collapse
i was wondering what -w is? probably a dumb question but i couldnt find anything on google about it

comic_nightwing said:
i was wondering what -w is? probably a dumb question but i couldnt find anything on google about it
Click to expand...
Click to collapse
In the flash-all batch file in the factory image the -w (part of a line in the batch file) controls whether it wipes clean or does a dirty install leaving apps and data (user).

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