problem

smeer

I have a Pixel 6a phone. I installed Graphene OS, then formatted it and installed e/OS, but it hasn't worked since. I need a solution.

Developer-Dude

smeer I have a Pixel 6a phone. I installed Graphene OS, then formatted it and installed e/OS, but it hasn't worked since. I need a solution.

Some more info may help.

smeer I installed Graphene OS, then formatted it and installed e/OS

So you mean you "formatted" it by factory resetting it, or by erasing GrapheneOS and installing /e/ ?

smeer but it hasn't worked since

What hasn't worked since? The phone? The OS? A specific feature? Currently, what OS is the phone running? Stock Pixel Android, GrapheneOS, or /e/ ?

Johnnyloans

smeer

Do you have an error message it says
Can you be our eyes?
Does it show the Google logo then it says corrupted system partition or what?

smeer

Developer-Dude
الهاتف عند ريطه باللابتوب يصدر صوت الارتباط لكن الشاشه سوداء
النظام الحالي نظام اي اوه اس لكن لايعمل ولا يشتغل الهاتف تماما
نظام الاندرويد بكسل الاصلي قد تم تغييره بنظام قراف فون اه اس ثم تم ترويته مره اخرى برومه اي اه اس ولكن الان لا يعمل اي منهما اصبح الهاتف شاشه سوداء

smeer

Johnnyloans

المشكله اني قمت بتحميل نظام
الجرافين
فوق هاتف قوقل بكسل 6 ايه وكان الهاتف يعمل بشكل سليم ثم قررت ان احمله نظام اي اوه اس فقمت بتنزيل الرومه من الموقع الرسمي هي
جوجل بيكسل 6a
"الزرقاء"
A16
مجتمع
شبكة الأمان: نعم
مشروب الروت بير: نعم
وثيقة تثبيت المجتمع
2022
قمت بفتح البوت لودر قفل المصنع وتحميل اولا الري كفري ثم الدخول الى الري كفري وتحميل الرومه واثناء التحميل كان يظهر خطاء وبعد الانتهاء من عملية التحميل خرج قبل الانتهاء من عملية التثبيت بعد العد الى 47 ثم ظهرت خيارات الري كفري قمت بالضغط على خيار الريبوت اعادة تشغيل لكن لم يشتغل بعدها اصبح شاشه سوداء وعند ربطه بالابتوب يصدر صوت الارتباط لكن الاشاشه سوداء ولا يقوم بالاقلاع والدخول الى الهاتف يبقى كما هو على الشاشه السوداء

smeer

المشكله اني قمت بتحميل نظام
graphene
فوق هاتف قوقل بكسل 6 ايه وكان الهاتف يعمل بشكل سليم ثم قررت ان احمله نظام اي اوه اس فقمت بتنزيل الرومه من الموقع الرسمي هي
Google Pixel 6a
"bluejay"
A16
Community
Safetynet : Yes
Rootbeer: Yes
Community install doc
2022
قمت بفتح البوت لودر قفل المصنع وتحميل اولا الري كفري ثم الدخول الى الري كفري وتحميل الرومه واثناء التحميل كان يظهر خطاء وبعد الانتهاء من عملية التحميل خرج قبل الانتهاء من عملية التثبيت بعد العد الى 47 ثم ظهرت خيارات الري كفري قمت بالضغط على خيار الريبوت اعادة تشغيل لكن لم يشتغل بعدها اصبح شاشه سوداء وعند ربطه بالابتوب يصدر صوت الارتباط لكن الاشاشه سوداء ولا يقوم بالاقلاع والدخول الى الهاتف يبقى كما هو على الشاشه السوداء

Developer-Dude

smeer

smeer
Ummm, English would help quite a lot to start.

smeer

ماهو الحل وهل يوجد طريقه لاعادة اصلاح الهاتف

Johnnyloans

smeer

You should translate to English then post the result here.

Luckily your bootloader is still unlocked so you can still flash any OS onto it then use the phone.

It'd be good to know the exact error it said when reaching 47% to know what's wrong.

Also, look at this comment for more I formation about that.
https://discuss.grapheneos.org/d/35574-random-crash-resulted-in-infinite-boot-loop/7

Make sure to install a recent, new version of the OS you choose. An older version might be incompatible with the bootloader on your phone.

Flash an OS again.
There are many options: Google stock OS, eOS, grapheneos, lineageOS

I have no idea if all of those are still updated. Do research on what you want.

smeer

Developer-Dude
When the phone is connected to the laptop, it makes a connection sound, but the screen is black.
The current system is e/OS, but it doesn't work and the phone doesn't turn on at all.
The original Android Pixel system was replaced with GraPhene AS and then re-rooted with AAS, but now neither works; the phone has a black screen.

I don't speak English very well.

smeer

Developer-Dude

Finding update package...
Verifying update package...
ERROR: recovery: footer is wrong
Update package verification took 0.2 s (result 1).
ERROR: recovery: Signature verification failed
ERROR: recovery: error: 21
and
Total xfer: 0.00x

yes this massage that is appear

Developer-Dude

smeer seems like possibly a screen failure, as @Johnnyloans mentioned. But we'll see what else it could be

de0u

smeer What is the step before that message?

It looks as if perhaps one system's OTA image is being sent to another system's Recovery, which won't work.

What happens if Google's flasher is used?

smeer

the phone is dead it can not charge, there is no sign the phone is alive but on windows device manager it appear when press power + vol up +vol down as serial port COM

de0u

smeer If the phone is dead, how is the "Signature verification failed" message obtained?

Johnnyloans

smeer

Maybe the screen is broken. The screen isn't showing anything.

It might possibly be that the phone did boot up into eOS but now the screen is broken?

It should show something while first booting up and should shoe something while off and charging. Both of these should show something on the screen even if the OS is not working.