Database Develop

Phone possibly bricked PLS help!

ok so i had my hero on the stock fresh rom from his kitchen and i decided to try out the new dc2.08.1 to see if there were still bugs that made me not want to use the older 2.1 roms. after flashing it no audio worked at all not even when talking on the phone. so i did a nandroid restore of a backup i made right before flashing DC. everything seemed to be back to normal but then i realized my audio is still not working but in calls it is working. i figured the restore messed up so i tried again and it didnt work for some reason. then i downloaded gumbo1.5c from my phone and flashed that and everything was perfect once again. the whole day my phone was flawless until last night at 2am i went to set an alarm clock and for some reason that triggered the audio to go off again. so i restarted my phone and figured it might fix itself but it didnt and i already deleted gumbo off my sd. i downloaded it again and then my phone seemed to start getting sluggish and finally completely froze after a while. i removed the battery and tried to turn it back on but it got stuck at the htc screen. then i tried to get into recovery but that doesnt work either now... fastboot does boot up and i tried to ruu from it but when the ruu is rebooting to bootloader my phone just stays off and doesnt reboot.. i did notice on fastboot it says "touch panel-fail".
before installing or restoring any roms i did wipe everything does anyone know what i have to do to restore my hero or am i just completely screwed D:

do a search for ruu error 110. try doing what it says and you should be able to get back to stock, and either take your phone in or flash again.

alright i will try that but i didnt have the 110 error any other possible solutions if this dont work? thx for the response

dylan6879 said:
alright i will try that but i didnt have the 110 error any other possible solutions if this dont work? thx for the response
Click to expand...
Click to collapse
What's he's saying is that if your phone has hardware issues, then you need to do the RUU to put it back to stock or sprint might not fix it under warranty.
I agree with the above, sounds like a hardware issue although the timing of the issue with a flash sounds strange.

yea i thought it might be a hardware issue but it just seems odd how it happened after flashing 2.1 and then reverting to 1.5. I want to bring it back to sprint but dont want to get screwed over because of it being rooted. i want to ruu but the phone just seems to be dead and doesnt want to do anything besides fastboot and show the htc screen

Some people have problems with the RUU, but the steps to fix the Error 110 after RUU'ing, should work anytime regardless if you RUUed or not. Your recovery could have gotten deleted. Try flashing it from fastboot. There are directions in this forum on how to do it from fastboot.

ok well i kept trying to do the ruu and i got it to run once and it completed succesfully... so i thought maybe i had fixed it but then it still wont boot and only shows the htc screen but fastboot still works so can someone link me to the thread that tells hows to reflash recovery from fastboot. ill look for it but just incase i cant find it.

dylan6879 said:
ok well i kept trying to do the ruu and i got it to run once and it completed succesfully... so i thought maybe i had fixed it but then it still wont boot and only shows the htc screen but fastboot still works so can someone link me to the thread that tells hows to reflash recovery from fastboot. ill look for it but just incase i cant find it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=674788
EVERYTHING, including the 110 fix is in that post.

i looked there i know the 110 error fix is in there but i cant find anything on flashing recovery through fastboot

dylan6879 said:
i looked there i know the 110 error fix is in there but i cant find anything on flashing recovery through fastboot
Click to expand...
Click to collapse
Did you try following his procedure? it should resolve your issue.
otherwise: fastboot flash recovery recoveryimagefilename
Pro tip: in a windows command prompt if you go to your androidsdk\tools directory and type 'fastboot' it will give you all the options.

alright so ive tried the 110 error fix and i cant get past the first step because my command prompt wont recognize the device.
thx for telling me how to get to fastboot commands and i tried installing a new rom from there but i cant type it correctly im not sure what i typed wrong. it say the syntax of the command is incorrect. im trying to do the command "update <filename>" so i typed in "fastboot update <update.zip>".

dylan6879 said:
alright so ive tried the 110 error fix and i cant get past the first step because my command prompt wont recognize the device.
thx for telling me how to get to fastboot commands and i tried installing a new rom from there but i cant type it correctly im not sure what i typed wrong. it say the syntax of the command is incorrect. im trying to do the command "update <filename>" so i typed in "fastboot update <update.zip>".
Click to expand...
Click to collapse
You don't need the < > in there.
fastboot update update.zip should work.

thx i tried it that way and it it went through but then said
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"

dylan6879 said:
thx i tried it that way and it it went through but then said
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
Click to expand...
Click to collapse
What exactly are you trying to flash? What's the filename, and what's it for?
If this is a ROM you don't want update.
If it's a recovery image:
fastboot flash recovery recoveryimagename.zip

oh yeah i was trying to flash a rom. i thought u could do that from there. where should i have the recovery img before i flash it. and is it possible to flash a rom through here?

ok so i put the recovery in the same place i had the roms and it went through but now it failed saying "sending 'recovery' <2326 KB>... FAILED <remote: not allow>".

dylan6879 said:
ok so i put the recovery in the same place i had the roms and it went through but now it failed saying "sending 'recovery' <2326 KB>... FAILED <remote: not allow>".
Click to expand...
Click to collapse
It's probably possible to flash a rom through fastboot, but I've never done it.
What recovery image are you using? And what is the exact name of the recovery image file? Where exactly did you put the recovery image file?

i tried the clockwork 1.7.6 and 1.5.2 and i tried them zipped up and as img files. i put them in the tools folder in android-sdk-windows. btw thx for all ur help
the name of the recovery image files are clockwork.zip, clockwork.img, 152.zip, and 152.img those are the four files i tried

dylan6879 said:
i tried the clockwork 1.7.6 and 1.5.2 and i tried them zipped up and as img files. i put them in the tools folder in android-sdk-windows. btw thx for all ur help
the name of the recovery image files are clockwork.zip, clockwork.img, 152.zip, and 152.img those are the four files i tried
Click to expand...
Click to collapse
Never used it, and 1.5.2 is old. I suggest downloading AmonRA's 1.6.2
You can't use zip files with fastboot...it wants the actual image (at least in this case, because those zip files aren't updates, they're just zip files).
So you should put the 152.img in the same directory as fastboot (Android-sdk-windows\tools)
Then you should do: fastboot flash recovery 1.5.2.img
What happens when you do that?

i tried flashing the 1.6.2.img and got the same result it says "sending 'recovery' <3720 KB>... FAILED <remote: not allow>".

[Q] Can not sideload, push, or restore.

Ok, I know I'm going to catch all kinds of hell probably for posting this. But, I'm stuck. This is the first question I have asked on this forum, and have literally spent days on end searching, and trying new things. What happened is I think I tried flashing a GSM rom (the new android revolution 30.0) onto my Sprint HTC One. I just got this phone two weeks ago, and unfortunately upgraded to the 4.3 with the 1.55 hboot. So, S-on. I was using slimbean as my dd, but wanted to give revolution a try. When I dl the rom, it stated for m7wls, so thought I was good. Well, went into a kind of bootloop where it would upgrade android like 41 out of 120, then it would restart. When it finally would boot up, I had about fifteen seconds before it would reboot again. I tried to wipe and restore, but same thing was happening. I read that the partitions may have been screwed up from the gsm to cdma so, I wiped data and everything. I was going to relock and flash an RUU. Then I find out that there isn't one yet for the 4.3. I tried the Guru reset, updating drivers, sideloading, flashing cwm from twrp, pushing and had a rom boot up once, but no service or gapps. In cmd fastboot, my phone is recognized. But, when I use adb, it can't find it.I can get into recovery, and I have the official android 4.3 stock rom on my laptop ready to flash, but just can't get it to the phone. I am a noob, so I am sorry for that, but we all were at one time or another. I researched, tried to learn as much as I could before I took the plunge. I've read thread upon thread here and in other forums trying to find a fix. Everything that I've tried from some of these posts just didn't work for me. I don't know what I'm doing wrong, and I am not sure what you guys would need from me as far as more info. But, I would be grateful if someone could steer me in the right direction. Thanks in advance, and again apologies if I'm not doing things right for you guys. Just trying to learn and do.
C:\Users\Guest\Desktop\Fastboot>fastboot devices
FA38DS904955 fastboot
C:\Users\Guest\Desktop\Fastboot>fastboot flash rom.zip Dev-3.22.1540.1-Stock-Roo
ted-DE-ODEX.zip
target reported max download size of 1526722560 bytes
sending 'rom.zip' (1061169 KB)...
OKAY [ 47.135s]
writing 'rom.zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 169.469s
This is what cmd tells me when I try to flash the rom.

Dev-3.22.1540.1-Stock-Rooted-DE-ODEX.zip
Click to expand...
Click to collapse
Is not a Sprint rom

bigdaddy619 said:
Is not a Sprint rom
Click to expand...
Click to collapse
Even when I tried to flash slimbean, same thing happens. Thank you for the reply though.
I downloaded super one rom to laptop, tried using adb sideloader, but it doesn't detect my device. I went into mounts and storage on cwm and tried mounting usb, but doesn't toggle. I really am in desperate need of directions. I would even pay if I could lol.

bbjay351 said:
Even when I tried to flash slimbean, same thing happens. Thank you for the reply though.
I downloaded super one rom to laptop, tried using adb sideloader, but it doesn't detect my device. I went into mounts and storage on cwm and tried mounting usb, but doesn't toggle. I really am in desperate need of directions. I would even pay if I could lol.
Click to expand...
Click to collapse
Installed universal usb drivers, got sideload working. But now after installing the rom it is in bootloop.
Installed slimbean, I can get into the rom, but only for a minute or two. I have no service at all. When I go into about phone phone status it shows unknown network, out of service, unknow phone number etc. How do I get that back up and running? And, how do I get it to stop rebooting after a few minutes? Thank you guys

Your partitions are borked from flashing a non Sprint Rom. To fix them
if you are s-on, flash the 4.3 full firmware http://www.androidfilehost.com/?fid=23159073880933344
if you are s-off, flash the modified firmware http://www.androidfilehost.com/?fid=23159073880933456
Then side load your Rom and you should be golden.
Sent from my HTCONE using xda app-developers app

Konfuzion said:
Your partitions are borked from flashing a non Sprint Rom. To fix them
if you are s-on, flash the 4.3 full firmware http://www.androidfilehost.com/?fid=23159073880933344
if you are s-off, flash the modified firmware http://www.androidfilehost.com/?fid=23159073880933456
Then side load your Rom and you should be golden.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Tried sideloading this and fails saying zip file is corrupt.

bbjay351 said:
Tried sideloading this and fails saying zip file is corrupt.
Click to expand...
Click to collapse
I hate to say it but use the Format Data option within TWRP to format your sdcard the try to sideload
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
bbjay351 said:
Tried sideloading this and fails saying zip file is corrupt.
Click to expand...
Click to collapse
Check PM

Get a signed download of the firmware and flash thru fastboot if nothing else.
Sent from my HTCONE using XDA Premium 4 mobile app

Big thanks
Just wanted to say thanks again to Bigdaddy619! Spent the time with me to walk me through. Learned a lot from him. And a thanks to all that replied. Love learning new stuff, even if it makes me pull my hair out lol

bbjay351 said:
Just wanted to say thanks again to Bigdaddy619! Spent the time with me to walk me through. Learned a lot from him. And a thanks to all that replied. Love learning new stuff, even if it makes me pull my hair out lol
Click to expand...
Click to collapse
Updated steps for below
So this is what we did:
1.We downloaded the s-on firmware zip from the link provided by @Konfuzion
2.Renamed it firmware.zip (put the firmware.zip into the folder you use to open your cmd window)
3.Booted to bootloader
4.Then used these commands
Code:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot
He got an error so I had him re-lock his bootloader
5.Ran the commands again
Got another error
Code:
failed 90 hboot pre-update! please flush image again
press the UP Arrow on your keyboard and press enter to issue the command again.
6.He was able to unlock the bootloader again and re-flash TWRP and sideload or adb push a rom to his phone.
7. S-OFF using Rumrunner
8.Win lol

bigdaddy619 said:
So this is what we did:
1.We downloaded the s-on firmware zip from the link provided by @Konfuzion
2.Renamed it firmware.zip (put the firmware.zip into the folder you use to open your cmd window)
3.Booted to bootloader
4.Then used these commands
Code:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot
He got an error so I had him re-lock his bootloader (not sure if it was needed but...)
5.Ran the commands again
Got another error
Code:
failed 90 hboot pre-update! please flush image again
press the UP Arrow on your keyboard and press enter to issue the command again.
6.He was able to unlock the bootloader again and re-flash TWRP and sideload or adb push a rom to his phone.
7. S-OFF using Rumrunner
8.Win lol
Click to expand...
Click to collapse
Ok so I am in a similar position with one of my Sprint devices (I have 2 my kids and mine...) Anyway the device is s-off and had gone into TWRP and formated everything in anticipation of loading a new ROM that 4.3 based so wiped everything and then was going to push the rom with ADB... Problem I am having is that ADB doesn't see the device.
Now it shouldn't be a driver issue as I connected my other device to it with no problem and adb sees it fine.
@bigdaddy619.
I followed steps 1-4 except I used the zip for s-off and received no errors so I went back to twrp and attempted to sideload and still won't work.
Thanks for the assistance.
MG
EDIT: Well looks like it was a driver issue, odd since I wasn't having trouble connecting with my other Sprint HTC One but I changed to the Universal Windows ADB Driver listed here in this post. I also updated to the latest Android-SDK and was able to sideload... Thanks all for the info in this thread!
MG

[Q] Problems in flash ClockworkMod at 11.4.1.30-20150121

Today, I got my new TF701 and as at my TF300T before, I unlocked the bootloader for flash the device.
First I ran through the updates, so that the system is running build 11.4.1.30-20150121.
Unlocking the bootloader was fine but the the flash of ClockworkMod, I ran into trouble.
In first run, everything looks fine but at entering recovery, I saw the dead android.
Then I tried again but all the time, I am getting the same messages
HTML:
fastboot -i 0xb05 flash recovery recovery.img
< waiting for device >
sending 'recovery' (6644 KB)...
FAILED (command write failed (Invalid argument))
Then I tried to erase the recovery for flashing again but the error message was still the same. The connection to the device is fine because
HTML:
fastboot devices
brings the right device information.
The ClockworkMod I tried from the following threads http://forum.xda-developers.com/transformer-tf701/development/rom-t2839030 and http://wiki.cyanogenmod.org/w/Install_CM_for_tf701t
Does anybody has an idea, how to fix and go ahead?

gremly said:
Today, I got my new TF701 and as at my TF300T before, I unlocked the bootloader for flash the device.
First I ran through the updates, so that the system is running build 11.4.1.30-20150121.
Unlocking the bootloader was fine but the the flash of ClockworkMod, I ran into trouble.
In first run, everything looks fine but at entering recovery, I saw the dead android.
Then I tried again but all the time, I am getting the same messages
HTML:
fastboot -i 0xb05 flash recovery recovery.img< waiting for device >sending 'recovery' (6644 KB)...FAILED (command write failed (Invalid argument))
Then I tried to erase the recovery for flashing again but the error message was still the same. The connection to the device is fine because
HTML:
fastboot devices
brings the right device information.
The ClockworkMod I tried from the following threads http://forum.xda-developers.com/transformer-tf701/development/rom-t2839030 and http://wiki.cyanogenmod.org/w/Install_CM_for_tf701t
Does anybody has an idea, how to fix and go ahead?
Click to expand...
Click to collapse
have you tried this one http://droidbasement.com/db-blog/?p=3568 its cwm 6.0.5.1 and its working fine here.
you can also find cm12 unofficials there. its pershoots site
btw im also on 11.4.1.30

tschmid said:
have you tried this one http://droidbasement.com/db-blog/?p=3568 its cwm 6.0.5.1 and its working fine here.
you can also find cm12 unofficials there. its pershoots site
btw im also on 11.4.1.30
Click to expand...
Click to collapse
Oh no, I did not why because I tried before, I had 4 recoveries in use but now, but now it runs fine. Thanks in advance.
PS: I had taken over my PAC-MAN ROM and when it looks fine, I will release.

Seemingly endless string of issues while trying to root

Hey guys, I've decided I'm going to root my Moto X Unlocked Edition. I've been following this guide: http://www.theandroidsoul.com/2014-moto-x-2nd-gen-marshmallow-root-86348/ (as well as many others) and I'm running into issue after issue.
I've managed to unlock my bootloader. I'm on step 8: "fastboot flash boot boot.img" and have tried with so many techniques but keep getting this "mismatched partition size (boot)" error after each attempt. I've tried using .img files from CMod, from the guide that I'm following, etc. I've googled the error with no useful result coming up. I'm at a loss here and really hoping someone is able to help me out. Searching is turning up nothing and I'm about to start tugging at my hair. If anyone has a one click installer that would work, please pass it along!
Thank you all very much!
Edit 4/29/16 13:01 ET: I've switched from trying to use the 'fastboot flash boot' command and started trying to use 'fastboot update <romname.zip >' with various different ROMs. I'm getting this error.
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Click to expand...
Click to collapse
I'm not sure what to do now. I feel like I'm getting reckless in trying an overwhelming amount of solutions to no avail. I'm going to wait, now. I'm starting to think that these phones can't be rooted or flashed with a new ROM.

What phone version do you have, XT1095? I just tried to root my device without reading carefully and ended up softbricked...had to use fastboot to wipe everything and flash stock to recover. Seems this devices is tricky to root on Marshmallow, much harder than ones I've had in the past.
Have you tried the method here? http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Or, if you install TWRP you could just flash a pre-rooted ROM instead of rooting stock.

Thank you for the help @viper74656!
I'm struggling to even get the TWRP installed. When I try to install TWRP-3.0.0-0-victara.img, I get
cmd: getvar: partition-type:recovery
cmd: getvar:max-download-size
cmd: download:0096c000
cmd: flash:recovery
Mismatched partition size (recovery)
Click to expand...
Click to collapse
I was having this problem earlier too when I was trying to work around that. I'm going to try an alternate way of installing TWRP.
Really, all I want to do is get CMod. When I rooted my HTC Inspire 4G, it was a cakewalk... I didn't expect all this LOL

viper74656 said:
What phone version do you have, XT1095? I just tried to root my device without reading carefully and ended up softbricked...had to use fastboot to wipe everything and flash stock to recover. Seems this devices is tricky to root on Marshmallow, much harder than ones I've had in the past.
Have you tried the method here? http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Or, if you install TWRP you could just flash a pre-rooted ROM instead of rooting stock.
Click to expand...
Click to collapse
Yeah, btw, I have an xXT1095

So I managed to get TWRP installed on my XT1095 using the "WinDroid" toolkit I found somewhere on XDA. It seems to push the right fastboot commands, but I had to manually download and select an older TWRP version. Read something about our recovery partition not working with the newer versions. I still got the mismatch error, but when I rebooted into recovery TWRP was there.
I haven't ventured back to try it again after having to wipe and start over...bleh.

Twrp manager (from the playstore) is what I had to use to install recovery. Windroid wouldn't push it for some reason.
Sent from my XT1096 using XDA-Developers mobile app

Fastboot Strangeness, Having Issues Rooting/Installing ROMS

Hello!
I've been enjoying my rooted Pixel 5 but today I saw that the first Pixel 5 ROM is available so I went to go try it. Just like the instructions asked I tried to flash the ROM like it was a standard stock image since we don't have TWRP yet. Everything was going fine until it got to the part where it sent boot.img, it would fail at that point saying the partition doesn't exist. The exact error was...
HTML:
FAILED (remote: Failed to write to partition Not Found)
I also did the 'fastboot -w' to wipe user data before rebooting as instructed, it just booted back into fastboot with the reason listed as "no valid slot to boot". After a while I figured out I could use 'fastboot flash boot_a /path/to/boot.img' to flash the slots manually and that booted me into stock Android, not the ROM. Even though I used the boot.img from the ROM, no ROM was installed.
After this I decided to go back to stock and flash Magisk again and wait until we have some more stable ROMs. annnnnnd that's where I realized I was in trouble. I tried doing 'flash-all.bat' like normal and it gave me the same error the ROM did. I then manually flashed the stock boot.img and set up the phone, once I was at the home screen I turned it off, flashed my prepared 'magisk_patched.img', all seemed to go just fine, but upon trying to reboot its stuck at fastboot again. I can get back to my homescreen by just flashing the stock boot.img but no matter what I try I cannot get it to reboot after flashing the patched image.
Things I have tried:
Updating ADB/Fastboot
Reinstalling ADB/Fastboot
Updating USB Drivers
Flash to Stock and Retry
Repatch a new image using Magisk Canary
Lots and Lots of reboots
Several attempts at all of the above (last time I rooted it gave me errors and then just worked for no reason after some reboots and tries)
Above steps in Linux Terminal (Ubuntu WSL)
For the night I'm just going to flash the Stock boot.img so I can have my alarms and receive messages, but I'd really like to return to stock as I use Tasker frequently as well as some other applications that require root access. If anyone has any tips for how to get more consistent results when rooting, I have no idea why it works sometimes and not other times. If anyone knows how to solve these errors please let me know.
Thanks y'all
***EDIT - FIXED, NOT SOLVED***: I'm still unsure what caused it in the first place, but I was able to regain root by flashing the October update, patching a new boot.img from that update, and then flashing. I was previously using the latest November update. I think that when I tried to flash the ROM something went wrong and it left things behind, and I don't think my original flash back to stock worked completely because flashing the October update took about 4 times as long. I used Pixel 5 unlocked stock images from Google's website for both attempts so im not sure why one worked and the other didn't, but I am rooted. If anyone else is experiencing similar issues, try flashing to a previous software update and rooting that.

this may be a stupid question but did you enable "Developer Options" and "OEM Unlocking"?
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-5-easy-follow-guide-0329550/

grisly grizzly said:
Hello!
I've been enjoying my rooted Pixel 5 but today I saw that the first Pixel 5 ROM is available so I went to go try it. Just like the instructions asked I tried to flash the ROM like it was a standard stock image since we don't have TWRP yet. Everything was going fine until it got to the part where it sent boot.img, it would fail at that point saying the partition doesn't exist. The exact error was...
HTML:
FAILED (remote: Failed to write to partition Not Found)
I also did the 'fastboot -w' to wipe user data before rebooting as instructed, it just booted back into fastboot with the reason listed as "no valid slot to boot". After a while I figured out I could use 'fastboot flash boot_a /path/to/boot.img' to flash the slots manually and that booted me into stock Android, not the ROM. Even though I used the boot.img from the ROM, no ROM was installed.
After this I decided to go back to stock and flash Magisk again and wait until we have some more stable ROMs. annnnnnd that's where I realized I was in trouble. I tried doing 'flash-all.bat' like normal and it gave me the same error the ROM did. I then manually flashed the stock boot.img and set up the phone, once I was at the home screen I turned it off, flashed my prepared 'magisk_patched.img', all seemed to go just fine, but upon trying to reboot its stuck at fastboot again. I can get back to my homescreen by just flashing the stock boot.img but no matter what I try I cannot get it to reboot after flashing the patched image.
Things I have tried:
Updating ADB/Fastboot
Reinstalling ADB/Fastboot
Updating USB Drivers
Flash to Stock and Retry
Repatch a new image using Magisk Canary
Lots and Lots of reboots
Several attempts at all of the above (last time I rooted it gave me errors and then just worked for no reason after some reboots and tries)
Above steps in Linux Terminal (Ubuntu WSL)
For the night I'm just going to flash the Stock boot.img so I can have my alarms and receive messages, but I'd really like to return to stock as I use Tasker frequently as well as some other applications that require root access. If anyone has any tips for how to get more consistent results when rooting, I have no idea why it works sometimes and not other times. If anyone knows how to solve these errors please let me know.
Thanks y'all
Click to expand...
Click to collapse
And you have usb debugging on

swangjang said:
this may be a stupid question but did you enable "Developer Options" and "OEM Unlocking"?
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-5-easy-follow-guide-0329550/
Click to expand...
Click to collapse
Hey, Yes OEM Unlocking is on and greyed out. It was giving me the option to turn it off again before, not sure why it isn't now.

jaythenut said:
And you have usb debugging on
Click to expand...
Click to collapse
I actually did not have USB debugging enabled, but after doing so I have the same problem. Just tried to flash magisk with the two custom .img files I made last night, and my last confirmed working one, same problem as before. It successfully flashes, then bootloops til I reflash the stock boot.img.

grisly grizzly said:
I actually did not have USB debugging enabled, but after doing so I have the same problem. Just tried to flash magisk with the two custom .img files I made last night, and my last confirmed working one, same problem as before. It successfully flashes, then bootloops til I reflash the stock boot.img.
Click to expand...
Click to collapse
Don't know if it will work but flash magisk on slot a and b
And just checking you done
fastboot flash boot magisk_patched.img

jaythenut said:
Don't know if it will work but flash magisk on slot a and b
And just checking you done
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
I think I tried that last night, but I tried again just now with a new patched.img just in case. Flashed successfully but same problem. Here's my exact powershell input/output. For powershell I gotta use ./fastboot but its the same as running 'fastboot' in cmd. And I've using powershell with and without admin access.
HTML:
PS C:\platform-tools> ./fastboot flash boot_a ".\patched.img"
Sending 'boot_a' (98304 KB) OKAY [ 0.469s]
Writing 'boot_a' OKAY [ 1.993s]
Finished. Total time: 2.725s
PS C:\platform-tools> ./fastboot flash boot_b ".\patched.img"
Sending 'boot_b' (98304 KB) OKAY [ 0.469s]
Writing 'boot_b' OKAY [ 1.981s]
Finished. Total time: 2.713s
Just gets me back to the fast boot menu saying boot partition not found, just flashed the stock boot.img and I'm back at my home screen again. If its of any importance, I only had to flash the stock boot.img to slot a in order to get back to my home screen. Slot B should still be flashed with the patched.img, no root access on slot a though.
Edit: Do you think it would be helpful to relock the bootloader (since it returns everything to stock) and then re-unlock and re-root? Nevermind I forgot that re-locking makes it so you can't re-unlock. Won't do that.

how exactly did you flash the stock rom bc im lost on this process.... Heres where im at bc i cant get any help from the ProtonAOSP thread or anywhere. ive never flashed a rom without twrp and im lost now:
BC This is what ive been getting:
C:\Users\james\AppData\Local\Android\Sdk\platform-tools>fastboot flash C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1.zip
unknown partition 'C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1.zip'
fastboot: error: cannot determine image filename for 'C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1.zip'
and now this fof Fastboot boot ZipFile
C:\Users\james\AppData\Local\Android\Sdk\platform-tools>fastboot boot C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1-gapps.zip
creating boot image...
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
but what im not understanding is do u unzip it to platform-tools and use flash-all, like reverting back to stock? bc this is what i get when i dont unzip it and just copy it to platform-tools directory from my downloads folder. this is my first time flashing a custom rom and i just cant seem to get anyone to tell me exactly what i need to do or what im doing wrong. PLEASE HELP