Hi All,
I have made an custom ROM for Huawei U8818 device.I flashed my device with the fastboot protocol and I received following messages during flash of device.
Code:
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.002s]
sending 'boot' (2806 KB)...
OKAY [ 0.713s]
writing 'boot'...
OKAY [ 0.778s]
sending 'recovery' (3124 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 0.602s]
sending 'system' (156310 KB)...
OKAY [ 39.081s]
writing 'system'...
OKAY [ 36.423s]
erasing 'userdata'...
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 0.007s]
rebooting...
finished. total time: 78.403s
From above it seems that device is flashed properly but when device is rebooting.
It does not proceed after boot screen.It simply stucks at boot screen.
How do I debug it.
Any suggestions.......
Hey guys,
i updated my razr to ics via the fastboot files. the update went through and i got a pass. now when i turn on my phone i get into a bootloop. sometimes the phone boots and restart after some minutes.
for the update i used rsd lite 5.7 and this fastboot file:
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.2_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml.zip
before the update i dont wipe my phone but now when i got into the bootloop i tried to wipe my phone but i am still in a bootloop.
have somebody an idea what i can do to get rid of this f*** bootloop?
I don't understand if you wiped and still have bootloop ore you couldn't wipe because of the bootloop.
If the latter, press powerbutton and vol down to reset and right after the reset press volume up and down and powerbutton
while the bootloop i make a force shut down and then i can boot in the recovery mode. so i can do a wipe i can also run in an ap fastboot mode but the factory recovery or the cache wipe do not help i got still the bootloop
Wipe again and try to reflash again with rds lite
already tried, i dosent help. i really dont know what the problem is. the updating process works fine no failures but i got into a bootloop
uhm is strange, are you sure that the sfb you are using is the correct one for your phone?
i was sure, now i am not i have a gsm retail razr and i think this is the right sbf, isnt it?
Seroga88i said:
i was sure, now i am not i have a gsm retail razr and i think this is the right sbf, isnt it?
Click to expand...
Click to collapse
What's your region Razr? It's .Eu, .Asia, .Latam?
Anyway, try erasing cache and data prior flash with rsd lite
Code:
fastboot erase cache
Code:
fastboot erase userdata
Cheers
i am in EU
i made data wipe and cache wipe before the flash with rsd lite, but no changes
Seroga88i said:
i am in EU
i made data wipe and cache wipe before the flash with rsd lite, but no changes
Click to expand...
Click to collapse
Do as I said and flash Ics again. Erase works somehow different from wipe.
.eu is your region razr?
Cheers
Sent from my XT910 using xda premium
oh sorry,
can you explain me how i can make a fastbook erase cache/userdata? i only know how to wipe data
yes the region of my razr is .eu
You have the sdk installed on your pc? If yes go into platform-tool with the cmd (if you are win, therminal if you are on linux/mac)
then type the life of pedro during fastboot ap
i did it like you both said. everything went fine the fastboot erase cache/userdata and the flash with the Final EU Android 4.0 ICS rom. but still i have a bootloop -.-
do you know is there an other ics rom which i can try for my razr?
i also tried to update with the leaked update file but i am still in a bootloop ....
Your razr is probably from another region.
Its not right to get a bootloop after flashing a stock rom and wipe data n cache.
Repeat the wipes in recovery. Both data n cache.
Cheers
Sent from my XT910 using xda premium
is it possible to find out which region my phone is?
if i flash with flashMe.bat i get this log:
have you an idea why i get this INFOPreflash validation failure?????
######################################
# EternityProject's FastBoot FlashME #
# #
# If you wanna support us, donate to #
# kholk -- [email protected] #
# #
# or come on our Website! #
# http://forum.eternityproject.eu #
# #
# Happy Flashing! #
######################################
ECHO ist ausgeschaltet (OFF).
Flashing BootLogo....
sending 'logo' (854 KB)... OKAY [ 0.109s]
writing 'logo'... INFOno such partition
FAILED (remote: )
Flashing EBR....
sending 'ebr' (16 KB)... OKAY [ 0.250s]
writing 'ebr'... OKAY [ 0.484s]
Flashing MBR....
sending 'mbr' (16 KB)... OKAY [ 0.203s]
writing 'mbr'... OKAY [ 0.437s]
Flashing DevTree....
sending 'devtree' (512 KB)... OKAY [ 0.172s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )
Flashing Android System....
sending 'system' (262144 KB)... OKAY [ 38.328s]
writing 'system'... OKAY [ 12.137s]
sending 'system' (262144 KB)... OKAY [ 40.622s]
writing 'system'... OKAY [ 10.546s]
sending 'system' (262144 KB)... OKAY [ 40.622s]
writing 'system'... OKAY [ 10.561s]
sending 'system' (6912 KB)... OKAY [ 1.076s]
writing 'system'... OKAY [ 0.343s]
Flashing Kernel....
sending 'boot' (8192 KB)... OKAY [ 1.154s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
Flashing Android Recovery....
sending 'recovery' (9216 KB)... OKAY [ 1.482s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Flashing CDR....
sending 'cdrom' (216832 KB)... OKAY [ 32.854s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
Flashing Radio (BP)....
sending 'radio' (14408 KB)... OKAY [ 2.184s]
writing 'radio'... OKAY [ 2.262s]
Flashing WebTop....
sending 'webtop' (262144 KB)... OKAY [ 33.181s]
writing 'webtop'... OKAY [ 11.482s]
sending 'webtop' (262144 KB)... OKAY [ 37.456s]
writing 'webtop'... OKAY [ 10.655s]
sending 'webtop' (262144 KB)... OKAY [ 36.442s]
writing 'webtop'... OKAY [ 10.624s]
sending 'webtop' (262144 KB)... OKAY [ 37.456s]
writing 'webtop'... OKAY [ 10.670s]
sending 'webtop' (262144 KB)... OKAY [ 36.379s]
writing 'webtop'... OKAY [ 10.702s]
sending 'webtop' (54016 KB)... OKAY [ 7.753s]
writing 'webtop'... OKAY [ 2.449s]
Erasing Cache....
erasing 'cache'... OKAY [ 0.889s]
Rebooting....
rebooting...
ECHO ist ausgeschaltet (OFF).
ECHO ist ausgeschaltet (OFF).
Greets from the EternityProject!
Maybe your download is corrupted, check the Md5 or download it again just to be sure.
Jaocagomez said:
Maybe your download is corrupted, check the Md5 or download it again just to be sure.
Click to expand...
Click to collapse
I agree. The radio wouldn't be flashed if it was a wrong region rom.
Anyway, check your region razr in motorola support page. Check for ur warranty status ir will return ur razr region n carrier
Meanwhile: download and flash this with rsd lite 5.7
http://forum.xda-developers.com/showthread.php?t=1747800
Cheers
Sent from my XT910 using xda premium
my razr is on warranty, the region is DE. and i flash it again on the first reboot its starts and i was possible to login in my google account than the device went off
I checkt the logs on the booting process and on the bootloop.
you can see the logs from the logcat in the attached files, maybe someone see the problem for the bootloop
Hi All,
i have created my own factory cable and i can now boot the phone up in to the recovery menu, but when i try to flash anything including the Utility i keep getting this error =
< waiting for device >
sending 'boot' (8192 KB)... OKAY [ 0.796s]
writing 'boot'... OKAY [ 0.830s]
sending 'recovery' (9216 KB)... OKAY [ 0.948s]
writing 'recovery'... FAILED (status read failed (Too many links))
Is there something i can do to correct this?
i also tried to do it manually and get the same,im on a UK razr if that helps
flash system system.img
< waiting for device >
sending 'system' (793344 KB)... OKAY [ 82.924s]
writing 'system'... INFOPreflash validation failure
FAILED (remote: )
finished. total time: 83.136s
flash radio radio.img
sending 'radio' (14404 KB)... OKAY [ 1.468s]
writing 'radio'... FAILED (status read failed (Too many links))
finished. total time: 2.124s
[Q&A] [GSM/CDMA] EternityProject's RSD Alternative for flashing OFFICIAL Motorola RO
Q&A for [GSM/CDMA] EternityProject's RSD Alternative for flashing OFFICIAL Motorola ROMs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GSM/CDMA] EternityProject's RSD Alternative for flashing OFFICIAL Motorola ROMs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
xirnibor said:
I'm getting AP Fastboot Flash Mode (s) Boot Failure
0a.6c
device is locked. status code: 0
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG HAB (CG: system, status: 0X0035)
Invalid CG OTV (CG: system)
Flashed SPDREM_U_01.6.5.1-73_SPU-11-PASS-10_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml
using 'flashme.bat' method - here is a copy/paste of results - please advise
C:\Users\rrix\Downloads\android\android\tools>flashME
######################################
# EternityProject's FastBoot FlashME #
# #
# If you wanna support us, donate to #
# kholk -- [email protected] #
# #
# or come on our Website! #
# http://forum.eternityproject.eu #
# #
# Happy Flashing! #
######################################
ECHO is off.
Flashing BootLogo....
< waiting for device >
sending 'logo' (854 KB)... OKAY [ 0.086s]
writing 'logo'... INFOno such partition
FAILED (remote: )
Flashing EBR....
sending 'ebr' (16 KB)... OKAY [ 0.248s]
writing 'ebr'... INFOPreflash validation failure
FAILED (remote: )
Flashing MBR....
sending 'mbr' (16 KB)... OKAY [ 0.257s]
writing 'mbr'... INFOPreflash validation failure
FAILED (remote: )
Flashing DevTree....
sending 'devtree' (512 KB)... OKAY [ 0.303s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )
Flashing Android System....
sending 'system' (262144 KB)... OKAY [ 24.843s]
writing 'system'... OKAY [ 10.986s]
sending 'system' (262144 KB)... OKAY [ 24.841s]
writing 'system'... OKAY [ 10.391s]
sending 'system' (262144 KB)... OKAY [ 24.814s]
writing 'system'... OKAY [ 0.050s]
sending 'system' (6912 KB)... OKAY [ 0.633s]
writing 'system'... OKAY [ 0.463s]
Flashing Kernel....
sending 'boot' (8192 KB)... OKAY [ 0.787s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
Flashing Android Recovery....
sending 'recovery' (9216 KB)... OKAY [ 0.992s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Flashing CDR....
sending 'cdrom' (216832 KB)... OKAY [ 20.711s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
Flashing Radio (BP)....
sending 'radio' (14408 KB)... OKAY [ 1.400s]
writing 'radio'... OKAY [ 1.693s]
Flashing WebTop....
sending 'webtop' (262144 KB)... OKAY [ 25.054s]
writing 'webtop'... OKAY [ 11.457s]
sending 'webtop' (262144 KB)... OKAY [ 24.171s]
writing 'webtop'... OKAY [ 10.471s]
sending 'webtop' (262144 KB)... OKAY [ 24.468s]
writing 'webtop'... OKAY [ 10.478s]
sending 'webtop' (262144 KB)... OKAY [ 24.442s]
writing 'webtop'... OKAY [ 10.502s]
sending 'webtop' (262144 KB)... OKAY [ 24.315s]
writing 'webtop'... OKAY [ 10.552s]
sending 'webtop' (54016 KB)... OKAY [ 5.073s]
writing 'webtop'... OKAY [ 2.404s]
Erasing Cache....
erasing 'cache'... OKAY [ 0.888s]
Rebooting....
rebooting...
ECHO is off.
ECHO is off.
Greets from the EternityProject!
Press any key to continue . . .
_____
resolved the issue following these steps here - http://forum.xda-developers.com/showthread.php?t=1416058 -
thanks xda
Click to expand...
Click to collapse
I HAVE SAME PROBLEM can you plzz explain me hoW TO RESOLVE IT?
Can you plzz telll me how can . Solve this?
I'm experimenting with a CalyxOS (13) fork, and suddenly broke booting (on a quite late stage — getting an NPE caused by my change in UserManagerService creation).
Other partitions, including boot should be fine, as I did no changes to their contents.
Device was stuck in a bootloop for ~3 reboots, then turned off and now does not react to any actions: any keys combination, holding power for about a minute or connecting a charger.
It was fully charged, and I've also tried to leave it connected to the charger for about 12 hours.
Is there some other way to enter the bootloader to flash a fixed fw?
Probably died and needs to be charged. Charge it and reflash factory firmware to both slots and wipe data using pixel flasher
ne0ns4l4m4nder said:
Probably died and needs to be charged. Charge it and reflash factory firmware to both slots and wipe data using pixel flasher
Click to expand...
Click to collapse
That's strange, because before bootloop it was fully charged, I don't think it could fully discharge in 2-3 minutes.
And I've also already tried to charge it, it doesn't react to charger even after being connected for 12 hours.
tibl37 said:
I'm experimenting with a CalyxOS (13) fork, and suddenly broke booting (on a quite late stage — getting an NPE caused by my change in UserManagerService creation).
Other partitions, including boot should be fine, as I did no changes to their contents.
Device was stuck in a bootloop for ~3 reboots, then turned off and now does not react to any actions: any keys combination, holding power for about a minute or connecting a charger.
It was fully charged, and I've also tried to leave it connected to the charger for about 12 hours.
Is there some other way to enter the bootloader to flash a fixed fw?
Click to expand...
Click to collapse
Did you have the A13 bootloader flashed to both slots? Symptoms are similar to when the new ARB bricks the Pixel 6 devices, whereby user only had the A13 bootloader on 1 slot, phone got into a bootloop, then reverted to the opposite slot which had the A12 bootloader on it, leading to a brick that so far has been unrecoverable except to RMA it.
Lughnasadh said:
Did you have the A13 bootloader flashed to both slots? Symptoms are similar to when the new ARB bricks the Pixel 6 devices, whereby user only had the A13 bootloader on 1 slot, phone got into a bootloop, then reverted to the opposite slot which had the A12 bootloader on it, leading to a brick that so far has been unrecoverable except to RMA it.
Click to expand...
Click to collapse
Hmm, looks like slot b still contained the original Android 12 bootloader
Here is the last fastboot log:
Bash:
Setting current slot to 'a' OKAY [ 0.072s]
Sending 'boot_a' (65536 KB) OKAY [ 1.749s]
Writing 'boot_a' OKAY [ 0.249s]
Sending 'dtbo_a' (16384 KB) OKAY [ 0.420s]
Writing 'dtbo_a' OKAY [ 0.063s]
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.026s]
Writing 'pvmfw_a' OKAY [ 0.007s]
Sending 'vbmeta_a' (8 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.002s]
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_a' OKAY [ 0.002s]
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_vendor_a' OKAY [ 0.002s]
Sending 'vendor_boot_a' (65536 KB) OKAY [ 1.648s]
Writing 'vendor_boot_a' OKAY [ 0.244s]
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.024s]
Resizing 'product_a' OKAY [ 0.003s]
Resizing 'system_a' OKAY [ 0.003s]
Resizing 'system_ext_a' OKAY [ 0.002s]
Resizing 'system_b' OKAY [ 0.002s]
Resizing 'vendor_a' OKAY [ 0.002s]
Resizing 'vendor_dlkm_a' OKAY [ 0.002s]
Resizing 'vendor_b' OKAY [ 0.002s]
Invalid sparse file format at header magic
Resizing 'product_a' OKAY [ 0.005s]
Sending sparse 'product_a' 1/5 (262120 KB) OKAY [ 7.131s]
Writing 'product_a' OKAY [ 1.034s]
Sending sparse 'product_a' 2/5 (262120 KB) OKAY [ 7.232s]
Writing 'product_a' OKAY [ 1.023s]
Sending sparse 'product_a' 3/5 (262120 KB) OKAY [ 7.282s]
Writing 'product_a' OKAY [ 1.095s]
Sending sparse 'product_a' 4/5 (262128 KB) OKAY [ 7.214s]
Writing 'product_a' OKAY [ 1.017s]
Sending sparse 'product_a' 5/5 (207840 KB) OKAY [ 5.494s]
Writing 'product_a' OKAY [ 0.865s]
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.004s]
Sending sparse 'system_a' 1/4 (262112 KB) OKAY [ 7.134s]
Writing 'system_a' OKAY [ 1.031s]
Sending sparse 'system_a' 2/4 (262120 KB) OKAY [ 7.087s]
Writing 'system_a' OKAY [ 1.089s]
Sending sparse 'system_a' 3/4 (262140 KB) OKAY [ 7.302s]
Writing 'system_a' OKAY [ 1.002s]
Sending sparse 'system_a' 4/4 (104872 KB) OKAY [ 2.835s]
Writing 'system_a' OKAY [ 0.501s]
Invalid sparse file format at header magic
Resizing 'system_ext_a' OKAY [ 0.004s]
Sending sparse 'system_ext_a' 1/2 (262124 KB) OKAY [ 7.442s]
Writing 'system_ext_a' OKAY [ 1.075s]
Sending sparse 'system_ext_a' 2/2 (89968 KB) OKAY [ 2.581s]
Writing 'system_ext_a' OKAY [ 0.357s]
Resizing 'system_b' OKAY [ 0.003s]
Sending 'system_b' (340 KB) OKAY [ 0.010s]
Writing 'system_b' OKAY [ 0.038s]
Invalid sparse file format at header magic
Resizing 'vendor_a' OKAY [ 0.005s]
Sending sparse 'vendor_a' 1/2 (262116 KB) OKAY [ 7.207s]
Writing 'vendor_a' OKAY [ 1.103s]
Sending sparse 'vendor_a' 2/2 (254340 KB) OKAY [ 7.116s]
Writing 'vendor_a' OKAY [ 0.965s]
Resizing 'vendor_dlkm_a' OKAY [ 0.004s]
Sending 'vendor_dlkm_a' (39444 KB) OKAY [ 1.102s]
Writing 'vendor_dlkm_a' OKAY [ 0.196s]
Rebooting OKAY [ 0.001s]
Finished. Total time: 122.552s
tibl37 said:
Not sure.
Here is the last fastboot log:
Bash:
Setting current slot to 'a' OKAY [ 0.072s]
Sending 'boot_a' (65536 KB) OKAY [ 1.749s]
Writing 'boot_a' OKAY [ 0.249s]
Sending 'dtbo_a' (16384 KB) OKAY [ 0.420s]
Writing 'dtbo_a' OKAY [ 0.063s]
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.026s]
Writing 'pvmfw_a' OKAY [ 0.007s]
Sending 'vbmeta_a' (8 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.002s]
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_a' OKAY [ 0.002s]
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_vendor_a' OKAY [ 0.002s]
Sending 'vendor_boot_a' (65536 KB) OKAY [ 1.648s]
Writing 'vendor_boot_a' OKAY [ 0.244s]
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.024s]
Resizing 'product_a' OKAY [ 0.003s]
Resizing 'system_a' OKAY [ 0.003s]
Resizing 'system_ext_a' OKAY [ 0.002s]
Resizing 'system_b' OKAY [ 0.002s]
Resizing 'vendor_a' OKAY [ 0.002s]
Resizing 'vendor_dlkm_a' OKAY [ 0.002s]
Resizing 'vendor_b' OKAY [ 0.002s]
Invalid sparse file format at header magic
Resizing 'product_a' OKAY [ 0.005s]
Sending sparse 'product_a' 1/5 (262120 KB) OKAY [ 7.131s]
Writing 'product_a' OKAY [ 1.034s]
Sending sparse 'product_a' 2/5 (262120 KB) OKAY [ 7.232s]
Writing 'product_a' OKAY [ 1.023s]
Sending sparse 'product_a' 3/5 (262120 KB) OKAY [ 7.282s]
Writing 'product_a' OKAY [ 1.095s]
Sending sparse 'product_a' 4/5 (262128 KB) OKAY [ 7.214s]
Writing 'product_a' OKAY [ 1.017s]
Sending sparse 'product_a' 5/5 (207840 KB) OKAY [ 5.494s]
Writing 'product_a' OKAY [ 0.865s]
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.004s]
Sending sparse 'system_a' 1/4 (262112 KB) OKAY [ 7.134s]
Writing 'system_a' OKAY [ 1.031s]
Sending sparse 'system_a' 2/4 (262120 KB) OKAY [ 7.087s]
Writing 'system_a' OKAY [ 1.089s]
Sending sparse 'system_a' 3/4 (262140 KB) OKAY [ 7.302s]
Writing 'system_a' OKAY [ 1.002s]
Sending sparse 'system_a' 4/4 (104872 KB) OKAY [ 2.835s]
Writing 'system_a' OKAY [ 0.501s]
Invalid sparse file format at header magic
Resizing 'system_ext_a' OKAY [ 0.004s]
Sending sparse 'system_ext_a' 1/2 (262124 KB) OKAY [ 7.442s]
Writing 'system_ext_a' OKAY [ 1.075s]
Sending sparse 'system_ext_a' 2/2 (89968 KB) OKAY [ 2.581s]
Writing 'system_ext_a' OKAY [ 0.357s]
Resizing 'system_b' OKAY [ 0.003s]
Sending 'system_b' (340 KB) OKAY [ 0.010s]
Writing 'system_b' OKAY [ 0.038s]
Invalid sparse file format at header magic
Resizing 'vendor_a' OKAY [ 0.005s]
Sending sparse 'vendor_a' 1/2 (262116 KB) OKAY [ 7.207s]
Writing 'vendor_a' OKAY [ 1.103s]
Sending sparse 'vendor_a' 2/2 (254340 KB) OKAY [ 7.116s]
Writing 'vendor_a' OKAY [ 0.965s]
Resizing 'vendor_dlkm_a' OKAY [ 0.004s]
Sending 'vendor_dlkm_a' (39444 KB) OKAY [ 1.102s]
Writing 'vendor_dlkm_a' OKAY [ 0.196s]
Rebooting OKAY [ 0.001s]
Finished. Total time: 122.552s
Click to expand...
Click to collapse
After initially flashing or updating to A13, whether it be a custom rom or stock firmware, did you ever flash an A13 build to the opposite (inactive) slot? Or flash the A13 bootloader to the opposite slot? Or did you ever take an OTA after updating to A13, resulting in A13 being put on the opposite slot? If not, then you likely still had the A12 bootloader on your opposite (inactive) slot.
Once updating to A13, the A13 bootloader needs to be flashed to both slots to avoid potentially bricking your device due to the new ARB. Your symptoms sound exactly the same as when users have bricked their devices because of this. They only had the A13 bootloader on one slot, got into a bootloop therefore causing the device to revert to the opposite slot which still had the A12 bootloader on it and thus bricking your device.
Android 13's anti-rollback protection has already bricked at least one Pixel 6
Some Pixel 6 users running Android 13 are stuck between a rock and a hard place with Google's anti-rollback protection.
www.androidpolice.com
Lughnasadh said:
After initially flashing or updating to A13, whether it be a custom rom or stock firmware, did you ever flash an A13 build to the opposite (inactive) slot? Or flash the A13 bootloader to the opposite slot? Or did you ever take an OTA after updating to A13, resulting in A13 being put on the opposite slot? If not, then you likely still had the A12 bootloader on your opposite (inactive) slot.
Once updating to A13, the A13 bootloader needs to be flashed to both slots to avoid potentially bricking your device due to the new ARB. Your symptoms sound exactly the same as when users have bricked their devices because of this. They only had the A13 bootloader on one slot, got into a bootloop therefore causing the device to revert to the opposite slot which still had the A12 bootloader on it and thus bricking your device.
Click to expand...
Click to collapse
I've probably upgraded to A13 OTA (not sure, because I had multiple Pixels and not sure if this one was updated OTA or by flashing with fastboot), but I'm sure that I didn't flash slot b manually.
tibl37 said:
I've probably upgraded to A13 OTA (not sure, because I had multiple Pixels and not sure if this one was updated OTA or by flashing with fastboot), but I'm sure that I didn't flash slot b manually.
Click to expand...
Click to collapse
If you didn't flash A13 to slot b manually, and you didn't take an OTA after initially updating to A13, then the likely scenario is that you bricked your device due to the anti-rollback protections implemented in the A13 bootloader because you still had the A12 bootloader (and firmware) on slot b.
All I can say is that your symptoms sound exactly like what happens when people brick their devices because of this. They get into a bootloop, phone turns off, can't turn it back on, buttons do nothing and charging does nothing. It's basically unresponsive and when connecting to the computer there might be a very short recognition, but that's it. They can't get into fastboot and the computer basically doesn't recognize the phone.
If this is indeed the case, from what I've observed, Google has been very good at replacing users devices when they have bricked their devices due to this.
@Lughnasadh I appreciate your time and effort in explaining the reason for boot failure to all of those who are experiencing hardbricks on their devices.
I'm really close to getting a good fix for our phone and probably going to open a combined forum for a combined reference on restoring the P6, P6P, P7, and P7P devices from a hard brick.
It's mainly related to a corruption of the correct memory address for bl1 resulting in the internal SOC requesting a new init_boot. If anyone can retrieve the header information for that file and possible a sparce layout for it(from any of the 4 devices) then I'll have a solution for restoring the phone for Windows, Unix, Linux, Android, and Darwin/MacOS users alike.
I bricked my P6a...well actually google took that HUGE liberty themselves! Compromised bootloader or not, I paid CASH in full for my phone. Effectively breaking my phone constitutes destruction of personal property....at $450 value, it's $50 short of being a felony iirc! Anyways...op it does sound like a 'e-fuse=blown' aka ARB brick. My was repaired under warranty but arrived back with a replaced screen w/ that peel-off screen protector and an unconnected fingerprint scanner! I was by then (15 days later) I was livid cuz my phone WAS in flawless condition. After raising all hell they broke down and sent me a NEW replacement, lol. So if ur not under warranty, take it to a local repair shop...you'll be glad u did. U can learn more about the infamous ARB 'e-fuse' in the 6a section's warning announcement post thread fwiw.
NonStickAtom785 said:
@Lughnasadh I appreciate your time and effort in explaining the reason for boot failure to all of those who are experiencing hardbricks on their devices.
I'm really close to getting a good fix for our phone and probably going to open a combined forum for a combined reference on restoring the P6, P6P, P7, and P7P devices from a hard brick.
It's mainly related to a corruption of the correct memory address for bl1 resulting in the internal SOC requesting a new init_boot. If anyone can retrieve the header information for that file and possible a sparce layout for it(from any of the 4 devices) then I'll have a solution for restoring the phone for Windows, Unix, Linux, Android, and Darwin/MacOS users alike.
Click to expand...
Click to collapse
What tools would be needed for that? I'm willing to help also even though my device isn't bricked.
I use a 6a so I sadly might not be of any use
I also have two Pixel 6 devices, one is bricked, another one is good, so if I can help somehow, ping me.
tibl37 said:
I also have two Pixel 6 devices, one is bricked, another one is good, so if I can help somehow, ping me.
Click to expand...
Click to collapse
It'd be bice if you could access the proprietary files on device. The soc uses exynos bootrom
Plz if you ever manage to get it fixed tag me. My pixel 6 is just catching dust here and I'm feeling really bad. You'd be an absolute life saver if you could find a solution.