Database Info

[AT&T][2.3.6]Heimdall One-Click Back-To-Stock UCKJ4 + Easy CWM install

Introduction
This package will totally reset your Infuse 4G to UCKJ4 . This package is intended for use on AT&T, however it will work with any device if you reset APN.
This package includes:
Repartitioning: Repartition to stock KJ4
Reloading: IBL/PBL, PARAM, SBL, SBL2, Kernel, Recovery, FactoryFS and modem
formatting:Cache and DBdata
This package does not wipe:
EFS(Where your serial number and carrier information is stored)
Data(where your market apps are stored)
SDCard (where your pictures are stored)
You may use this code to reformat the Data and SDCard *2767*3855# There is no way to do this from Download Mode. The code will leave the EFS untouched.
Download:
Download Total Stock UCKJ4
{
"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"
}
Instructions:
Get the latest version of java here: http://java.com/en/download/installed.jsp
Put your phone into "Download Mode"
Run the program once, and if it does not work, then check the "Flash Bootloaders" checkbox and flash again
Your device will end up as it came from the factory. You will be asked to set your device up again.
If you would like to install CWM on your device to restore or flash a custom ROM, I have prepared LinuxBozo's Defuse 1.5 kernel in a One-Click package here:
Download Defuse 1.5
To flash this package, follow the directions above.
Please note, this may not boot your device, but it will allow you to use CWM recovery. Hold the 3 button combo without USB plugged in to activate CWM mode.
How I created these package:
I obtained the stock 2.3 bootloader from a link LinuxBozo gave me
The stock part.pit came from my device using Heimdall(Download Pit option)
Uploaded the UCKJ4 firmware to my device
Performed "wipe data" in recovery mode
Exploited the root prompt at the battery charge sequence using UART and grabbed the stock, wiped dbdata/cache partitions and params.lfs partition
Created a Heimdall tar.gz package using Heimdall 1.3
Finally, I used my Heimdall One-Click *BETA* packager to generate these one-clicks
This procedure can be reproduced for any custom ROM in the future by using the dd command to obtain the factoryfs and kernels from any device. Bootloaders may be obtained from within this package as it is an executable JAR file which can be unzipped.

Thanks
Cranky...

Nice, I'll be using this when needed.
Also, you have a typo in your title, it's 2.3.6. :]
Sent from my phone. :3

AdamOutler said:
This is the current version pushed out on new Captivate devices today.
Click to expand...
Click to collapse
Wait, Captivate devices got an official update today? Wow.

Any downsides we should be worried about?

I copied the first paragraph from another post I made. That was a typo.

You might want to put the defuse kernel in another thread. Don't want people flashing 2.2.1 kernels on 2.3.6
Also might want to make a Hellraiser kernel version for people that Odin'd the leak or Rogers users that want a quick root/cwm without Odin

Dani897 said:
You might want to put the defuse kernel in another thread. Don't want people flashing 2.2.1 kernels on 2.3.6
Also might want to make a Hellraiser kernel version for people that Odin'd the leak or Rogers users that want a quick root/cwm without Odin
Click to expand...
Click to collapse
This package is posted as a method to get your phone back to stock and the defuse kernel provides easy access to cwm.. I had it around and it works. I tested before posting. Its there because it will give CWM. I will probly post a new one later with a 2.3.6 kernel but for now, this is how you get CWM on your device from Linux or Mac with one click.

I needed to flash the bootloader in order to get mine to boot up, but its been running for ~1 hour now and looks pretty nice. Offhand, do you know if HDMI is working for you? I'll go ahead and test after posting and I'll include my results here.
Edit: Nevermind, found cross-post with the results I needed. Stock kernel, HDMI works, rooted kernel (Entropy, etc.) breaks HDMI as they're based on Rogers roms.

HOw TO ROOT THIS ROM

cookieboy said:
HOw TO ROOT THIS ROM
Click to expand...
Click to collapse
Use defuse kernel, boot into CWM, then flash a rooted CWM zip. This ROM is very new.

nice work!

Only thing i noticed is that their is no stock ringtones with this rom.
Sent from my SAMSUNG-SGH-I997 using XDA App

Also want to add when you open facebook newsfeed, it wont let you select news, status updates, photos and etc. If you refresh the page while in app it will show you the list. Small bug i came acrossed. Let ya know if i find more.
Sent from my SAMSUNG-SGH-I997 using XDA App

After running stock UCKJ4 for a few hours, I seem to be having an issue where I get an error message saying my Google Talk authentication is not working, to make sure Chat is enabled on my account, as well as returning errors any time I try to install things from the Market. Anyone else running into this? Going to try removing and re-adding my Google account.
Edit: Crap, apparently you can't remove it without factory resetting. Damnsauce.

After factory resetting, things appear to be fixed. Thanks again for this package!
Sent from my SAMSUNG-SGH-I997 using xda premium

adalgiso said:
After factory resetting, things appear to be fixed. Thanks again for this package!
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
I had a similar problem. Downloading apps from market told me I had Insufficient space on the device. Clearing cache and Factory reset fixed the issue, Incase any others run into this.

Axiomkid said:
I had a similar problem. Downloading apps from market told me I had Insufficient space on the device. Clearing cache and Factory reset fixed the issue, Incase any others run into this.
Click to expand...
Click to collapse
Just to clarify, I was not receiving the insufficient space issue, I don't remember the exact wordage. 'There was an error' and nothing else.
---------- Post added at 12:30 PM ---------- Previous post was at 11:35 AM ----------
Attempting to root using zergRush exploit from here: http://forum.xda-developers.com/showthread.php?t=1321582
Will post results.
Edit: Check my thread here: http://forum.xda-developers.com/showthread.php?t=1332656

i was trying this everything seemed to work then it wouldnt boot so i did the flash bootloaders like it said, now nothing will work, not even the screen please help, im in dire need

steezinstangl said:
i was trying this everything seemed to work then it wouldnt boot so i did the flash bootloaders like it said, now nothing will work, not even the screen please help, im in dire need
Click to expand...
Click to collapse
oh boy, there is always a risk of permabricking when flashing bootloaders, (unless you did the unbrickable mod or have a jtag)
ok to start to see if you are actually permabricked;
1 pull your battery out
2 get a good micro usb cable, try this with more than one if you have to, if you had a problem flashing it may have been caused by the cable.
3 insert the cable into the usb port and into the computer.
4 hold both volumes with the phone face down, while the volumes are held slide the battery into position. see if the phone enters the download warning screen, it will ask you if you are sure you want to flash custom firmware, hit volume up. it may also go into a phone + computer screen or strait into download mode. all are good signs.
if you end up in download mode congrats! reflash!
if the screen is still black id recommend sending the device to connexion for jtag flashing or to adam if he is willing to repair it, these methods will void the warranty do to hardware modification (the repair may require soldering) . you may also atempt a warranty repair with samsung or insurance replacement with att but if they find that you are responsible samsung will charge you for the repair and im not sure what the insurance company will do.

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

[GUIDE][ICS]How to root stock

{
"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"
}
presents....
A guide to root the new ICS UVLH5 firmware update.
This guide will try and make it very easy to root your stock firmware for those of you who are having
problems or don't want to wait for a stock rooted rom
anyways here goes the step by step assuming that you have a Samsung Galaxy S Blaze 4g T769 and are on ICS
UVLH5 firmware.
Before anything of course you'll need the files and here they are:
ClockWorkMod Recovery
Blaze Pit
Odin 1.8.5 Zip
SuperUser Zip
After downloading all the files first move the Superuser.zip to the root of your sdcard..not internal sdcard but the removable one. Then unzip the Odin zip and once unzipped:
Step 1:
Run Odin 1.85.exe, and prepare Odin:
Check "auto-reboot", and uncheck all other options.
Click PDA and select the TAR for clockworkdmod you downloaded. Click PIT and select the Blaze PIT your downloaded.
DOUBLE CHECK THAT YOU HAVE REPARTITION UNCHECKED
Step 2:
Connect the USB cable to your PC, but NOT your device.
Remove the battery.
Reinsert the battery.
Hold down Volume Up + Volume Down
Then while holding the voume keys plug in USB cable
You should now be in Download Mode
Step 3:
Make Sure repartition is still unchecked and click START in Odin.
Step 4:
When done the phone will reboot to the OS after this you have to reboot to recovery, here are a few ways.
1. adb command: adb reboot recovery
2. volume combo.
a. turn off phone.
b. hold volume + and volume -
c. while holding the volume buttons hold the power button for 10 seconds
d. after the 10 seconds release power button but keep holding volume buttons until you get into CWM recovery
Step 5:
Flash the SuperUser zip file
Step 6:
Reboot to System
Step 7:
Check whether root took or not.
Step 8:
If it did come back here and click thanks
Credits:
CWM (shabbypenguin)
Odin 1.8.5 (k0nane)
SuperUser (chainfire)
Hosting (gfx.myst)
TFQ ( cus we here to help )

Because I can lol

Do we need to update via kies first?
Sent from my SGH-T769 using xda app-developers app

Wait I did this a little earlier and I didn't flash the pit. Will this cause any problems down the road?
Sent from my SGH-T769 using xda app-developers app

shaikmonster said:
Do we need to update via kies first?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Yes or use the tar file a user uploaded around here a bit earlier.
KrimsonChin said:
Wait I did this a little earlier and I didn't flash the pit. Will this cause any problems down the road?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
If it flashed fine then I don't think it'll cause you any problems down the road.

Can I do this on Mac?
Sent from my SGH-T769 using xda app-developers app

Where in the process do we do the downloaded tar file?

im_awesome_right? said:
Can I do this on Mac?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
nope just for windows as Odin is only windows compatible
shaikmonster said:
Where in the process do we do the downloaded tar file?
Click to expand...
Click to collapse
the TAR file is the CWM recovery

im_awesome_right? said:
Can I do this on Mac?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I dont think there's a MAC version of Odin.... if you can somehow flash the CWM, you're golden. until then... ::shrugs::

Do I just drag the superuser zip to sd? gotta make sure..

erikmm said:
nope just for windows as Odin is only windows compatible
the TAR file is the CWM recovery
Click to expand...
Click to collapse
The ics tar file

Worked for me
Thanks erik! Looks like I've got root!

motez23 said:
Do I just drag the superuser zip to sd? gotta make sure..
Click to expand...
Click to collapse
you can. or download it. the important part is remembering whether its on your internal or external SD card when you go to flash it in CWM. as long as the MD5 is good, you're good as I figured out yesterday, my work computer messes with MD5's like a mutha******

I didn't expect to be able to do that so easily, but it all worked! Thanks much.

I had used the first stock root posted here, but didn't bother updating it to the minor patch that was released. I updated to ICS using Kies, knowing that I would lose root, and since my phone was rooted I was half expecting it to not work.
Well it did, and it almost worked too well. I was pleasantly surprised that I didn't even lose any apps or settings in the process. I lost root of course, although surprisingly superuser is still loaded on the phone. (I've confirmed the phone is not still rooted)
Anyways, my memory is a bit foggy, but doing this process is a total wipe on the phone right? I might even prefer that.

Cirkustanz said:
I had used the first stock root posted here, but didn't bother updating it to the minor patch that was released. I updated to ICS using Kies, knowing that I would lose root, and since my phone was rooted I was half expecting it to not work.
Well it did, and it almost worked too well. I was pleasantly surprised that I didn't even lose any apps or settings in the process. I lost root of course, although surprisingly superuser is still loaded on the phone. (I've confirmed the phone is not still rooted)
Anyways, my memory is a bit foggy, but doing this process is a total wipe on the phone right? I might even prefer that.
Click to expand...
Click to collapse
The first couple boots will be laggy. That's the nature with any rom
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

I'm rather confused by your quoting my reply, and not replying to it.

Cirkustanz said:
I'm rather confused by your quoting my reply, and not replying to it.
Click to expand...
Click to collapse
honestly, as am i, as my reply had nothing to do with your post perhaps a lack of sleep, perhaps a miss click, idk. but I guess we never will

I wish I read this thread sooner.
Here's my situation:
I had a rooted Gingerbread stock ROM that I upgraded to the official ICS update using Kies. I then used the same ODIN method to root the phone and now it won't boot up past the "Samsung Galaxy S" loading screen. Any ideas on where to go from here? I'm afraid if I do anything else haphazardly, I would only be digging myself deeper into this hole.
Thank you!

You flashed a GB kernel on ICS. If I were you, I would flash a GB .tar using Odin (unless you can find an ICS .tar somewhere?). Then, boot into recovery and wipe system and data, because you'll see a blue ICS menu flickering in the background upon booting up into the GB phone setup screen. At least, that is what happened to me. Then, upgrade to ICS using Kies.
Sent from my SGH-T769 using xda app-developers app

[Q] Binary counter at 5 can only access download mode

I've been searching for 2 days now and can't come up with an answer. This last time trying to go back to stock using Odin the phone goes through the process but it takes 2 minutes instead of the usual 10 minutes or so. When the phone reboots still stuck with the unauthorized software message. I thought as long as I could access download mode the phone was recoverable. Under binary counter in download mode it says yes counter 5 instead of the preferred no. From what I've read the only way to reset the counter is with the triangle away app which I obviously can't get the phone to that point. My question am I screwed? Is there any other way to get my phone back to stock using a different file or are there alternate methods to reset the counter? I thought the counter was only for store purposes and wouldn't affect flashing abilities. Please help I'm using an iPhone 5 because of this issue and I hate it.

Maduro78 said:
I've been searching for 2 days now and can't come up with an answer. This last time trying to go back to stock using Odin the phone goes through the process but it takes 2 minutes instead of the usual 10 minutes or so. When the phone reboots still stuck with the unauthorized software message. I thought as long as I could access download mode the phone was recoverable. Under binary counter in download mode it says yes counter 5 instead of the preferred no. From what I've read the only way to reset the counter is with the triangle away app which I obviously can't get the phone to that point. My question am I screwed? Is there any other way to get my phone back to stock using a different file or are there alternate methods to reset the counter? I thought the counter was only for store purposes and wouldn't affect flashing abilities. Please help I'm using an iPhone 5 because of this issue and I hate it.
Click to expand...
Click to collapse
Try downloading another Odin image. You can go with a no wipe image or whatever. But try a different image. If its only taking 2 minutes there might be something screwy with the file. After you do that it should relock your boot loader and flash a stock recovery.
You're not screwed. And question... Were you running a version of AOSP 4.3 or 4.4?
Tapatalk 4 sucks
{
"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"
}

I was running 4.3. So if the counter is maxed out the phone is still flash able? Thanks for your time

Just tried using another odin version. This tie it rebooted in 7 seconds and said pass but im still stuck with the system software not authorized message. Gonna try flashing the most current tar file see if that works

Maduro78 said:
Just tried using another odin version. This tie it rebooted in 7 seconds and said pass but im still stuck with the system software not authorized message. Gonna try flashing the most current tar file see if that works
Click to expand...
Click to collapse
Try using a different usb cable or different usb port (on your PC) too. I had something similar happen last time I had to ODIN, and it ended up being either a bad USB cable or bad USB port on my machine.

At this point I'll try anything.

Maduro78 said:
At this point I'll try anything.
Click to expand...
Click to collapse
The software unauthorized message just means you haven't unlocked the bootloader yet.
Sent from my SCH-I535 using Tapatalk

The things i used ez unlock before all this happened and it did say unlocked.

Maduro78 said:
The things i used ez unlock before all this happened and it did say unlocked.
Click to expand...
Click to collapse
Which version?
Sent from my SCH-I535 using Tapatalk

Can't confirm this since I can't check it but I believe it was 1.2. App said it was unlocked bit obviously it wasn't. I'm at my wits end it's just one issue after the other

Maduro78 said:
Can't confirm this since I can't check it but I believe it was 1.2. App said it was unlocked bit obviously it wasn't. I'm at my wits end it's just one issue after the other
Click to expand...
Click to collapse
You may have accidently hit the lock button because that app works no problem
Sent from my SCH-I535 using Tapatalk

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