So i've tried pretty much every tutorial out there and tried baking my phone and hitting it with a heat gun, 4core boot img,
my bootloader is unlocked and im able to flash any factory image onto the device but the outcome is the same where its stuck on the google screen.
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.107s]
writing 'bootloader'...
OKAY [ 0.203s]
finished. total time: 0.310s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.031s
< waiting for any device >
target reported max download size of 494927872 bytes
sending 'radio' (48472 KB)...
OKAY [ 1.156s]
writing 'radio'...
OKAY [ 2.156s]
finished. total time: 3.312s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (11 MB) to disk... took 0.063s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (12 MB) to disk... took 0.047s
archive does not contain 'recovery.sig'
extracting system.img (1923 MB) to disk... took 14.723s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (180 MB) to disk... took 1.453s
archive does not contain 'vendor.sig'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6694270 4k blocks and 1676080 inodes
Filesystem UUID: 15015e2a-3b5f-11e8-a195-95614c87b792
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
wiping cache...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 25600 4k blocks and 25600 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: angler-02.45
Baseband Version.....: angler-02.50
Serial Number........: 84B5T15C05003502
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.016s]
sending 'boot' (12045 KB)...
OKAY [ 0.297s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (12981 KB)...
OKAY [ 0.297s]
writing 'recovery'...
OKAY [ 0.203s]
erasing 'system'...
OKAY [ 0.406s]
sending sparse 'system' 1/5 (463062 KB)...
OKAY [ 10.660s]
writing 'system' 1/5...
OKAY [ 6.468s]
sending sparse 'system' 2/5 (466961 KB)...
OKAY [ 10.882s]
writing 'system' 2/5...
OKAY [ 6.759s]
sending sparse 'system' 3/5 (479253 KB)...
OKAY [ 11.297s]
writing 'system' 3/5...
OKAY [ 7.418s]
sending sparse 'system' 4/5 (481623 KB)...
OKAY [ 11.191s]
writing 'system' 4/5...
OKAY [ 6.764s]
sending sparse 'system' 5/5 (79148 KB)...
OKAY [ 1.902s]
writing 'system' 5/5...
OKAY [ 1.134s]
sending 'vendor' (185129 KB)...
OKAY [ 4.012s]
writing 'vendor'...
OKAY [ 2.973s]
erasing 'userdata'...
OKAY [ 0.313s]
sending 'userdata' (4412 KB)...
OKAY [ 0.141s]
writing 'userdata'...
OKAY [ 0.094s]
erasing 'cache'...
OKAY [ 0.031s]
sending 'cache' (96 KB)...
OKAY [ 0.016s]
writing 'cache'...
OKAY [ 0.016s]
rebooting...
finished. total time: 84.571s
Press any key to exit...
fastboot getvar all
(bootloader) version:0.01
(bootloader) unlocked:yes
(bootloader) hardware-revision:ANGLER-VN2
(bootloader) version-baseband:angler-02.50
(bootloader) version-bootloader:angler-02.45
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1d800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x66257ee00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) serialno:84B5T15C05003502
(bootloader) kernel:lk
(bootloader) product:angler
all:
finished. total time: 0.187s
any suggestions would be appreciated.
onikii said:
So i've tried pretty much every tutorial out there and tried baking my phone and hitting it with a heat gun, 4core boot img,
my bootloader is unlocked and im able to flash any factory image onto the device but the outcome is the same where its stuck on the google screen.
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.107s]
writing 'bootloader'...
OKAY [ 0.203s]
finished. total time: 0.310s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.031s
< waiting for any device >
target reported max download size of 494927872 bytes
sending 'radio' (48472 KB)...
OKAY [ 1.156s]
writing 'radio'...
OKAY [ 2.156s]
finished. total time: 3.312s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (11 MB) to disk... took 0.063s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (12 MB) to disk... took 0.047s
archive does not contain 'recovery.sig'
extracting system.img (1923 MB) to disk... took 14.723s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (180 MB) to disk... took 1.453s
archive does not contain 'vendor.sig'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6694270 4k blocks and 1676080 inodes
Filesystem UUID: 15015e2a-3b5f-11e8-a195-95614c87b792
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
wiping cache...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 25600 4k blocks and 25600 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: angler-02.45
Baseband Version.....: angler-02.50
Serial Number........: 84B5T15C05003502
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.016s]
sending 'boot' (12045 KB)...
OKAY [ 0.297s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (12981 KB)...
OKAY [ 0.297s]
writing 'recovery'...
OKAY [ 0.203s]
erasing 'system'...
OKAY [ 0.406s]
sending sparse 'system' 1/5 (463062 KB)...
OKAY [ 10.660s]
writing 'system' 1/5...
OKAY [ 6.468s]
sending sparse 'system' 2/5 (466961 KB)...
OKAY [ 10.882s]
writing 'system' 2/5...
OKAY [ 6.759s]
sending sparse 'system' 3/5 (479253 KB)...
OKAY [ 11.297s]
writing 'system' 3/5...
OKAY [ 7.418s]
sending sparse 'system' 4/5 (481623 KB)...
OKAY [ 11.191s]
writing 'system' 4/5...
OKAY [ 6.764s]
sending sparse 'system' 5/5 (79148 KB)...
OKAY [ 1.902s]
writing 'system' 5/5...
OKAY [ 1.134s]
sending 'vendor' (185129 KB)...
OKAY [ 4.012s]
writing 'vendor'...
OKAY [ 2.973s]
erasing 'userdata'...
OKAY [ 0.313s]
sending 'userdata' (4412 KB)...
OKAY [ 0.141s]
writing 'userdata'...
OKAY [ 0.094s]
erasing 'cache'...
OKAY [ 0.031s]
sending 'cache' (96 KB)...
OKAY [ 0.016s]
writing 'cache'...
OKAY [ 0.016s]
rebooting...
finished. total time: 84.571s
Press any key to exit...
fastboot getvar all
(bootloader) version:0.01
(bootloader) unlocked:yes
(bootloader) hardware-revision:ANGLER-VN2
(bootloader) version-baseband:angler-02.50
(bootloader) version-bootloader:angler-02.45
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1d800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x66257ee00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) serialno:84B5T15C05003502
(bootloader) kernel:lk
(bootloader) product:angler
all:
finished. total time: 0.187s
any suggestions would be appreciated.
Click to expand...
Click to collapse
Did you flash the special kernel that shuts off half of the CPU cores. If you were bootloop was because of the hardware issue then that is your only fix
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Did you flash the special kernel that shuts off half of the CPU cores. If you were bootloop was because of the hardware issue then that is your only fix
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I flashed 7.1.2 angler-n2g48b factory image to the nexus then I flashed the 4 core boot img fix along with twrp 4 core as well.
I'm unable to get into recovery and the boot fix did not work as its still stuck at the google screen for the last 2 hours.
onikii said:
I flashed 7.1.2 angler-n2g48b factory image to the nexus then I flashed the 4 core boot img fix along with twrp 4 core as well.
I'm unable to get into recovery and the boot fix did not work as its still stuck at the google screen for the last 2 hours.
Click to expand...
Click to collapse
I am having the same issues and also tried the steps in this post with no luck.
https://forum.xda-developers.com/showpost.php?p=75774448&postcount=2289
Related
Hello
My terminal only works with 4.2.2, will not start, I've tried everything and nothing, it only works with 4.2.2.
4.4. Logs
First attempt - Stuck
C:\A44>fastboot-toolkit devices
0488e8040e4c64aa fastboot
C:\A44>fastboot-toolkit oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.004s
C:\A44>fastboot-toolkit reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
C:\A44>fastboot-toolkit erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.024s]
finished. total time: 0.027s
C:\A44>fastboot-toolkit erase recovery
erasing 'recovery'...
OKAY [ 0.006s]
finished. total time: 0.009s
C:\A44>fastboot-toolkit erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.029s]
finished. total time: 0.030s
C:\A44>fastboot-toolkit flash bootloader bootloader-mako-makoz20
sending 'bootloader' (2203 KB)...
OKAY [ 0.144s]
writing 'bootloader'...
OKAY [ 0.335s]
finished. total time: 0.489s
C:\A44>fastboot-toolkit reboot-bootloader
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
C:\A44>fastboot-toolkit flash radio radio-mako-m9615a-cefwmazm-2
sending 'radio' (45537 KB)...
OKAY [ 1.467s]
writing 'radio'...
OKAY [ 2.540s]
finished. total time: 4.018s
C:\A44>fastboot-toolkit reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.013s
C:\A44>fastboot-toolkit -w update image-occam-krt16o.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.97
Serial Number........: 0488e8040e4c64aa
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (6336 KB)...
OKAY [ 0.208s]
writing 'boot'...
OKAY [ 0.341s]
sending 'recovery' (6884 KB)...
OKAY [ 0.232s]
writing 'recovery'...
OKAY [ 0.397s]
erasing 'system'...
OKAY [ 0.045s]
sending 'system' (700500 KB)...
OKAY [ 23.810s]
writing 'system'...
OKAY [ 40.364s]
erasing 'userdata'...
OKAY [ 6.720s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 6189744128
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 23612
Label:
Blocks: 1511168
Block groups: 47
Reserved block group size: 375
Created filesystem with 11/378256 inodes and 50366/1511168 block
sending 'userdata' (98413 KB)...
writing 'userdata'...
OKAY [ 30.821s]
erasing 'cache'...
OKAY [ 0.028s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 1.045s]
rebooting...
finished. total time: 104.093s
Click to expand...
Click to collapse
Second attempt - Stuck
C:\A44>fastboot-toolkit devices
0488e8040e4c64aa fastboot
C:\A44>fastboot-toolkit oem unlock
...
OKAY [ 12.595s]
finished. total time: 12.596s
C:\A44>fastboot-toolkit reboot-bootloader
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
C:\A44>fastboot-toolkit erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\A44>fastboot-toolkit erase recovery
erasing 'recovery'...
OKAY [ 0.017s]
finished. total time: 0.018s
C:\A44>fastboot-toolkit erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.675s]
finished. total time: 0.680s
C:\A44>fastboot-toolkit flash bootloader bootloader-mako-makoz20i.img
sending 'bootloader' (2203 KB)...
OKAY [ 0.077s]
writing 'bootloader'...
OKAY [ 0.304s]
finished. total time: 0.391s
C:\A44>fastboot-toolkit reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.015s
C:\A44>fastboot-toolkit flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
sending 'radio' (45537 KB)...
OKAY [ 1.498s]
writing 'radio'...
OKAY [ 2.679s]
finished. total time: 4.184s
C:\A44>fastboot-toolkit reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.015s
C:\A44>fastboot-toolkit -w update image-occam-krt16o.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.97
Serial Number........: 0488e8040e4c64aa
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (6336 KB)...
OKAY [ 0.210s]
writing 'boot'...
OKAY [ 0.362s]
sending 'recovery' (6884 KB)...
OKAY [ 0.238s]
writing 'recovery'...
OKAY [ 0.380s]
erasing 'system'...
OKAY [ 0.042s]
sending 'system' (700500 KB)...
OKAY [ 23.502s]
writing 'system'...
OKAY [ 39.985s]
erasing 'userdata'...
OKAY [ 0.192s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 6189744128
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 23612
Label:
Blocks: 1511168
Block groups: 47
Reserved block group size: 375
Created filesystem with 11/378256 inodes and 50366/1511168 blocks
sending 'userdata' (98413 KB)...
writing 'userdata'...
OKAY [ 11.658s]
erasing 'cache'...
OKAY [ 0.028s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 1.035s]
rebooting...
finished. total time: 77.702s
Click to expand...
Click to collapse
4.2.2 Logs
Works OK
C:\A44>fastboot-toolkit devices
0488e8040e4c64aa fastboot
C:\A44>fastboot-toolkit oem unlock
...
OKAY [ 12.595s]
finished. total time: 12.596s
C:\A44>fastboot-toolkit reboot-bootloader
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
C:\A44>fastboot-toolkit erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\A44>fastboot-toolkit erase recovery
erasing 'recovery'...
OKAY [ 0.017s]
finished. total time: 0.018s
C:\A44>fastboot-toolkit erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.675s]
finished. total time: 0.680s
C:\A44>fastboot-toolkit flash bootloader bootloader-mako-makoz20i.img
sending 'bootloader' (2203 KB)...
OKAY [ 0.077s]
writing 'bootloader'...
OKAY [ 0.304s]
finished. total time: 0.391s
C:\A44>fastboot-toolkit reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.015s
C:\A44>fastboot-toolkit flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
sending 'radio' (45537 KB)...
OKAY [ 1.498s]
writing 'radio'...
OKAY [ 2.679s]
finished. total time: 4.184s
C:\A44>fastboot-toolkit reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.015s
C:\A44>fastboot-toolkit -w update image-occam-krt16o.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.97
Serial Number........: 0488e8040e4c64aa
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (6336 KB)...
OKAY [ 0.210s]
writing 'boot'...
OKAY [ 0.362s]
sending 'recovery' (6884 KB)...
OKAY [ 0.238s]
writing 'recovery'...
OKAY [ 0.380s]
erasing 'system'...
OKAY [ 0.042s]
sending 'system' (700500 KB)...
OKAY [ 23.502s]
writing 'system'...
OKAY [ 39.985s]
erasing 'userdata'...
OKAY [ 0.192s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 6189744128
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 23612
Label:
Blocks: 1511168
Block groups: 47
Reserved block group size: 375
Created filesystem with 11/378256 inodes and 50366/1511168 blocks
sending 'userdata' (98413 KB)...
writing 'userdata'...
OKAY [ 11.658s]
erasing 'cache'...
OKAY [ 0.028s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 1.035s]
rebooting...
finished. total time: 77.702s
C:\A44>cd\
C:\>cd a422
C:\A422>flash-all
sending 'bootloader' (2188 KB)...
OKAY [ 0.075s]
writing 'bootloader'...
OKAY [ 0.301s]
finished. total time: 0.382s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
< waiting for device >
sending 'radio' (54593 KB)...
OKAY [ 3.458s]
writing 'radio'...
OKAY [ 3.254s]
finished. total time: 6.717s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ10o
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.48
Serial Number........: 0488e8040e4c64aa
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.003s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (5898 KB)...
OKAY [ 0.373s]
writing 'boot'...
OKAY [ 0.359s]
sending 'recovery' (6398 KB)...
OKAY [ 0.404s]
writing 'recovery'...
OKAY [ 0.394s]
erasing 'system'...
OKAY [ 0.669s]
sending 'system' (523357 KB)...
OKAY [ 32.861s]
writing 'system'...
OKAY [ 33.697s]
erasing 'userdata'...
OKAY [ 0.388s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 6189744128
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 23612
Label:
Blocks: 1511168
Block groups: 47
Reserved block group size: 375
Created filesystem with 11/378256 inodes and 50366/1511168 blocks
sending 'userdata' (98413 KB)...
writing 'userdata'...
OKAY [ 14.253s]
erasing 'cache'...
OKAY [ 0.057s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 1.448s]
rebooting...
finished. total time: 84.965s
Press any key to exit...
Click to expand...
Click to collapse
Can you help me?
Thanks
wipe data/cache on stock recovery
Find the bug! Is the radio file!
4.2.2 - Works OK
4.3 with 4.2 Radio - Works OK
4.4 with 4.2 Radio - Stuck in the X logo
kindly follow this method ull hav no problem i got stuck on flashing factory image of 4.4 through fastboot. then i used this method n it worked try out ur self too i made the video
http://forum.xda-developers.com/showthread.php?t=2531374
Sent from my Nexus 4 using xda app-developers app
@amartinpascual OP next time posting results of a large text amount try using the hide function so to not take up so much space on a post. Its quite useful
Hmmy 4444 said:
kindly follow this method ull hav no problem i got stuck on flashing factory image of 4.4 through fastboot. then i used this method n it worked try out ur self too i made the video
http://forum.xda-developers.com/showthread.php?t=2531374
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Don´t works, stuck on logo again!
amartinpascual said:
Don´t works, stuck on logo again!
Click to expand...
Click to collapse
Hi i have the same situatiom with my nexus 4. Firmware 4.2.2 works good. 4.3 works only with radio 48, 4.4 is not working. I tried to install every radio with this 4.4, 48, 84, and official radio from 4.4,but every try finally is bootloop. Wtf?
Same problem here. Exactly same problem!!!!. Will we live in 4.3 or 4.2.2 forever ?
WTF!
I dont know dude. I think there is a lot nexuses with the same problem. I have crashed audio output, maybe its reason?
same situation..
?
Do you have crash audio out?
The Speaker works, the headphones jack don´t works
Mi audio jack works fine
.
@up2
Do its exactly the same like in my nexus. Maybe all problems are made by this crashed audio jack.
amartinpascual said:
Don´t works, stuck on logo again!
Click to expand...
Click to collapse
Re download the factory image, n try i again n connect ur phone wth ur pc, n keep ur phone in bootloader mode
Hmmy 4444 said:
Re download the factory image, n try i again n connect ur phone wth ur pc, n keep ur phone in bootloader mode
Click to expand...
Click to collapse
Re download the factory image and Try again - Don´t Works
Close and open again the bootloader - Don´t Works
Only works with 4.22. and 4.3 with Radio .48
opssemnik said:
wipe data/cache on stock recovery
Click to expand...
Click to collapse
This!
.
Amartin we have exactly the same situation. I think everything is because of crashed audio jack.
Mi jack is fine and I have the same problem
Rumors, Google Prepairs a 4.4.1 OTA update, have detected the problem?
I went to restore the Recovery OS Image so i can update to the latest OS version (i couldn't update since I was rooted). Everything went well until i was flashing the system.img file.
target reported max download s
erasing 'system'...
OKAY [ 0.758s]
sending sparse 'system' (62437
OKAY [ 1.775s]
writing 'system'...
OKAY [ 2.737s]
sending sparse 'system' (62993
OKAY [ 1.812s]
writing 'system'...
OKAY [ 2.660s]
sending sparse 'system' (65443
OKAY [ 1.996s]
writing 'system'...
OKAY [ 3.211s]
sending sparse 'system' (65512
OKAY [ 1.854s]
writing 'system'...
OKAY [ 2.726s]
sending sparse 'system' (65532
OKAY [ 1.869s]
writing 'system'...
OKAY [ 2.654s]
sending sparse 'system' (63893
OKAY [ 1.814s]
writing 'system'...
OKAY [ 2.712s]
sending sparse 'system' (58260
OKAY [ 1.637s]
writing 'system'...
OKAY [ 2.377s]
sending sparse 'system' (59088
OKAY [ 1.683s]
writing 'system'...
OKAY [ 2.434s]
sending sparse 'system' (65533
OKAY [ 1.872s]
writing 'system'...
OKAY [ 2.756s]
sending sparse 'system' (64176
OKAY [ 1.818s]
writing 'system'...
OKAY [ 2.560s]
sending sparse 'system' (58956
OKAY [ 1.674s]
writing 'system'...
OKAY [ 2.405s]
sending sparse 'system' (65532
OKAY [ 1.833s]
writing 'system'...
OKAY [ 2.613s]
sending sparse 'system' (60898
OKAY [ 1.752s]
writing 'system'...
OKAY [ 2.700s]
sending sparse 'system' (62455
OKAY [ 1.814s]
writing 'system'...
OKAY [ 2.767s]
sending sparse 'system' (65532
OKAY [ 1.865s]
writing 'system'...
OKAY [ 2.727s]
sending sparse 'system' (65532
OKAY [ 1.858s]
writing 'system'...
OKAY [ 2.699s]
sending sparse 'system' (61848
OKAY [ 1.764s]
writing 'system'...
OKAY [ 2.664s]
sending sparse 'system' (61428
OKAY [ 1.746s]
writing 'system'...
OKAY [ 2.472s]
sending sparse 'system' (65532
OKAY [ 1.853s]
writing 'system'...
OKAY [ 2.764s]
sending sparse 'system' (65533
OKAY [ 1.881s]
writing 'system'...
OKAY [ 2.707s]
sending sparse 'system' (63217
OKAY [ 1.817s]
writing 'system'...
OKAY [ 2.680s]
sending sparse 'system' (65533
OKAY [ 1.872s]
writing 'system'...
OKAY [ 2.786s]
sending sparse 'system' (65053
OKAY [ 1.914s]
writing 'system'...
OKAY [ 2.983s]
sending sparse 'system' (65538
FAILED (remote: data too large
finished. total time: 104.455s
How can this fail if it's an official method? Anybody have any idea?
I managed to get my device back to 5.1 by installing with twrp the zip from this post https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062
the script will have errors but it will boot the system afterwards. It also fails in updating to 5.2.
same issue here nvidia is really pissing me off
You need to limit the chunk size like so:
Code:
fastboot -S 50M flash system system.img
rodalpho said:
You need to limit the chunk size like so:
Code:
fastboot -S 50M flash system system.img
Click to expand...
Click to collapse
For me that works by limiting chunk size. But after flashing and reboot I get "No command" or gets stuck on Logo Screen NVIDIA
Did you flash vendor.img afterwards? I try re-flashing the entire series from flash-all.sh in sequence. To get back to fastboot mode, try Nvidia's hardware instructions here.
http://developer.download.nvidia.co...ATV_2017/5.0.0/HowTo-Flash-Recovery-Image.txt
pendragon666 said:
I went to restore the Recovery OS Image so i can update to the latest OS version (i couldn't update since I was rooted). Everything went well until i was flashing the system.img file.
target reported max download s
erasing 'system'...
OKAY [ 0.758s]
sending sparse 'system' (62437
OKAY [ 1.775s]
writing 'system'...
OKAY [ 2.737s]
sending sparse 'system' (62993
OKAY [ 1.812s]
writing 'system'...
OKAY [ 2.660s]
sending sparse 'system' (65443
OKAY [ 1.996s]
writing 'system'...
OKAY [ 3.211s]
sending sparse 'system' (65512
OKAY [ 1.854s]
writing 'system'...
OKAY [ 2.726s]
sending sparse 'system' (65532
OKAY [ 1.869s]
writing 'system'...
OKAY [ 2.654s]
sending sparse 'system' (63893
OKAY [ 1.814s]
writing 'system'...
OKAY [ 2.712s]
sending sparse 'system' (58260
OKAY [ 1.637s]
writing 'system'...
OKAY [ 2.377s]
sending sparse 'system' (59088
OKAY [ 1.683s]
writing 'system'...
OKAY [ 2.434s]
sending sparse 'system' (65533
OKAY [ 1.872s]
writing 'system'...
OKAY [ 2.756s]
sending sparse 'system' (64176
OKAY [ 1.818s]
writing 'system'...
OKAY [ 2.560s]
sending sparse 'system' (58956
OKAY [ 1.674s]
writing 'system'...
OKAY [ 2.405s]
sending sparse 'system' (65532
OKAY [ 1.833s]
writing 'system'...
OKAY [ 2.613s]
sending sparse 'system' (60898
OKAY [ 1.752s]
writing 'system'...
OKAY [ 2.700s]
sending sparse 'system' (62455
OKAY [ 1.814s]
writing 'system'...
OKAY [ 2.767s]
sending sparse 'system' (65532
OKAY [ 1.865s]
writing 'system'...
OKAY [ 2.727s]
sending sparse 'system' (65532
OKAY [ 1.858s]
writing 'system'...
OKAY [ 2.699s]
sending sparse 'system' (61848
OKAY [ 1.764s]
writing 'system'...
OKAY [ 2.664s]
sending sparse 'system' (61428
OKAY [ 1.746s]
writing 'system'...
OKAY [ 2.472s]
sending sparse 'system' (65532
OKAY [ 1.853s]
writing 'system'...
OKAY [ 2.764s]
sending sparse 'system' (65533
OKAY [ 1.881s]
writing 'system'...
OKAY [ 2.707s]
sending sparse 'system' (63217
OKAY [ 1.817s]
writing 'system'...
OKAY [ 2.680s]
sending sparse 'system' (65533
OKAY [ 1.872s]
writing 'system'...
OKAY [ 2.786s]
sending sparse 'system' (65053
OKAY [ 1.914s]
writing 'system'...
OKAY [ 2.983s]
sending sparse 'system' (65538
FAILED (remote: data too large
finished. total time: 104.455s
How can this fail if it's an official method? Anybody have any idea?
I managed to get my device back to 5.1 by installing with twrp the zip from this post https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062
the script will have errors but it will boot the system afterwards. It also fails in updating to 5.2.
Click to expand...
Click to collapse
I would advise you to quickly download DRM Info from the PlayStore, If you can, and verify you still have Widevine L1 Status. It might not be a big deal if you don't use Netflix, or Amazon. But other outfits like NBC which is free, also use this to protect their Content, and will prevent you from viewing such if your not in compliance.
I know this as I myself got into the same but of trouble between Experience 3.x, and 5.x on my Pro. I managed to get a different Device, and have since made a backup of first few Partitions of my SSHD on my Shield to cover my ass in the eventual case that it should ever happen again.
Though I'm not sure how that's going to be relevant info for a 16Gb eMMC user though.
The flashing worked with chunk limiting.
I think my updating failed after i flashed that zip i mentioned in the first post because of wrong keys. When i flashed the update with twrp it said something along those lines and failed.
Everything back to normal now.
Thanks for the solution.
I had to sparse system and vendor images with -S 50M to get it to work.
Download: https://developer.android.com/preview/download.html
Credit to @skaforey for the scoop over at the Pixel2 XL forum, and at this point just about every other android tech site.
Interesting change to the navigation bar. Looks like they're trying to reduce the burn in problem people are getting.
Does this use visualcore
It keeps telling me I don't have any eligible devices.. as I type this on my fully stock Pixel 2.
Edit: I'm now able to enroll!
TLDR; Make sure you update your fastboot first!
I flashed the 8.1 beta using an old fastboot (that didn't know about slots) and now I'm stuck in the bootloader. I can't get android to boot, and I can't even get into the stock recovery or download options.
I've tried flashing the stock image several times, but that didn't do any good.
Any Help would be greatly appreciated!
Thanks!
pvillegeek said:
TLDR; Make sure you update your fastboot first!
I flashed the 8.1 beta using an old fastboot (that didn't know about slots) and now I'm stuck in the bootloader. I can't get android to boot, and I can't even get into the stock recovery or download options.
I've tried flashing the stock image several times, but that didn't do any good.
Any Help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Download the factory and flash-all.bat?
Chronzy said:
Download the factory and flash-all.bat?
Click to expand...
Click to collapse
I tried that. It appeared to flash correctly, but didn't help.
Code:
platform-tools>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.125s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00049000
(bootloader) Updating: cmnlib @0008D000 sz=00038000
(bootloader) Updating: devcfg @000C5000 sz=0000F000
(bootloader) Updating: hyp @000D4000 sz=00040000
(bootloader) Updating: keymaster @00114000 sz=00046000
(bootloader) Updating: lockbooter @0015A000 sz=00016000
(bootloader) Updating: pmic @00170000 sz=0000D000
(bootloader) Updating: rpm @0017D000 sz=0003A000
(bootloader) Updating: tz @001B7000 sz=001DB000
(bootloader) Updating: xbl @00392000 sz=003A2000
(bootloader) Updating: apdp @00734000 sz=00004000
(bootloader) Updating: msadp @00738000 sz=00004000
(bootloader) Updating: hosd @0073C000 sz=01E31000
(bootloader) Updating: abl @0256D000 sz=00065000
OKAY [ 1.016s]
finished. total time: 1.141s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 0.172s]
writing 'radio_a'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.547s]
finished. total time: 0.734s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00122-1708311414
Serial Number........: FA79C1A05734
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.016s]
sending 'boot_a' (32768 KB)...
OKAY [ 0.109s]
writing 'boot_a'...
OKAY [ 0.297s]
erasing 'system_a'...
OKAY [ 0.188s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 2.219s]
writing 'system_a' 1/4...
OKAY [ 4.782s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 2.109s]
writing 'system_a' 2/4...
OKAY [ 4.813s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 2.219s]
writing 'system_a' 3/4...
OKAY [ 4.798s]
sending sparse 'system_a' 4/4 (322300 KB)...
OKAY [ 1.328s]
writing 'system_a' 4/4...
OKAY [ 2.954s]
erasing 'system_b'...
OKAY [ 0.203s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 2.188s]
writing 'system_b' 1/2...
OKAY [ 4.798s]
sending sparse 'system_b' 2/2 (80600 KB)...
OKAY [ 0.359s]
writing 'system_b' 2/2...
OKAY [ 0.750s]
erasing 'vendor_a'...
OKAY [ 0.188s]
sending 'vendor_a' (346964 KB)...
OKAY [ 1.062s]
writing 'vendor_a'...
OKAY [ 3.188s]
Setting current slot to 'a'...
OKAY [ 0.031s]
erasing 'userdata'...
OKAY [ 0.750s]
sending 'userdata' (140906 KB)...
OKAY [ 0.438s]
writing 'userdata'...
OKAY [ 1.516s]
rebooting...
finished. total time: 41.536s
Press any key to exit...
pvillegeek said:
I tried that. It appeared to flash correctly, but didn't help.
Click to expand...
Click to collapse
Read up over at the 2XL forum: https://forum.xda-developers.com/pixel-2-xl/how-to/8-1-developer-images-available-t3694556/page3
Some talk about having to extract and flash files individually. Maybe that'll help. I've had to do that on devices in the past.
dude, beware flashing this, thought I bricked my device, had to manually flash everything.... wtf google
I'm waiting for the OTA tomorrow. Looking forward to the colored nav bar and fading buttons! It's nice to see Google taking action on something rather than having to enable an accessibility service for a 3rd party app to color the navigation bar, and the fading buttons are a nice touch.
Chronzy said:
Read up over at the 2XL forum: https://forum.xda-developers.com/pixel-2-xl/how-to/8-1-developer-images-available-t3694556/page3
Some talk about having to extract and flash files individually. Maybe that'll help. I've had to do that on devices in the past.
Click to expand...
Click to collapse
Thanks, I tried that, but still no luck. I ended up contacting google support and they are sending a replacement.
pvillegeek said:
Thanks, I tried that, but still no luck. I ended up contacting google support and they are sending a replacement.
Click to expand...
Click to collapse
Wow, that's quite the hook up. Do you have the insurance?
Has anyone noticed a difference in the HDR+ processing speed or something like that? (preliminary Pixel core was enabled with this 8.1 DP1)
www.androidpolice.com/2017/10/26/an...ual-core-chip-now-enabled-developers-can-use/
Who's received the update via OTA after signing up for the beta? I'm still waiting here on my Pixel 2.
quakeaz said:
Who's received the update via OTA after signing up for the beta? I'm still waiting here on my Pixel 2.
Click to expand...
Click to collapse
Also waiting here.
pvillegeek said:
Thanks, I tried that, but still no luck. I ended up contacting google support and they are sending a replacement.
Click to expand...
Click to collapse
You fastboot flashing unlock_critcal? I doubt it's bricked.
Sent from my Nexus 6 using Tapatalk
quakeaz said:
Who's received the update via OTA after signing up for the beta? I'm still waiting here on my Pixel 2.
Click to expand...
Click to collapse
Still waiting...
The developer preview from Pixel 2 is at moment down, I think they make changes.
Gesendet von meinem Pixel 2 mit Tapatalk
How stable are the developer previews, in general?
cb474 said:
How stable are the developer previews, in general?
Click to expand...
Click to collapse
In general they are rather stable, but there are exceptions.
As to any particular phone, you can wait a couple of days and see if there are many reports of problems.
---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------
Does anyone have the direct link to the OTA they are pushing out?
See https://forum.xda-developers.com/showpost.php?p=74307421&postcount=88 for the link for the Pixel 2 XL.
I flashed the phone with fastboot with a non-branded STOCK ROM, file by file, when the phone was rebooted, it was branded TIM Italy, why?
Is it possible that fastboot, despite the video results, did not flasha anything?
I tried several ROMs without success.
Code:
D:\Cellulare\adb-and-fastboot>fastboot flash cust debrand\CUST.img
Sending 'cust' (134830 KB) OKAY [ 5.832s]
Writing 'cust' OKAY [ 3.059s]
Finished. Total time: 8.928s
D:\Cellulare\adb-and-fastboot>fastboot flash kernel debrand\KERNEL.img
Sending 'kernel' (45749 KB) OKAY [ 1.629s]
Writing 'kernel' OKAY [ 1.009s]
Finished. Total time: 2.676s
D:\Cellulare\adb-and-fastboot>fastboot flash ramdisk debrand\RAMDISK.img
Sending 'ramdisk' (11205 KB) OKAY [ 0.414s]
Writing 'ramdisk' OKAY [ 0.273s]
Finished. Total time: 0.726s
D:\Cellulare\adb-and-fastboot>fastboot flash recovery_ramdisk debrand\RECOVERY_RAMDIS.img
Sending 'recovery_ramdisk' (27893 KB) OKAY [ 0.998s]
Writing 'recovery_ramdisk' OKAY [ 0.630s]
Finished. Total time: 1.676s
D:\Cellulare\adb-and-fastboot>fastboot flash system debrand\SYSTEM.img
Sending sparse 'system' 1/6 (468550 KB) OKAY [ 19.835s]
Writing sparse 'system' 1/6 OKAY [ 12.017s]
Sending sparse 'system' 2/6 (513679 KB) OKAY [ 20.851s]
Writing sparse 'system' 2/6 OKAY [ 11.767s]
Sending sparse 'system' 3/6 (515737 KB) OKAY [ 20.873s]
Writing sparse 'system' 3/6 OKAY [ 12.012s]
Sending sparse 'system' 4/6 (517855 KB) OKAY [ 21.453s]
Writing sparse 'system' 4/6 OKAY [ 12.797s]
Sending sparse 'system' 5/6 (521377 KB) OKAY [ 21.275s]
Writing sparse 'system' 5/6 OKAY [ 11.808s]
Sending sparse 'system' 6/6 (57052 KB) OKAY [ 2.236s]
Writing sparse 'system' 6/6 OKAY [ 1.276s]
Finished. Total time: 222.547s
D:\Cellulare\adb-and-fastboot>fastboot reboot
Rebooting
Finished. Total time: 0.004s
D:\Cellulare\adb-and-fastboot>
Here is the sequence of commands:
C:\Users\blah\Desktop\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
PM1LHMA7blahblah unauthorized
C:\Users\blah\Desktop\platform-tools>adb devices
List of devices attached
PM1LHMA7blahblah device
C:\Users\blah\Desktop\platform-tools>adb reboot bootloader
C:\Users\blah\Desktop\platform-tools>fastboot devices
PM1LHMA7blahblah fastboot
C:\Users\blah\Desktop\platform-tools>fastboot getvar current-slot
current-slot: _a
Finished. Total time: 0.001s
C:\Users\blah\Desktop\platform-tools>fastboot flash vendor_a vendor-QQ1A.200105.088.img # OOPS i should have put b so i try to fix it in the next command
Sending 'vendor_a' (392296 KB) OKAY [ 9.211s]
Writing 'vendor_a' OKAY [ 2.446s]
Finished. Total time: 11.667s
C:\Users\blah\Desktop\platform-tools>fastboot flash vendor_b vendor-QQ1A.200105.088.img
Sending 'vendor_b' (392296 KB) OKAY [ 9.215s]
Writing 'vendor_b' OKAY [ 2.439s]
Finished. Total time: 11.661s
C:\Users\blah\Desktop\platform-tools>fastboot erase system_b
Erasing 'system_b' OKAY [104.577s]
Finished. Total time: 104.580s
C:\Users\blah\Desktop\platform-tools>fastboot flash system_b system.img
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/6 (523151 KB) OKAY [ 12.365s]
Writing 'system_b' OKAY [ 3.943s]
Sending sparse 'system_b' 2/6 (520769 KB) OKAY [ 12.262s]
Writing 'system_b' OKAY [ 3.271s]
Sending sparse 'system_b' 3/6 (523599 KB) OKAY [ 12.327s]
Writing 'system_b' OKAY [ 3.311s]
Sending sparse 'system_b' 4/6 (522306 KB) OKAY [ 12.262s]
Writing 'system_b' OKAY [ 3.563s]
Sending sparse 'system_b' 5/6 (503327 KB) OKAY [ 11.967s]
Writing 'system_b' OKAY [ 8.774s]
Sending sparse 'system_b' 6/6 (42300 KB) OKAY [ 1.068s]
Writing 'system_b' OKAY [ 0.311s]
Finished. Total time: 87.248s
C:\Users\blah\Desktop\platform-tools>fastboot flash boot_b unsigned-new.img
fastboot: error: Couldn't parse partition size '0x'.
C:\Users\blah\Desktop\platform-tools>fastboot flash boot_a unsigned-new.img
fastboot: error: Couldn't parse partition size '0x'.
C:\Users\blah\Desktop\platform-tools>fastboot flash:raw boot_b unsigned-new.img
Sending 'boot_b' (23864 KB) OKAY [ 0.634s]
Writing 'boot_b' OKAY [ 0.298s]
Finished. Total time: 0.958s
##FORGET TO USE COMMAND fastboot set_active a
C:\Users\blah\Desktop\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 54.443s]
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 26768215 4k blocks and 6692864 inodes
Filesystem UUID: blah
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (544 KB) OKAY [ 0.100s]
Writing 'userdata' OKAY [ 0.018s]
Finished. Total time: 54.827s
Now when i restart the phone it just stays on the screen with the essential logo and powered by android at the bottom; never gets to spinning circles. When I restart i can pause it from booting because the bootloader is unlocked, but adb cant find it because to do that i have to give it debug permissions, but no OS to boot to so i cant do that. Did i brick my phone?
If you can still get into the bootloader, its fixable. Just reflash stock
vsn4 said:
If you can still get into the bootloader, its fixable. Just reflash stock
Click to expand...
Click to collapse
When I reboot, it says press power to pause (the screen where it says g.co/ABH), but then eventually proceeds to boot by itself after a few seconds.
noideawtf said:
When I reboot, it says press power to pause (the screen where it says g.co/ABH), but then eventually proceeds to boot by itself after a few seconds.
Click to expand...
Click to collapse
It boots back into the screen with the logo and phrase powered by android and sits there. After it dissipated its power all night doing that, I was able to get the bootloader screen to appear (The word start in big green letters) this morning, but i selected start and now that screen refuses to show up again, so ill try draining it again i guess?
I drained it of power and as soon as i plugged it into a charger it turned on by itself and went into the bootloader unlike it was doing before. Was able to issue the command I missed earlier and now it loads right up.