Quote:
Originally Posted by Renate
Hey! How about checking out the EDL loaders for me, please?
|
I will when I can get out of the bootloop.
Quote:
Originally Posted by Renate
The original included 76 MB of zeroes. But watch out for the AVB0 footer, which may or may not be important. You can use my imgutil.exe /v to see structure/padding of an image.?
|
This is the output so there is 76MB of zeroes indeed.
Code:
imgutil.exe /v .\15.recovery_a.img
Header2: 1,660 (0000067c)
Kernel: 15,259,279 (00e8d68f) 00001000
Ramdisk: 8,340,618 (007f448a) 00e8f000
Recovery: 94,979 (00017303) 01684000
DTB: 290,066 (00046d12) 0169c000
Signature: 640 (00000280) 016e3000
Padding: 76,660,736 (0491c000) 016e4000
Command: console=ttyMSM0,115200n8 earlycon=msm_geni_serial,0x4a90000 androidboot.hardware=qcom androidboot.console=ttyMSM0 androidboot.memcg=1 lpm_levels.sleep_disabled=1 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 service_locator.enable=1 swiotlb=2048 loop.max_part=7 buildvariant=user
I can boot into recovery and boot fastboot from there. I tried flashing the stock boot and recovery images but the device keeps bootlooping. (Factory reset in recovery doesn't work either)
Both 'fastboot reboot-edl' and 'fastboot oem edl' return:
Code:
...
FAILED (remote: unknown command)
finished. total time: 0.004s
I extracted the 'mmcblk0.bin' it contains there images.
I guess I could flash them all through 'fastboot flashall' and hope it solves the bootloop.
Code:
0.xbl_a.img
1.xbl_b.img
10.boot_a.img
11.boot_b.img
12.super.img
13.vbmeta_system_a.img
14.vbmeta_system_b.img
15.recovery_a.img
16.recovery_b.img
17.keymaster_a.img
18.keymaster_b.img
19.mdtpsecapp_a.img
2.xbl_config_a.img
20.mdtpsecapp_b.img
21.mdtp_a.img
22.mdtp_b.img
23.modem_a.img
24.modem_b.img
25.dsp_a.img
26.dsp_b.img
27.abl_a.img
28.abl_b.img
29.ddr.img
3.xbl_config_b.img
30.bluetooth_a.img
31.bluetooth_b.img
32.ssd.img
33.dtbo_a.img
34.dtbo_b.img
35.imagefv_a.img
36.imagefv_b.img
37.uefisecapp_a.img
38.uefisecapp_b.img
39.persist.img
4.tz_a.img
40.metadata.img
41.misc.img
42.keystore.img
43.devcfg_a.img
44.devcfg_b.img
45.featenabler_a.img
46.featenabler_b.img
47.qupfw_a.img
48.qupfw_b.img
49.frp.img
5.tz_b.img
50.rawdump.img
51.devinfo.img
52.dip.img
53.apdp.img
54.spunvm.img
55.splash.img
56.limits.img
57.toolsfv.img
58.logfs.img
59.cateloader.img
6.rpm_a.img
60.logdump.img
61.vbmeta_a.img
62.vbmeta_b.img
63.storsec.img
64.multiimgoem_a.img
65.multiimgoem_b.img
66.multiimgqti.img
67.secdata.img
68.catefv.img
69.catecontentfv.img
7.rpm_b.img
70.uefivarstore.img
71.modemst1.img
72.modemst2.img
73.fsg.img
74.fsc.img
75.onyxconfig.img
76.userdata.img
8.hyp_a.img
9.hyp_b.img
Another option would be to modify the recovery so that I can boot it and have ADB from there, then reboot into EDL. Worst case I would have to open the device, in that case I can also take a picture of the CPU.
I guess there reed-switches are good too?
Amazon