Database Develop

[Q] [Help] Unique situation: root to unroot OR just unroot

Question/issues solved - thread done!
Picture of M7 screen with information: http://imgur.com/a/l6hIg
Basically, last year I traded this phone for my current phone at the time with a T-Mobile employee.
Got home and reset everything, setup everything to my liking, etc.
I then tried to go through the rooting process and all that but it didn't work (sadly, this was a while ago and I don't remember the exact issue...).
I tried everything I could but nothing worked and so I gave up since the phone was working fine other than it not being 'rootable'.
Fast forward to a couple days ago and I found a great deal on the M8 and have been using it to make sure it is everything the seller said it would be.
Then my friend said he wants to buy my M7 and I said sure but I need some time to backup my stuff and clear/reset the phone.
So the real details/interesting part of the situation is this:
Between when I got the M7 and a couple days ago the performance of the M7 has degraded and by this I mean that I have to restart the phone to get mobile data working (even though the symbol shows 4g/LTE), some apps have randomly crashed (namely Maps but it seems updates have fixed that). When I did try to root and all that, I installed TitaniumBackUp Pro and Root Explorer (here comes the interesting part) - sometimes TPUP has root access and sometimes it doesn't have root access; however, Root Explorer has always worked for what I needed (looking for downloaded files).
So is it possible to somehow properly root the phone and then unroot to make sure everything is good to go for my friend or do I need to just unroot the phone? Or do I simply need to do a factory reset (I am fine with this since I have all my contacts on the M8 already)? I haven't touched any software/rooting stuff since my 1 and only attempt to root the phone.
Sorry for the wall of text and I did try searching for similar posts/threads but couldn't (maybe I searched the wrong words?) and please feel free to ask questions for clarification and I will do my best to respond ASAP! Thank you in advance for your help.

CTR01 said:
Picture of M7 screen with information: http://imgur.com/a/l6hIg
Basically, last year I traded this phone for my current phone at the time with a T-Mobile employee.
Got home and reset everything, setup everything to my liking, etc.
I then tried to go through the rooting process and all that but it didn't work (sadly, this was a while ago and I don't remember the exact issue...).
I tried everything I could but nothing worked and so I gave up since the phone was working fine other than it not being 'rootable'.
Fast forward to a couple days ago and I found a great deal on the M8 and have been using it to make sure it is everything the seller said it would be.
Then my friend said he wants to buy my M7 and I said sure but I need some time to backup my stuff and clear/reset the phone.
So the real details/interesting part of the situation is this:
Between when I got the M7 and a couple days ago the performance of the M7 has degraded and by this I mean that I have to restart the phone to get mobile data working (even though the symbol shows 4g/LTE), some apps have randomly crashed (namely Maps but it seems updates have fixed that). When I did try to root and all that, I installed TitaniumBackUp Pro and Root Explorer (here comes the interesting part) - sometimes TPUP has root access and sometimes it doesn't have root access; however, Root Explorer has always worked for what I needed (looking for downloaded files).
So is it possible to somehow properly root the phone and then unroot to make sure everything is good to go for my friend or do I need to just unroot the phone? Or do I simply need to do a factory reset (I am fine with this since I have all my contacts on the M8 already)? I haven't touched any software/rooting stuff since my 1 and only attempt to root the phone.
Sorry for the wall of text and I did try searching for similar posts/threads but couldn't (maybe I searched the wrong words?) and please feel free to ask questions for clarification and I will do my best to respond ASAP! Thank you in advance for your help.
Click to expand...
Click to collapse
probably a better idea to reset the phone back to stock. can you post the output of "fastboot getvar all" except imei/serialno?

alray said:
probably a better idea to reset the phone back to stock. can you post the output of "fastboot getvar all" except imei/serialno?
Click to expand...
Click to collapse
@alray:
Thanks for the quick reply. I will gladly just reset to stock if that's the easiest/best method.
I currently don't have ADB setup on either computer since I haven't been in the rooting game for a long while now.
As of now I'm on my MacBook Pro 13" with Retina display and Mac OSX 10.9.4 and internet connection.
My home Windows desktop currently doesn't have internet due to some issues at home...
So I'm guessing the first thing is to setup ADB on the Mac (if possible?), though I haven't done it before on a Mac.
Thanks.

CTR01 said:
@alray:
Thanks for the quick reply. I will gladly just reset to stock if that's the easiest/best method.
I currently don't have ADB setup on either computer since I haven't been in the rooting game for a long while now.
As of now I'm on my MacBook bla bla bla.
My home Windows desktop currently doesn't have internet due to some issues at home...
So I'm guessing the first thing is to setup ADB on the Mac (if possible?), though I haven't done it before on a Mac.
Thanks.
Click to expand...
Click to collapse
yes its also possible to have adb and fastboot on mac, just make a quick google search and you'll find a great thread how to setup fastboot/adb on mac.

alray said:
yes its also possible to have adb and fastboot on mac, just make a quick google search and you'll find a great thread how to setup fastboot/adb on mac.
Click to expand...
Click to collapse
@alray:
Great, thanks for that and I will be sure to update here as soon as it is all setup.

@alray:
I found this link from a Google search that showed me how to install adb/fastboot on Mac in less than 5 minutes and my M7 is showing up in the adb devices list.
Screen shot with all the info is attached.
Sorry for the delayed reply, had to eat dinner.

CTR01 said:
@alray:
I found this link from a Google search that showed me how to install adb/fastboot on Mac in less than 5 minutes and my M7 is showing up in the adb devices list.
Screen shot with all the info is attached.
Sorry for the delayed reply, had to eat dinner.
Click to expand...
Click to collapse
So you have probably unlocked the bootloader in your attempt to root the phone. When you unlock the bootloader, it wipe users data but it also wipe some preloaded app by HTC in /data/preload. Problem is your friend will not be able to install ota updates with those missing files.
Good news is that there is a ruu for your phone version you could use to reset the phone back to stock and it will also wipe all your personal data at the same time, like if the phone was new (no need to factory reset). The ruu is a .exe file so you'll need a windows computer and because of the hboot version on the phone (1.44) you can't use windows 8.1 to flash the ruu, you'll need windows 7. Because your phone is S-ON, you'll also need to relock the bootloader before flashing the RUU. After flashing it, the phone will be wiped from any user data and ready to take ota updates.
so
relock bootloader:
Code:
fastboot oem relock
download the 1.27.531.11 ruu.exe from here
with the phone booted in bootloader mode or booted in the OS and connected to the windows 7 pc, lauch the ruu.exe and follow simple instructions so the ruu.exe will flash the phone automatically.
sell the phone to your friend

alray said:
So you have probably unlocked the bootloader in your attempt to root the phone. When you unlock the bootloader, it wipe users data but it also wipe some preloaded app by HTC in /data/preload. Problem is your friend will not be able to install ota updates with those missing files.
Good news is that there is a ruu for your phone version you could use to reset the phone back to stock and it will also wipe all your personal data at the same time, like if the phone was new (no need to factory reset). The ruu is a .exe file so you'll need a windows computer and because of the hboot version on the phone (1.44) you can't use windows 8.1 to flash the ruu, you'll need windows 7. Because your phone is S-ON, you'll also need to relock the bootloader before flashing the RUU. After flashing it, the phone will be wiped from any user data and ready to take ota updates.
so
relock bootloader:
Code:
fastboot oem relock
download the 1.27.531.11 ruu.exe from here
with the phone booted in bootloader mode or booted in the OS and connected to the windows 7 pc, lauch the ruu.exe and follow simple instructions so the ruu.exe will flash the phone automatically.
sell the phone to your friend
Click to expand...
Click to collapse
@alray:
My first post has a link to a picture of what the current status is of my phone, if you missed it before.
I will look at this part in more detail after I'm done with work
I'll post asap when I get a chance. Thanks!

@alray:
So I tried the bootlock command but then got the following error/problem (see screen shot).
I was either in the wrong mode or did stuff in the wrong order...
What I did:
1) open Terminal app
2) move to the adb/fastboot folder on Mac
3) type in the fastboot oem relock command
4) then received the attached screen shot error/problem.
I have a feeling the problem is going to be a bit tougher to solve than anticipated...
EDIT:
I have managed to screw up my device by doing factory reset and getting rid of the OS
EDIT 2:
I have managed to solve the above issue of no OS by getting CM 10 installed and working.
Now I need to get things back to stock to sell to my friend.
Thanks!

CTR01 said:
@alray:
So I tried the bootlock command but then got the following error/problem (see screen shot).
I was either in the wrong mode or did stuff in the wrong order...
What I did:
1) open Terminal app
2) move to the adb/fastboot folder on Mac
3) type in the fastboot oem relock command
4) then received the attached screen shot error/problem.
I have a feeling the problem is going to be a bit tougher to solve than anticipated...
EDIT:
I have managed to screw up my device by doing factory reset and getting rid of the OS
EDIT 2:
I have managed to solve the above issue of no OS by getting CM 10 installed and working.
Now I need to get things back to stock to sell to my friend.
Thanks!
Click to expand...
Click to collapse
sorry mate, my bad! The correct command is "fastboot oem lock" not "fastboot oem relock"

alray said:
sorry mate, my bad! The correct command is "fastboot oem lock" not "fastboot oem relock"
Click to expand...
Click to collapse
@alray:
No worries, I'll try that and get back to you.
Thanks.
Sent from my HTC One_M8

@alray:
So quick recap:
1) use the fastboot oem lock command
2) install the RUU.exe that you linked to me (I have it downloaded) on a Windows 7 computer (which I have)
3) then everything should be good to go and I can sell to my friend
Question:
Do I need to have HTC Sync Manager and/or USB drivers installed on the Windows 7 computer for the above process to work?

CTR01 said:
@alray:
So quick recap:
1) use the fastboot oem lock command
2) install the RUU.exe that you linked to me (I have it downloaded) on a Windows 7 computer (which I have)
3) then everything should be good to go and I can sell to my friend
Question:
Do I need to have HTC Sync Manager and/or USB drivers installed on the Windows 7 computer for the above process to work?
Click to expand...
Click to collapse
yes you need the drivers, but better to have htc sync uninstalled

alray said:
yes you need the drivers, but better to have htc sync uninstalled
Click to expand...
Click to collapse
Great, thanks for that clarification. I'll update you when I get a chance to run through the steps!

@alray:
I don't think that the M7 is communicating with the computer/adb based on the screen shot attached and that after typing in the command to lock the bootloader, it keeps waiting for device.
Thoughts?
Sent from my HTC One_M8

CTR01 said:
@alray:
I don't think that the M7 is communicating with the computer/adb based on the screen shot attached and that after typing in the command to lock the bootloader, it keeps waiting for device.
Thoughts?
Sent from my HTC One_M8
Click to expand...
Click to collapse
driver installed incorrectly? Is the phone listed in windows device manager when booted in bootloader?

alray said:
driver installed incorrectly? Is the phone listed in windows device manager when booted in bootloader?
Click to expand...
Click to collapse
@alray:
Yeah, the drivers installed just fine.
However, I actually just showed my friend the phone with CM10 on it and told him the pros/cons and he was just fine with everything since he just wanted a phone that would work and not freeze/lag like his current phone does.
So thank you for your help and the situation has been solved!

[Q] Extremely Slow Xperia SP

Im really sorry for posting this question, but im really really noob at this.
I Have a Xperia SP C5303 with stock Android 4.3 and 12.1.A.1.205 and bootloader locked.
My phone is getting extremely slow at everthing, all applications take huge time to load, sometimes even crash, i cleared all cache on applications, even deleted all my messages (1.5years) and nothing worked. Started in safe mode and its pretty fast.
Im tempted to update my SP to a custom rom 4.4.x or even 5.xx .....but i really dont know nothing about it. Dont know how should i proceed and what steps should i take to backup and prevent any problem in case of something goes wrong.
I already used the "towelroot" and installed SuperSU from google playstore and it says its rooted, but already read somewhere that towelroot doesnt actually really root.
I really really appreciate a huge help on this if possible.
Thank you very much.

bravept said:
Im really sorry for posting this question, but im really really noob at this.
I Have a Xperia SP C5303 with stock Android 4.3 and 12.1.A.1.205 and bootloader locked.
My phone is getting extremely slow at everthing, all applications take huge time to load, sometimes even crash, i cleared all cache on applications, even deleted all my messages (1.5years) and nothing worked. Started in safe mode and its pretty fast.
Im tempted to update my SP to a custom rom 4.4.x or even 5.xx .....but i really dont know nothing about it. Dont know how should i proceed and what steps should i take to backup and prevent any problem in case of something goes wrong.
I already used the "towelroot" and installed SuperSU from google playstore and it says its rooted, but already read somewhere that towelroot doesnt actually really root.
I really really appreciate a huge help on this if possible.
Thank you very much.
Click to expand...
Click to collapse
first of all (search for doing this !! )
take a TA partition backup and then unlock your bootloader .....then install the recoveries on the stock ROM>>then replay to me after that

Ok. Thank you.
Already did the TA Backup with Backup-TA-9.11, now moving on to search "unlocking bootloader"....

bravept said:
Ok. Thank you.
Already did the TA Backup with Backup-TA-9.11, now moving on to search "unlocking bootloader"....
Click to expand...
Click to collapse
I think unlocking your bootloader resets everything so backup your apps for re installation once your are done.
I unlocked my bootloader the good old fashioned way via fastboot :
1 - Check if unlocking possible by typing *#*#7378423#*#* in the dialer and going into Service info > Configuration.
2 - If it says something like Bootloader unlock allowed - Yes then its unlockable. If its already unlocked, it will say something along those line as well.
If neither option appears then it isn't unlockable.
3 - Get the unlock code from Sony after filling the necessary details along with the IMEI no. of the phone.
3 - Open command prompt in the adb & flashboot folder by holding Shift + right click and selecting the "open command window here" option.
4 - Type fastboot.exe -i 0x0fce getvar version to check if device is connected properly.
5 - Type fastboot.exe -i 0x0fce oem unlock 0xKEY. Repalce KEY with the code that was received from Sony and hit Enter.
Alternatively the BLU option in FlashTool can be used to simplify things as it automates most of the above procedure. It can also be used to relock your bootloader.
There's also a new app called Kingo SONY Bootloader Unlock that apparently unlocks your bootloader with one click. Check it out.

I was doing that at the moment. Im using Fastboot also ....since i didnt find other ways
Already made a copy of everthing i can remember and used Titan backup also.
My phone says "Bootloader unlock allowed : no" , but im still trying doing all the thing....i read somewhere that sometimes works.
At the moment im stuck in connecting the phone in the computer with volume up ...and testing the fastboot getvar version to check if the phone is connected....but stays there....waiting for device...and nothing ...

bravept said:
I was doing that at the moment. Im using Fastboot also ....since i didnt find other ways
Already made a copy of everthing i can remember and used Titan backup also.
My phone says "Bootloader unlock allowed : no" , but im still trying doing all the thing....i read somewhere that sometimes works.
At the moment im stuck in connecting the phone in the computer with volume up ...and testing the fastboot getvar version to check if the phone is connected....but stays there....waiting for device...and nothing ...
Click to expand...
Click to collapse
If it says no then dunno what the chances of success are.
Came across this Youtube tutorial : https://www.youtube.com/watch?v=Li8Eim6gugw
Don't know how legit it is since its been posted a few months back and there are no comments at all so please proceed with caution and of course don't blame me if you brick your device
Also did you try the Kingo unlock app I mentioned?

Nothing works...cant really connect in Fastboot mode...i tried everthing...even in 3 diferent computers...nothing works.
Dont know if "bootloader unlock allowed : no" means that i cannot enter in fastboot mode....or if im doing something wrong...

Just install some 4.4.4 lbl build, for example cm11 by mateo337 is really good and even up-to-date.
You will not be able to unlock the boot loader i had XSP that said no and i was not able to do anything about it.
Dont use 5.x.x builds, they are really outdated and have a lot of bugs.

So, then i suppose the next step its to install a LBL Recovery? So i can boot in recovery to flash the custom rom....right?

bravept said:
Nothing works...cant really connect in Fastboot mode...i tried everthing...even in 3 diferent computers...nothing works.
Dont know if "bootloader unlock allowed : no" means that i cannot enter in fastboot mode....or if im doing something wrong...
Click to expand...
Click to collapse
No you should still be able to enter fastboot mode. Are you using the latest version of FlashTool and have you installed all 3 required drivers? Does your phone show up in device manager when you connect it in fast boot mode?
I am not sure abt the last 2 procedures I posted but the first 2 require your phone to boot into fastboot and stay there till the job's done.
bravept said:
So, then i suppose the next step its to install a LBL Recovery? So i can boot in recovery to flash the custom rom....right?
Click to expand...
Click to collapse
Yeah. Since your phone's rooted now, you can follow a LBL procedure for flashing a custom recovery to allow you to install custom ROMs.
Sent from my Xperia SP using XDA Free mobile app

[Q] I think I hard bricked my N6

Hi there,
So I just bought a brand new N6.
Did nothing to it, did not unklock the bootloader, di not flash anything.
Just ran it a first time, set my account, donwloaded the 5.1 OTA when proposed to and then it was over.
After the OTA installation my phone displayed a dead android and "Error".
When rebooting my phone, the apps are "optimizing" undefinitely and then the phone will restart.
I tried factory reset from recovery, that did nothing, I mean, the phone will still bootloop endlessly.
My bootloader is not unlocked so I cannot flash my phone..
Is there anything I can do ?
Thank you in advance

Aanze said:
Hi there,
So I just bought a brand new N6.
Did nothing to it, did not unklock the bootloader, di not flash anything.
Just ran it a first time, set my account, donwloaded the 5.1 OTA when proposed to and then it was over.
After the OTA installation my phone displayed a dead android and "Error".
When rebooting my phone, the apps are "optimizing" undefinitely and then the phone will restart.
I tried factory reset from recovery, that did nothing, I mean, the phone will still bootloop endlessly.
My bootloader is not unlocked so I cannot flash my phone..
Is there anything I can do ?
Thank you in advance
Click to expand...
Click to collapse
try fastboot formatting userdata and fastboot formatting cache

simms22 said:
try fastboot formatting userdata and fastboot formatting cache
Click to expand...
Click to collapse
Same story.
Black screen then reboot, then optimizing then reboot and so on...

Aanze said:
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Click to expand...
Click to collapse
Well, since you haven't enabled OEM unlock, there's not much you can do besides RMA at this point.

Aanze said:
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Click to expand...
Click to collapse
unfortunately, that might have been your only option. as you need to boot up first, to enable unlocking of your bootloader, to reflash the factory image. and you cant boot up

Evolution_Tech said:
Well, since you haven't enabled OEM unlock, there's not much you can do besides RMA at this point.
Click to expand...
Click to collapse
That's what I thought.
I thought I could use the fix described here http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518 but my device does not appear as "qhusb_bulk" like specified so I guess its over.

id get the phone refurbished, from google or from motorola, since it wasnt anything that you did, but was the updates fault. btw, that happens, very rarely, but it does happen that updates can cause issues.

simms22 said:
id get the phone refurbished, from google or from motorola, since it wasnt anything that you did, but was the updates fault. btw, that happens, very rarely, but it does happen that updates can cause issues.
Click to expand...
Click to collapse
Well thank you anyway, looks like I have no other choice than send the device back.
One last question, since my phone won't stop rebooting endlessly is there any way to turn it off ? Long press on power does not do anythng, it will stil restart...
Edit: I found how to turn it off through bootloader.

Aanze said:
Well thank you anyway, looks like I have no other choice than send the device back.
One last question, since my phone won't stop rebooting endlessly is there any way to turn it off ? Long press on power does not do anythng, it will stil restart...
Edit: I found how to turn it off through bootloader.
Click to expand...
Click to collapse
exactly. i was just gonna write how to do that.

simms22 said:
exactly. i was just gonna write how to do that.
Click to expand...
Click to collapse
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?

Aanze said:
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Click to expand...
Click to collapse
If getting that it should unlock. Got nothing to lose and if does unlock it is recoverable.

Aanze said:
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Click to expand...
Click to collapse
yes! if you can unlock the bootloader, then you can flash the factory image via fastboot while youre in your bootloader. which would fix you not booting

prdog1 said:
If getting that it should unlock. Got nothing to lose and if does unlock it is recoverable.
Click to expand...
Click to collapse
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.

Aanze said:
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Click to expand...
Click to collapse
Your good to go. Just need to fastboot the stock images.

just return it, if you find that you cant recover it after unlocking the bootloader then they wont take it back

Aanze said:
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Click to expand...
Click to collapse
grab a factory image, and read directions for flashing a factory image. you want to flash each individual file inside separately, instead of using the flash-all script.

simms22 said:
grab a factory image, and read directions for flashing a factory image. you want to flash each individual file inside separately, instead of using the flash-all script.
Click to expand...
Click to collapse
Yep, doing it right now.. flashing system currently.. crossing fingers;.

crossing my fingers for you over here as well

It worked !! IT WORKED !
I love you xda ! really do love you.
Thanks a million.
(Although it's a bit strange that I was able to unlock bootloader without usb debbugging mode enabled no ?)

This is very interesting indeed. To the OP, where did you purchase the device? I find it very peculiar that you were able to issue the OEM unlock command without using the toggle in settings.

Bricked the phone and locked the bootloader! Seriously need help from you.

Hi friends,
I am telling you the whole story in a short way,
I have needed to root my devices, so I unlocked bootloader as it said on some web sites and install a new rom. Mine was Android 8.1 Nokia 7 plus TA-1046 600CN I think now its Pie 600WW.
After that that Pie did not work well on my devices, especially sensors and notifications was awful. So tried to downgrade to stock rom, but could not.
Right now, there is no rom on my device and bootloader and also locked the critical partitions.
I have TWRP recovery installed but i cant enter the recovery mode, the device is always in download mode even try to enter with volume UP + Power button phone goes directly download mode.
I have done something stupid with locking bootloader I agree but please help me to get out of this situation.
Its too bad without a phone
Thank you very much.

I dont know if it will work. Did you try to switch the partitions from A to B or B to A?
There are tutorials on how to do that via adb. I cant tell you exactly how to do it, i did it also from tutorials.

magiQx said:
I dont know if it will work. Did you try to switch the partitions from A to B or B to A?
There are tutorials on how to do that via adb. I cant tell you exactly how to do it, i did it also from tutorials.
Click to expand...
Click to collapse
in both partitions it is saying Your device is corrupt. It can't be trusted and will not boot.
and
I cant go into recovery

That sounds bad. Sorry, im not that advanced.
Isn't it possible to force it into recovery via adb? I got no idea, just asking.

magiQx said:
That sounds bad. Sorry, im not that advanced.
Isn't it possible to force it into recovery via adb? I got no idea, just asking.
Click to expand...
Click to collapse
Unfortunately I can`t because the bootloader is locked I have to unlock it but I can not because I have to downgrade the bootloader from Pie to Oreo

It sounds like a bad situation indeed. I think you may be SOOL, but hopefully a way forward will become apparent. Otherwise a new device might be indicated ?

1.unlock bootloader
2.reflash firmware with tools.
for piehttps://forum.xda-developers.com/nokia-7-plus/how-to/guide-workaround-flashing-sparse-t3906070
for oreohttps://forum.xda-developers.com/nokia-7-plus/how-to/workaround-flashing-oreo-firmware-t3793791

I ran into a similar situation and I installed the stock rom using NOST (Nokia Online Service Tool) and the stock rom in .NB0 file type.
If you need those files PM me and I can provide them for you, most likely you have them already if you unlocked your bootloader using TechMesto's service.

Pixel 5 - Removal from Beta 13 - Corrupt Error

So.... I removed my Pixel 5 form the beta 13 program, selected update on the devices and had it download Android 12 a few weeks back. On reboot I get the "device is corrupt" error with visit the g.co/ABH link. If I hit the power button that error loops, and trying a hard / factory reset does nothing.
I tried several of the steps but since I cannot get into Dev mode to unlock the bootloader I'm kind of stuck.
The most I have been able to do is with the rescue tool, but that throws a "software on device is newer then this tool" error and wont go forward.
Any suggestions? Should I just send in to a repair shop? Or move on?

I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA

xunholyx said:
I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA
Click to expand...
Click to collapse
Tried both types of cables, no luck...

grmacd said:
Tried both types of cables, no luck...
Click to expand...
Click to collapse
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.

V0latyle said:
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.
Click to expand...
Click to collapse
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet

grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
Unfortunate and I feel for you.
It's generally advisable to always unlock the bootloader when running any kind of beta software, just because of this eventuality - if something goes wrong, you need to have a way to recover the device.

grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
You should be able to boot to recovery from the bootloader

I can boot to recovery, but the software wont sideload since the boot locker is locked.
My one hope is the fact Rescue mode on the web is throwing "software on the device older then this tool" so I am hoping once that gets a newer version I will be ok. So into the drawer it goes...

But you don't need an unlocked bootloader to sideload an OTA....

xunholyx said:
But you don't need an unlocked bootloader to sideload an OTA....
Click to expand...
Click to collapse
Ok... perhaps I will give it another try tomorrow.

grmacd said:
Ok... perhaps I will give it another try tomorrow.
Click to expand...
Click to collapse
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now

xunholyx said:
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now
Click to expand...
Click to collapse
So this AM I downloaded the newest ZIP file and followed the step on the site - after about 10 minutes presto the phone is back up and running with Android 13! Thanks for your help!