After an automatic restart at night, my phonestuck in a bootloop

DeletedUser315

de0u doesn't the phone need to have USB debugging on to this though??

de0u

DeletedUser315 doesn't the phone need to have USB debugging on to this though??

For what?

I recommend referring to the directions on the GrapheneOS web site. I believe that neither the installation instructions nor the OTA instructions mention requiring USB debugging. USB debugging is designed for connecting a debugger to an Android device.

Edit: The OTA instructions explictly say that USB debugging is not needed. Overall the notion that doing anything "serious" with an Android device requires USB debugging is a misconception.

DeletedUser315

de0u For what?

Side loading updates

DeletedUser315

de0u Ah apoligies, I had read that on your last post but wasn't sure if you where just asking me this question > de0u For what? or answering it too for something else.
Again apologise I got confused. But that answers that then.

de0u

bastian_42 Then I'm afraid your next move may be a factory reset from Recovery.

bastian_42

de0u I just tryed to factory reset the device via the recovery menu. This resulted in an error:
--Wiping data... Error: recovery: Failed to recive number of sectors from init, system_a, /dev/block/dm-1,/dev/block/dm-2,/dev/block/dm-0 from snapuserd deamon ERROR: recovery: InitDmUserCow failed ERROR: recovery: Could not map dm-user device for partition system_a ERROR: recovery: Unable to map partitions to complete merge. Unable to check merge status and/or complete update merge. Unable to check merge status or complete merge, cannot wipe partitions.

de0u

DeletedUser315 Quoting from the GrapheneOS OTA instructions:

You do not need to have adb enabled within the OS or the host's ADB key whitelisted within the OS to sideload an update to recovery. Recovery mode does not trust the attached computer and this can be considered a production feature. Trusting a computer with ADB access within the OS is much different and exposes the device to a huge amount of attack surface and control by the trusted computer.

DeletedUser315

bastian_42 So that could be a hardware issue or just curupt data.
If anyone else has any better ideas you could try flashing back to stock and then reflashing GOS back.

You could try reflashing GOS straight away but not sure that will work.

de0u

bastian_42 To me that sounds like a potential failure of the flash storage, which seems consistent with the other symptoms described so far. But I am not an expert on that, so it might make sense to wait a bit to see if anybody else weighs in.

bastian_42

After, two weeks without further informations. I wanted to try the solution @DeletedUser315 suggested. The installation of the factory immage is falin gecaues the OEM is locked. Is there a way to performe a OEM unlock with out the ability to access the developer menue?

DeletedUser315

bastian_42 if you are trying to go back to stock have you done everything instructed here:
https://grapheneos.org/install/web#replacing-grapheneos-with-the-stock-os

And have you tried to unlock the boot loader via fastboot commands
https://source.android.com/docs/core/architecture/bootloader/locking_unlocking

bastian_42

DeletedUser315 the isue is the following, the OEM is locked and I didn't find a working solution to unlock. The mentioned Articel says:

boot to the home screen, open the Settings > System > Developer options menu and enable the OEM unlocking option

But I have no option to enter this Setting.

other8026

bastian_42 you can follow these instructions to do that https://grapheneos.org/install/web#enabling-oem-unlocking

bastian_42

other8026 Hi, the install instruction is the same are the mentioned Google ones. The issue is that the device is not booting. This is why I can't accses settings from the OS. I experymented wit a comand line tool for Samsung devices but this workaround is not working with Pixel devices.

« Previous Page