Database Info

How to know bootloaders unlocked

Is there anywhere that says the bootloader is unlocked on the phone? I want to make sure in unlocked but its not like my nexus with the pad lock at startup screen.

tonytownsend said:
Is there anywhere that says the bootloader is unlocked on the phone? I want to make sure in unlocked but its not like my nexus with the pad lock at startup screen.
Click to expand...
Click to collapse
If i'm not mistaken the lock at boot is no longer there on the lower part of screen on boot up. I would check again but dont want to do the mms fix. try that

so just being able to do mms flash should prove its unlocked?

Like the poster above said, if you're "Unlock" symbol on restart is gone than you've successfully flashed the new bootloader

tonytownsend said:
so just being able to do mms flash should prove its unlocked?
Click to expand...
Click to collapse
Lol no.
When you reboot, does the first screen that says Samsung hang for a few seconds or does it just blow right by?
Sent from my SGS3 on Synergy Nightlies

tonytownsend said:
so just being able to do mms flash should prove its unlocked?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
all kidding aside that should be the quickest way to know if unlock worked for you

another easy way is to plug in phone and use your adb and type in: adb reboot bootloader
If you see: Qualcom Secureboot: ENABLED
then you have successfully unlocked your bootloader.

xraytedjim said:
another easy way is to plug in phone and use your adb and type in: adb reboot bootloader
If you see: Qualcom Secureboot: ENABLED
then you have successfully unlocked your bootloader.
Click to expand...
Click to collapse
It says ENABLED from the factory. Aside from the lack of Custom+padlock Samsung screen on boot (if you already had it) or flashing a kernel, there isn't really anything else at the moment.

xraytedjim said:
another easy way is to plug in phone and use your adb and type in: adb reboot bootloader
If you see: Qualcom Secureboot: ENABLED
then you have successfully unlocked your bootloader.
Click to expand...
Click to collapse
If you read through some other posts I think Adam or another dev posted that even with unlocked bootloader it will still say enabled. It is just a bug or something that cannot be changed regardless if bootloader is unlocked or not.
The only way to tell AFAIK for now is to try flashing a kernel. So hang tight kids until we get one released.
Sent from my Rooted, Synergized (1.7) and now unlocked bootloader VZW S3!

LinxuSx said:
If you read through some other posts I think Adam or another dev posted that even with unlocked bootloader it will still say enabled. It is just a bug or something that cannot be changed regardless if bootloader is unlocked or not.
The only way to tell AFIAK for now is to try flashing a kernel. So hang tight kids until we get one released.
Sent from my Rooted, Synergized (1.7) and now unlocked bootloader VZW S3!
Click to expand...
Click to collapse
There's a few ways to test it. I tested it by flashing a recovery through Odin and it worked. Another thing I noticed is that when you enter Download mode, there's less warning text then before about flashing a custom OS. You can also tell by quicker boot times.
Also the secure boot means the phone checks the partitions on boot to make sure they are valid (I believe this is only for the radio and boot loader partitions) as I THINK secure boot is enabled on every GS3, but may be wrong there.
Also another note, used triangle away on the unlocked boot loader to remove the count from flashing the custom recovery in Odin, and it worked without a hitch!

This is great
Thanks all!

So If I see the padlock on boot, does that mean I am locked? It is weird since when I had my GNex, the padlock meant it was unlocked.:fingers-crossed::fingers-crossed:

When it bots does it say custom with a lock inder it. If so that means rooted with locked bootloader. Use ez unlock 4.2 and it will go away.
Sent from my SCH-I535 using xda app-developers app

Toddricks said:
When it bots does it say custom with a lock inder it. If so that means rooted with locked bootloader. Use ez unlock 4.2 and it will go away.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I just flashed the stock root66 file, I want to unroot, how do I do that? Yes it says custom with lock under it. Does this mean that the stock firmware file is rooted? What is the correct file to unroot?
---------- Post added at 09:38 PM ---------- Previous post was at 09:35 PM ----------
Toddricks said:
When it bots does it say custom with a lock inder it. If so that means rooted with locked bootloader. Use ez unlock 4.2 and it will go away.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Also, When I open ez- unlock, it says "are you rooted?" Does this mean that the phone thinks I am rooted? I have the superuser app for some reason, but I am not rooted as it seems. Thanks for your help.

tonytownsend said:
Is there anywhere that says the bootloader is unlocked on the phone? I want to make sure in unlocked but its not like my nexus with the pad lock at startup screen.
Click to expand...
Click to collapse
I believe another way to check if you have the unlocked aboot.img file saved somewhere is to pull a copy of your phone's bootloader image via ADB and compare MD5's with the unsecure aboot.img

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

[Help] Phone Won't Leave Recovery

Hey guys. First I'd like to aplogize for posting so many help threads but I'm trying my best to figure it out on my own.
I was using one-click to stock when my mother dropped something and needed my help urgently, so I told my brother to start it up for me as my phone was already plugged in and connected. I am running the T959W rather than the T959V and my brother clicked on the option to flash bootloaders. The download was completed normally I think. However, my phone will not leave the recovery mode.
Could you guys please help? Thanks.
When flash bootloaders was hit on T959V back to stock, my brother said it said "MODEM UPLOAD FAILED ENDING SESSION". My guess is that it cleared my boot loader and then since it failed while trying to upload the modem, it ended the session without readding a boot loader? It continously says "MODEL UPLOAD FAILED" Whenever I attempt to use the T959V back to stock.
Edit:
I have tired the back to stock for T959W from: http://forum.xda-developers.com/showthread.php?t=1956025
However, I get these error messages.
Kernel is missing because I removed it out of the package hoping maybe it'd solve the problem since it was also failing, but so is recovery...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

WayTooGosu said:
Hey guys. First I'd like to aplogize for posting so many help threads but I'm trying my best to figure it out on my own.
I was using one-click to stock when my mother dropped something and needed my help urgently, so I told my brother to start it up for me as my phone was already plugged in and connected. I am running the T959W rather than the T959V and my brother clicked on the option to flash bootloaders. The download was completed normally I think. However, my phone will not leave the recovery mode.
Could you guys please help? Thanks.
Click to expand...
Click to collapse
Try instilling a new ROM
Sent from my SGH-T959V using xda app-developers app

Cooptx said:
Try instilling a new ROM
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I have tried installing AOKP Milestone 6 by team acid unofficial (ICS) and CM10 (JB) but the same thing keeps occuring.

I think you should look here if you haven't already
http://forum.xda-developers.com/showthread.php?t=1956025

TwitchyEye said:
I think you should look here if you haven't already
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
Yes I was trying that but for some reason it just kept failing "KERNEL UPLOAD FAILED" "RECOVERY UPLOAD FAILED"

WayTooGosu said:
Yes I was trying that but for some reason it just kept failing "KERNEL UPLOAD FAILED" "RECOVERY UPLOAD FAILED"
Click to expand...
Click to collapse
Sometimes heimdall is finicky so if you know for sure you got the drivers working and you followed instructions properly trying it a couple times in a row might do it....although I guess if you say it keeps failing that would imply more than once...

TwitchyEye said:
Sometimes heimdall is finicky so if you know for sure you got the drivers working and you followed instructions properly trying it a couple times in a row might do it....although I guess if you say it keeps failing that would imply more than once...
Click to expand...
Click to collapse
Yes it has failed every attempt (I''ve tried about 10 times).

At this point you should really start fresh maybe even a different computer and see if you get anywhere. Typically if it's not working it's a driver issue and you gotta get rid of all the drivers related to the phone and reboot, then re-install them using zadig...and maybe reboot again.

TwitchyEye said:
At this point you should really start fresh maybe even a different computer and see if you get anywhere. Typically if it's not working it's a driver issue and you gotta get rid of all the drivers related to the phone and reboot, then re-install them using zadig...and maybe reboot again.
Click to expand...
Click to collapse
I think the driver is being recognized fine because it is being recognized by ZDiag, T959V back to stock program, Hemidall. I am not quite sure what the problem is :|.

WayTooGosu said:
I think the driver is being recognized fine because it is being recognized by ZDiag, T959V back to stock program, Hemidall. I am not quite sure what the problem is :|.
Click to expand...
Click to collapse
Maybe the gods will chime in about now...?

I suggest using a new pc too. Sometimes its a simple conflict that is causing the problem and a different pc will fix it every time.

Try a different cable/port combo? Sometimes cables die at the worst times....
Sent from my SGH-T959V using xda app-developers app

eollie said:
I suggest using a new pc too. Sometimes its a simple conflict that is causing the problem and a different pc will fix it every time.
Click to expand...
Click to collapse
Hmm, I just tried it on my laptop, back to stock T959V flashs just fine however I still ahve the issue of being stuck in recovery mode but I can't get T959W to work still.

WayTooGosu said:
Hmm, I just tried it on my laptop, back to stock T959V flashs just fine however I still ahve the issue of being stuck in recovery mode but I can't get T959W to work still.
Click to expand...
Click to collapse
When flash bootloaders was hit on T959V back to stock, my brother said it said "MODEM UPLOAD FAILED ENDING SESSION". My guess is that it cleared my boot loader and then since it failed while trying to upload the modem, it ended the session without readding a boot loader? It continously says "MODEL UPLOAD FAILED" Whenever I attempt to use the T959V back to stock.

The problem is you are using the V HOC's there is a package for W phones on the forums.

eollie said:
The problem is you are using the V HOC's there is a package for W phones on the forums.
Click to expand...
Click to collapse
Yes I realize that however, I checked the T959W thread and they said there were no bootloaders. And that is likely the thing that is messed up right now. Thanks for your help!

I think there's no way to flash bootloaders on W's and the package that's specifically for the W was designed just for this purpose, to bring back a phone that's messed up from attempting to flash V bootloaders. Have you tried downloading it again? If that's the only one you have trouble with maybe it's just a bad download.
---------- Post added at 11:54 PM ---------- Previous post was at 11:52 PM ----------
Oh also you can go in and uncheck flash modem on the one-click and the rest of it should work just fine. I think.

TwitchyEye said:
I think there's no way to flash bootloaders on W's and the package that's specifically for the W was designed just for this purpose, to bring back a phone that's messed up from attempting to flash V bootloaders. Have you tried downloading it again? If that's the only one you have trouble with maybe it's just a bad download.
---------- Post added at 11:54 PM ---------- Previous post was at 11:52 PM ----------
Oh also you can go in and uncheck flash modem on the one-click and the rest of it should work just fine. I think.
Click to expand...
Click to collapse
How do you disable things from being flashed on the V back to stock?

WayTooGosu said:
How do you disable things from being flashed on the V back to stock?
Click to expand...
Click to collapse
This might help me just get the boot loaders fixed!

here is the deal unless you worked some weird voodoo magic you never flashed the V's bootloaders. There is a partition in there that will not allow it to work properly.
Rereading getochkn's instructions you should not be flashing the bootloaders as he DID NOT include them. Follow his directions to the letter. Dont use the one clicks for the V. I remember chatting with him in IRC while he was trying to figure this out and he could NOT flash a hoc for the V with bootloaders successfully I dont even think it worked without bootloaders.

URGENT: Phone is possibly Bricked (Samsung GS3)

Ok, So I installed LiquidSmooth and Gapps (or at least tried) then go to the last option (Reboot System) Now its stuck doing nothing, it just sits at the blank screen, I also tried putting it in Download and Recovery Mode.
Someone out there, HELP ME.:crying:

Try going back to stock. May have been a bad flash.

DubleJayJ said:
Try going back to stock. May have been a bad flash.
Click to expand...
Click to collapse
How can I? I tried putting the device into Recovery and Download mode, it does nothing.

nconfer13 said:
How can I? I tried putting the device into Recovery and Download mode, it does nothing.
Click to expand...
Click to collapse
Not sure how it works on the SG3 but for us Sony people, all we have to do is put it in flash boot and flash a file and we are back at stock.

DubleJayJ said:
Not sure how it works on the SG3 but for us Sony people, all we have to do is put it in flash boot and flash a file and we are back at stock.
Click to expand...
Click to collapse
That is only for Sony phones.

DubleJayJ said:
Not sure how it works on the SG3 but for us Sony people, all we have to do is put it in flash boot and flash a file and we are back at stock.
Click to expand...
Click to collapse
So, I took the battery out, plugged it into my computer and my computer made a sound that something was plugged in, but it does not show the device in my files program. the LED (red) light is now off and I can not get it to boot at all. Nothing comes up on the screen.

You probably flashed the wrong Version of a Rom you'll probably have to send it to these people on the internet they fixed mine for 60 bucks because I flashed a wrong kernel and mine did the exact same thing yours is doing
Sent from my SCH-I535 using xda app-developers app

jmxc23 said:
That is only for Sony phones.
Click to expand...
Click to collapse
You guys don't have stock images and stuff? That's weird

DubleJayJ said:
You guys don't have stock images and stuff? That's weird
Click to expand...
Click to collapse
Everything gets altered by the manufacturer so just because your Sony phone has whatever it was we were discussing doesn't mean that Samsung has kept the same functions.

U need a j tag
Sent from my SCH-I535 using xda premium

jmxc23 said:
Everything gets altered by the manufacturer so just because your Sony phone has whatever it was we were discussing doesn't mean that Samsung has kept the same functions.
Click to expand...
Click to collapse
It's just a normal stock image file. Why doesn't Samsung have a stock image for their altered version of Android? Most companies do it. Motorola does it, Sony, same with my Nexus 7. It has stock images. And I'm sure they do, why don't they just release it?
Secondly, check out this thread - http://forum.xda-developers.com/showthread.php?t=2092244
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That looks like it might work. But, I dunno.

DubleJayJ said:
It's just a normal stock image file. Why doesn't Samsung have a stock image for their altered version of Android? Most companies do it. Motorola does it, Sony, same with my Nexus 7. It has stock images.
Click to expand...
Click to collapse
We do have stock image files. They are flashed by connecting the phone to a PC and using a program called ODIN. The phone must be in download mode in order to flash files though ODIN, and the OP has said he cannot get his phone into download mode. So ODIN doesn't help him at this point..Hope that helps you understand how it is done on a Samsung phone.

landshark68 said:
We do have stock image files. They are flashed by connecting the phone to a PC and using a program called ODIN. The phone must be in download mode in order to flash files though ODIN, and the OP has said he cannot get his phone into download mode. So ODIN doesn't help him at this point..Hope that helps you understand how it is done on a Samsung phone.
Click to expand...
Click to collapse
Most likely getting one soon, so that helps.
OT - It's probably bricked. Bring it to your local Verizon store and beg for mercy.

DubleJayJ said:
Most likely getting one soon, so that helps.
OT - It's probably bricked. Bring it to your local Verizon store and beg for mercy.
Click to expand...
Click to collapse
Again since you're new to the Samsung dealings with bricked phones going through Verizon is pointless if he can go to mobile tech video's website and ship them his bricked phone and they will fix it for 50 bucks.

J tag will not work I have one and it wouldn't put it in download mode so I had to send it in to mobile tech videos
Sent from my SCH-I535 using xda app-developers app

rayraycarter4 said:
J tag will not work I have one and it wouldn't put it in download mode so I had to send it in to mobile tech videos
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Um mobiletechvideos do have jtag too and why do you think people keep recommending the websites jtag services as they actually know how to use jtag. As for the matter of jtag it seems like you didn't know what you were doing when using jtag so you send it to mobiletechvideos which basically did the same thing you did but with more experience with the debugger tool.

jmxc23 said:
Um mobiletechvideos do have jtag too and why do you think people keep recommending the websites jtag services as they actually know how to use jtag. As for the matter of jtag it seems like you didn't know what you were doing when using jtag so you send it to mobiletechvideos which basically did the same thing you did but with more experience with the debugger tool.
Click to expand...
Click to collapse
I'm trying a new method, So I'll update you guys on what works and what does not.

Alrighty fellow forumers,
My Galaxy S 3 that's a Verizon flavor is solidly bricked. I've tried almost every method out there (in the wild wild Internet) and nothing has even gotten the device to turn on or flash or anything.
Here's the thing thought: When I take the battery out and plug the S3 into my computer (or wall charger), the LED (red) light comes on as if it is charging (when plugged into the computer, it actually installs the USB drivers as it is recognizing it, but ODIN saw it once before [still bricked] but doesn't anymore).
If there is any other way I can perform a different method on trying to unbrick this thing. Feel free to send me a message on here.
Thanks for all you guys help! Wish me luck and lets pray for a work around.

nconfer13 said:
Alrighty fellow forumers,
My Galaxy S 3 that's a Verizon flavor is solidly bricked. I've tried almost every method out there (in the wild wild Internet) and nothing has even gotten the device to turn on or flash or anything.
Here's the thing thought: When I take the battery out and plug the S3 into my computer (or wall charger), the LED (red) light comes on as if it is charging (when plugged into the computer, it actually installs the USB drivers as it is recognizing it, but ODIN saw it once before [still bricked] but doesn't anymore).
If there is any other way I can perform a different method on trying to unbrick this thing. Feel free to send me a message on here.
Thanks for all you guys help! Wish me luck and lets pray for a work around.
Click to expand...
Click to collapse
You are describing classic signs of a hard brick. Jtag is your only help. Contact mobile tech videos.

nconfer13 said:
Alrighty fellow forumers,
My Galaxy S 3 that's a Verizon flavor is solidly bricked. I've tried almost every method out there (in the wild wild Internet) and nothing has even gotten the device to turn on or flash or anything.
Here's the thing thought: When I take the battery out and plug the S3 into my computer (or wall charger), the LED (red) light comes on as if it is charging (when plugged into the computer, it actually installs the USB drivers as it is recognizing it, but ODIN saw it once before [still bricked] but doesn't anymore).
If there is any other way I can perform a different method on trying to unbrick this thing. Feel free to send me a message on here.
Thanks for all you guys help! Wish me luck and lets pray for a work around.
Click to expand...
Click to collapse
There is no work around you have to use jtag services to fix hardware bricks. There is one for every smartphone.

Samsung pay

I just installed the app but it says I'm running custom software. I'm not rooted and I'm still on stock. I previously tried to Odin twrp but it didn't take because I didn't root 1st. So is it to late? Should I just go ahead and root?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N920P using Tapatalk

Sent from my SM-N920P using Tapatalk

If you go to settings>about device>status>device status, what does it say?

Custom
Sent from my SM-N920P

DarkManX4lf said:
If you go to settings>about device>status>device status, what does it say?
Click to expand...
Click to collapse
Custom
Sent from my SM-N920P

lilmeanz said:
Custom
Sent from my SM-N920P
Click to expand...
Click to collapse
Something took when you tried to Odin TWRP. That's why you can't use Samsung Pay. It won't work unless you are 100% stock. At this point just flash the kernel for root and then odin TWRP. However, if you want to use Samsung Pay, then you have to be 100% stock. I'm pretty sure you tripped Knox so I'm not sure Samsung Pay would work even if you odin'ed the stock tar and returned to stock out the box.

You can try to Odin stock tar and see if Samsung pay works after that.

Root 1st then Odin stock tar?
Sent from my SM-N920P

No you dont have to root first
Sent from my SM-N920P using XDA Premium HD app

lilmeanz said:
Root 1st then Odin stock tar?
Sent from my SM-N920P
Click to expand...
Click to collapse
No you don't have to root first. You can just boot into downloader and Odin the stock tar. It's not guaranteed that it will bring your phone back to non custom status and your Knox counter will still be tripped.

DarkManX4lf said:
No you don't have to root first. You can just boot into downloader and Odin the stock tar. It's not guaranteed that it will bring your phone back to non custom status and your Knox counter will still be tripped.
Click to expand...
Click to collapse
It's 100% guaranteed that it will bring the phone back to Official status. The Knox will still be tripped but everything else will go back to its stock out the box settings. You will have to go into recovery after you odin the stock tar, wipe both cache and factory reset. Once the phone boots back up it should be Official across the board. I've done it and can confirm it bings the phone back to Official status. I didn't try Samsung Pay because I returned the phone for other reasons but it was definitely back to Official when I checked in Download Mode.

travisw0204 said:
It's 100% guaranteed that it will bring the phone back to Official status. The Knox will still be tripped but everything else will go back to its stock out the box settings. You will have to go into recovery after you odin the stock tar, wipe both cache and factory reset. Once the phone boots back up it should be Official across the board. I've done it and can confirm it bings the phone back to Official status. I didn't try Samsung Pay because I returned the phone for other reasons but it was definitely back to Official when I checked in Download Mode.
Click to expand...
Click to collapse
I've had times where I Odin the stock tar and it still said custom. I had to Odin couple more times for it to say official. This happened to me on the note 3. Just thought I should add the comment.

DarkManX4lf said:
I've had times where I Odin the stock tar and it still said custom. I had to Odin couple more times for it to say official. This happened to me on the note 3. Just thought I should add the comment.
Click to expand...
Click to collapse
Oh no doubt. Wiping the cache and factory reset after the stock tar is odined usually helps out for that.
Sent from my SM-N920P using Tapatalk

I just spoke to Samsung Pay Tech Support. Once your phone tripped KNOX, you are done for good on that device regardless if you flashed OEM TAR firmware.

Caught in boot loop, not sure what to do

I'm sorry for the incredibly naïve question, I am new to this and am absolutely freaking out.
So I successfully unlocked the bootloader on my Pixel 3a, and then tried to follow this post and flashed the .img file corresponding to my build number, but my device got caught in a boot loop. I then downloaded the stock ROM from here, and tried to use flash-all.bat in order to reflash my phone, but I got error messages and my phone now says that it is corrupted when I turn it on. What should I do? Again, sorry for such a naïve question.

WARlord1903 said:
I'm sorry for the incredibly naïve question, I am new to this and am absolutely freaking out.
So I successfully unlocked the bootloader on my Pixel 3a, and then tried to follow this post and flashed the .img file corresponding to my build number, but my device got caught in a boot loop. I then downloaded the stock ROM from here, and tried to use flash-all.bat in order to reflash my phone, but I got error messages and my phone now says that it is corrupted when I turn it on. What should I do? Again, sorry for such a naïve question.
Click to expand...
Click to collapse
Stay calm. It will be alright.
Download factory image, download fastboot and adb, move factory image to same directory as fastboot and adb, unzip factory image, go to stock recovery, factory reset device from stock recovery, reboot to fastboot, fastboot flashall.bat.
Sent from my Pixel 3a using Tapatalk

Keep in mind that steps above will erase your phone.
You can try to remove the "-w" if you edit the flash-all.bat if you want to try that without wiping. It should work.

Oh thank goodness, I fixed it. Thank you so much, my mind tends to go to worst case scenario, and knowing that not all was lost was very reassuring. Now do you mind explaining to me what I did wrong, and what I need to do to gain root access?

WARlord1903 said:
Oh thank goodness, I fixed it. Thank you so much, my mind tends to go to worst case scenario, and knowing that not all was lost was very reassuring. Now do you mind explaining to me what I did wrong, and what I need to do to gain root access?
Click to expand...
Click to collapse
Probably nothing. Sometimes it's like voodoo mixed with black magic. Pixels are sometimes finicky beasts. What works on one sometimes doesn't on others. Just remember, as long as you can get to fastboot, you are golden. Very hard to brick once your unlocked.
Sent from my Pixel 3a using Tapatalk

Okay, so I'm trying to set it up now, but the touchscreen is totally jacked. I can't even get passed the first screen. Is this a problem with how I flashed it?
EDIT: I think I downloaded the ROM for the 3a XL, trying again now.
EDIT 2: Yeah, I definitely flashed the wrong one, lmao.

is this fastboot?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jmtjr278 said:
Probably nothing. Sometimes it's like voodoo mixed with black magic. Pixels are sometimes finicky beasts. What works on one sometimes doesn't on others. Just remember, as long as you can get to fastboot, you are golden. Very hard to brick once your unlocked.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
i cannot choose anything on this screen even with volume button