Database Develop

[Q] How to fix Sensation XL from GUIDE

Hello,
I've been following this guide: http://forum.xda-developers.com/showthread.php?t=1466436
When I came to the part where I had to fastboot the Chinese ROM my phone stopped working. I followed it straight out, and when I chose "Recovery" as the guide told me to choose, my phone only boots with a black lit screen and then turns black completely (no backlight), but the touch buttons still work and the phone vibrates.
The part it failed at was this:
1. You cant just flash a custom rom on this phone, firstly you will need the 'Chinese rom' which is here http://hotfile.com/dl/148413075/8990...01713.zip.html and make sure it is on the SDcard part of your phones memory. Make sure it on the root of the SDcard because it will be easier to find later. Then you will need this rom RCMix3d Runny XL rom from here http://dl.dropbox.com/u/56143145/RCM...ny_XL_v1.2.zip (thanks to benjamin.j.goodwin) and make sure that is on the SDcard too with the other rom
2. Then you will need to download this file from here http://forum.xda-developers.com/show...7&postcount=18 it is the 'Chinese boot.img' and will need flashing from fastboot again. So put the phone in fastboot and extract the 'boot.img' from the 'boot.rar' file and put it in the fastboot folder on the PC. Open the command prompt again and type this... fastboot flash boot boot.img ... This should only need doing once if you're coming from a stock rom.
3. Once you've done that you will need to get into recovery. From fastboot select bootloader and then look for recovery, it should be under fastboot if its worked correctly. Select that and the phone should then reboot and go into 'CWM' (recovery). Once there you will need to use the volume keys and power button just like when you were in bootloader. Go down and select 'Factory Reset/Data Wipe' and select that, the select yes on following screen. This will take a few mins (don't worry if it looks like its not doing anything). After that go down to 'Wipe Cache' and select that. and then go down to 'Advanced' select that and on the following screen select 'Wipe Dalvik Cache'.
Click to expand...
Click to collapse
The bolded text is what I have done, whatever comes after I never got a chance to do. Nothing I have tried so far have worked.
I'm very new to doing this kind of stuff and I thought I'd try the three musketeers ROM out, so far I haven't gotten this far. I need help in getting my phone to work again so I can continue the guide.
I'm sorry if this is in the wrong section of the forums. Like I said, I'm new, and please move this to the correct area (If any mods around). Sorry for any troubles, and appreciate any help.
Thanks! <3

I've tried to get back to stock version, but it's not working.
My phone only boots to FASTBOOT and BOOTLOADER right now. It says on the top:
***RELOCKED***
RUNNYMEDE PVT SHIP S-ON
RADIO-3831.16.00.16_M
eMMC-BOOT
When trying to do anything within the CMD it says:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3424 KB)...
OKAY [ 2.594s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.031s
:/

Phrebbie said:
I've tried to get back to stock version, but it's not working.
My phone only boots to FASTBOOT and BOOTLOADER right now. It says on the top:
***RELOCKED***
RUNNYMEDE PVT SHIP S-ON
RADIO-3831.16.00.16_M
eMMC-BOOT
When trying to do anything within the CMD it says:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3424 KB)...
OKAY [ 2.594s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.031s
:/
Click to expand...
Click to collapse
Unlock bootloader and flash recovery. Måske device s-off then run the ruu.exe . do not relock bootloader.
Sent from my Sensation XL using XDA Premium HD app

anders3408 said:
Unlock bootloader and flash recovery. Måske device s-off then run the ruu.exe . do not relock bootloader.
Sent from my Sensation XL using XDA Premium HD app
Click to expand...
Click to collapse
I'm really sorry, but how should I do this? :/
It keeps telling me it failed and remote: signature failed.

I think I did it now.
I unlocked bootlader again.
I flashed the recovery "Clockwork" OK.
Now I have no idea what to do next? I tried putting in the Chinese ROM again and then hit "Recover", but I only come to black screen and nothing happens.
RUU.EXE doesn't work either, tried it, it says security/update fail or something and it just stops.

Phrebbie said:
I think I did it now.
I unlocked bootlader again.
I flashed the recovery "Clockwork" OK.
Now I have no idea what to do next? I tried putting in the Chinese ROM again and then hit "Recover", but I only come to black screen and nothing happens.
RUU.EXE doesn't work either, tried it, it says security/update fail or something and it just stops.
Click to expand...
Click to collapse
From boot loader go to recovery.
From recovery mount SD card for PC/USB
Copy the ROM over to sdcard.
Unmount for USB/PC
Wipe data/factory reset
Wipe cache and dalvik cache
Flash the ROM
Boot up the new ROM
S-off the device
Then install the ruu.exe.
Sent from my Sensation XL using XDA Premium HD app

Thank you for reply Anders,
The problem is I can't go into "recovery" on my phone. It just goes black and nothing happens.
I did both version of Clockwork recovery flash and it succeeded - no idea if it's related, but I just can't go into recovery.

Phrebbie said:
Thank you for reply Anders,
The problem is I can't go into "recovery" on my phone. It just goes black and nothing happens.
I did both version of Clockwork recovery flash and it succeeded - no idea if it's related, but I just can't go into recovery.
Click to expand...
Click to collapse
Try from fastboot and flash twrp.
Fastboot flash recovery recovery.img
Sent from my Sensation XL using XDA Premium HD app

Thank you,
TWRP worked much better.
I put rom on USB storage (i had to format it first to be able to open it, so it was completely empty and i just put file in there)
I did wipe/reset and cache/dalvik wipe.
I flashed the ROM succesfully.
I tried booting it up, the HTC logo comes up as well as the BEATS animation, then HTC logo with "Quietly Brilliant" beneath, and it stops there, nothing happens. Also, it starts making the startup HTC signal for less than a second, then it's quiet.
The ROM I put in storage and flashed with was "Total_Senseless_SXL-v4.1.1".
No idea if I did it right but I will try the Chinese ROM as well. As said, I'm new to this.

I get a problem when trying to flash the runnymede_ax918 .zip file.
It tells me this:
Installing '/sdcard/runnymede_ax918_11511_10171
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
E:Error in /sdcard/runnymede_ax918_11511_101713
(Status 1)
Error flashing zip '/sdcard/runnymede_ax918_1115
Updating partition details...
And a red text "Failed".
According to the guide I have to install the Chinese ROM first which is what I'm trying to do here.
I flashed the boot.img first, entered TWRP, factory reset/wipe cache/dalvik
Find the Chinese .zip file (runnymede_ax918) and press install and this problem occurs.

That guide is old, you do not need any other chinese ROM's and suc, just unlock bootloader, flash recovery, root, S-OFF and after that you can have whatever you want on your phone. The thing with cbinese ROM and.such was before S-OFF was available.for the device...
Sent from my Nexus S using xda app-developers app

Well that's fun. Thanks for pointing that out though.
I can't stress it enough, I'm new to this, what should I do next? How do I root and how do I S-OFF? Guides?
Sorry for troubles.

Phrebbie said:
I get a problem when trying to flash the runnymede_ax918 .zip file.
It tells me this:
Installing '/sdcard/runnymede_ax918_11511_10171
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
E:Error in /sdcard/runnymede_ax918_11511_101713
(Status 1)
Error flashing zip '/sdcard/runnymede_ax918_1115
Updating partition details...
And a red text "Failed".
According to the guide I have to install the Chinese ROM first which is what I'm trying to do here.
I flashed the boot.img first, entered TWRP, factory reset/wipe cache/dalvik
Find the Chinese .zip file (runnymede_ax918) and press install and this problem occurs.
Click to expand...
Click to collapse
Delete ROM from zip and put it over again. And ofc try and open the zip on the computer first. If you can't open it on computer download the ROM again.
BTW. That is just how I did it, since no one really knows what its so special in that ROM and no one knows for sure that it makes Amy difference at all when using it or not, you can do as lexmazter wrote and don't use it.
The reason for me to flash that ROM is that I had read in here that when that ROM has been flashed hard brick was almost impossible with some common sense
No matter what, if you delete or has wrong vold.fstab and formats the sdcard from PC you only luck will be jtag.
Sent from my Sensation XL using XDA Premium HD app

anders3408 said:
Delete ROM from zip and put it over again. And ofc try and open the zip on the computer first. If you can't open it on computer download the ROM again.
BTW. That is just how I did it, since no one really knows what its so special in that ROM and no one knows for sure that it makes Amy difference at all when using it or not, you can do as lexmazter wrote and don't use it.
The reason for me to flash that ROM is that I had read in here that when that ROM has been flashed hard brick was almost impossible with some common sense
No matter what, if you delete or has wrong vold.fstab and formats the sdcard from PC you only luck will be jtag.
Sent from my Sensation XL using XDA Premium HD app
Click to expand...
Click to collapse
From what i know, that Chinese ROM was supposed to have unsecured boot, don't know how that helps and i don't get the ideea behind it anyways, so the right way to do it is to Unlock Bootloader -> Flash Recovery -> Root -> S-OFF -> Free to try whatever custom ROM out there you want, hard bricking is pretty hard even without common sense, i personally tried to do it and i failed, i think you need to know how to brick it in order to brick it, but to avoid that, make sure you do things the right way, read things before you try and so on.

Lexmazter said:
From what i know, that Chinese ROM was supposed to have unsecured boot, don't know how that helps and i don't get the ideea behind it anyways, so the right way to do it is to Unlock Bootloader -> Flash Recovery -> Root -> S-OFF -> Free to try whatever custom ROM out there you want, hard bricking is pretty hard even without common sense, i personally tried to do it and i failed, i think you need to know how to brick it in order to brick it, but to avoid that, make sure you do things the right way, read things before you try and so on.
Click to expand...
Click to collapse
a simple way to do a hard brick:
flash a rom with only has the vold.fstab for hboot 1.25 and device is 1.28 , then mount sdcard for pc and format sdcard (pc says you need to do it before it can read the sdcard) - the result = BRICKED

[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] Recovery has Dissappeared: Please Help

Hi everyone,
I flashed the OTA update for the AOSB rom earlier today. Upon doing so I realised that my Gapps weren't functioning properly: so, I went to go into my recovery to re-flash them but wait. My recovery seems to have disappeared. I have tried manually flashing the boot.img and I have also tried adb reboot recovery; I have also tried flashing Philz CWMR but to no avail. The LED does not turn on during boot to indicate that there is a recovery option and I am unable to find any way to get into recovery to reflash Gapps.
So, I would really appreciate it if someone could let me know how to get my recovery back, or, if all else fails, just to flash gapps some other way.
Thanks in advance!
n30d3xx0r
Device Details:
Xperia z1 (Honami)
Running AOSB 4.3.3
MOD EDIT: Warez reference.

n30d3xx0r said:
Hi everyone,
I flashed the OTA update for the AOSB rom earlier today. Upon doing so I realised that my Gapps weren't functioning properly: so, I went to go into my recovery to re-flash them but wait. My recovery seems to have disappeared. I have tried manually flashing the boot.img and I have also tried adb reboot recovery; I have also tried flashing Philz CWMR but to no avail. The LED does not turn on during boot to indicate that there is a recovery option and I am unable to find any way to get into recovery to reflash Gapps.
So, I would really appreciate it if someone could let me know how to get my recovery back, or, if all else fails, just to flash gapps some other way.
Thanks in advance!
n30d3xx0r
Device Details:
Xperia z1 (Honami)
Running AOSB 4.3.3
Click to expand...
Click to collapse
Try to restart to recovery from power menu (from ROM), that wilk work if you still have recovery..
Couldn't you just go to fastboot mod and flash boot.img with recovery?
I'm not 100% sure there is kernel with recovery to fastboot for Z1 but I know that was the easiest way on XS...
If that fails, download Goomanager from market and install recovery with it...
Sent from my D6503 using Tapatalk

Use fastboot to flash the boot.img and please post the output here

Will give it a shot
funky0308 said:
Try to restart to recovery from power menu (from ROM), that wilk work if you still have recovery..
Couldn't you just go to fastboot mod and flash boot.img with recovery?
I'm not 100% sure there is kernel with recovery to fastboot for Z1 but I know that was the easiest way on XS...
If that fails, download Goomanager from market and install recovery with it...
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply.
I've tried getting into recovery that way as well (already had it in my power menu) but to no avail either: I think it might be gone.
If by that you mean extract the boot.img from the rom zip and flash that then yes I have tried it.
And as for your third suggestion I'll take a look at that and let you know how it goes.
Thanks again!

All looks fine to me
gregbradley said:
Use fastboot to flash the boot.img and please post the output here
Click to expand...
Click to collapse
I tried it again: here's the output. I'm not an expert by any means but that looks fine to me?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot aosbboot.img
sending 'boot' (8178 KB)...
OKAY [ 0.260s]
writing 'boot'...
OKAY [ 0.532s]
finished. total time: 0.795s
Thanks!

I've fixed it!
Thanks for all of your help but I worked out how to fix it
For future reference, if anyone has the same issue download the Z1 multirecovery package and run that.
Sorry, I can't post the link
Should solve the problem
Thanks for all of your help anyway!

I wonder if its just a wronf sequence of button pressing
Maybe the boot.img for that rom has not implemented the LED notification, and maybe you need to press volume up or volume down......
But there should be a recovery in that kernel

[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.

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