device stuck in bootloop - ASUS ROG Phone II Questions & Answers

I have a problem with my rog phone 2, it's bootloop, I can't get into recovery, I flash RAW - QFIL - MI FLASH - all flash resource successfully, but the system doesn't update on the device.
found the problem of my phone - EMMC burned, it does not save the settingsfound the problem of my phone - EMMC burned, it does not save the settings flash rom
only the processor and the ram work
(bootloader) board_info: msmnile
(bootloader) mem_info: 8GB
(bootloader) cpu_freq: 2.96 GHz
(bootloader) product_name: ASUS_I001_1
(bootloader) product_locale: en-US
(bootloader) product_carrier: ASUS-ASUS_I001D-WW
(bootloader) csc_build_version: WW_ZS660KL-17.0240.2007.27-0
(bootloader) bt_mac: 04D9F5
(bootloader) wifi_mac: 04D9F56
(bootloader) imei: 3582971
(bootloader) imei2: 35829710
(bootloader) ssn: L2AIB600P0748FF
(bootloader) isn: MB1ZS660AG70HT
(bootloader) color: 1A
(bootloader) country: BR
(bootloader) client: ASUS

This happened to my phone now. Can anyone please help us fix this

Related

Turbo Stuck in BootLoop after replacing screen

So I dropped my Turbo and the screen shattered. I'd taken the Turbo apart before (replacing battery) so I am familiar with how to do it and what NOT to do. Note that this happened last week so the Turbo has been sitting in pieces without the battery attached to the motherboard.
Note: My Turbo is unlocked, rooted, with TWRP recovery and has Resurrection Remix custom ROM installed.
Ordered a new screen and digitizer; replaced it and put the Turbo back together. Powered it up and - woo hoo (I thought) - The Moto logo showed up fine on the new screen! Problem is, it boot loops constantly thru the Moto logo - can't get any further than that.
I can boot to my bootloader, which shows:
AF Fastboot Flast Mode (Secure)
...
...
Device is UNLOCKED. Status Code: 3
Software Status: Modified
Transfer Mode: USB Connected.
And ran mfastboot.exe getvar all which returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-70.8A
(bootloader) product: quark
(bootloader) board: quark
(bootloader) secure: yes
(bootloader) hwrev: 0x84A0
(bootloader) radio: 0x4
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 3072MB Samsung S8 SDRAM DIE=6Gb
(bootloader) cpu: APQ8084 ES1.1
(bootloader) serialno: xxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) cid: 0x0002
(bootloader) channelid: 0x00
(bootloader) uid: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 09-29-2014
(bootloader) sku: XT1254
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Apr 19 9:58:54 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/quark_verizon/quark:5.1/S
(bootloader) ro.build.fingerprint[1]: U4TL-44/44:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.21.44.quark_veriz
(bootloader) ro.build.version.full[1]: on.verizon.en.US
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.10.40-perf-g90ddf4a (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Sep 1 22:50:23 CDT
(bootloader) kernel.version[3]: 2015
(bootloader) sdi.git: git=MBM-NG-V70.8A-0-gf291c61
(bootloader) sbl1.git: git=MBM-NG-V70.8A-0-g60ea7e6
(bootloader) rpm.git: git=MBM-NG-V70.8A-0-g18b261e
(bootloader) tz.git: git=MBM-NG-V70.8A-0-gce6d7d0
(bootloader) aboot.git: git=MBM-NG-V70.8A-0-g021bfc8
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-type:sdi: raw
(bootloader) partition-type:sec: raw
(bootloader) partition-type:ddr: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:factorytune1: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:sbl1bak: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:mdm1m9kefs1: raw
(bootloader) partition-type:mdm1m9kefs2: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:mdm1hob: raw
(bootloader) partition-type:mdm1dhob: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-typeds: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:mdm1m9kefs3: raw
(bootloader) partition-type:mdm1m9kefsc: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:factorytune2: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x0000000008000000
(bootloader) partition-size:sbl1: 0x0000000000060000
(bootloader) partition-size:sdi: 0x000000000000e000
(bootloader) partition-size:sec: 0x0000000000004000
(bootloader) partition-size:ddr: 0x0000000000008000
(bootloader) partition-size:aboot: 0x0000000000100000
(bootloader) partition-size:rpm: 0x0000000000040000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:tz: 0x000000000007d000
(bootloader) partition-size:factorytune1: 0x0000000000300000
(bootloader) partition-sizeadA: 0x000000000010f000
(bootloader) partition-size:sbl1bak: 0x0000000000060000
(bootloader) partition-size:abootBackup: 0x0000000000100000
(bootloader) partition-size:rpmBackup: 0x0000000000040000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:tzBackup: 0x000000000007d000
(bootloader) partition-size:mdm1m9kefs1: 0x0000000000100000
(bootloader) partition-size:mdm1m9kefs2: 0x0000000000100000
(bootloader) partition-sizeadB: 0x000000000020f000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-sizeersist: 0x0000000002000000
(bootloader) partition-size:mdm1hob: 0x0000000000040000
(bootloader) partition-size:mdm1dhob: 0x0000000000008000
(bootloader) partition-size:sp: 0x0000000000100000
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-sizeds: 0x0000000000300000
(bootloader) partition-size:logo: 0x0000000000800000
(bootloader) partition-size:clogo: 0x0000000000b00000
(bootloader) partition-size:misc: 0x0000000000100000
(bootloader) partition-sizeadC: 0x0000000000198000
(bootloader) partition-size:mdm1m9kefs3: 0x00000000000c3000
(bootloader) partition-size:mdm1m9kefsc: 0x0000000000000400
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:recovery: 0x0000000001004000
(bootloader) partition-size:factorytune2: 0x0000000001008000
(bootloader) partition-size:cache: 0x0000000059af4000
(bootloader) partition-size:system: 0x00000000d3000000
(bootloader) partition-size:userdata: 0x0000000608be0000
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: vzw
all: listed above
finished. total time: 0.158s
I can boot fine into the bootloader, but that is all. Can't reboot into Recovery, and the ROM won't boot. Just boot loops constantly in the Moto Logo. I double checked all my connections and everything looks fine. I tried reflashing TWRP recovery (which said it worked) but that didn't help either.
Any ideas? Could leaving the motherboard unpowered for days have caused everything to be erased from ROM/RAM? If so, what do I do now? Am stumped, any ideas appreciated.
-Tom
Don't know about the pros, but I'd try flashing twrp via ADB while in bootloader. Once on, you can wipe stuff, and reflash your ROM from TWRP.
Sent from my XT1254 using Tapatalk
Einsteindks said:
Don't know about the pros, but I'd try flashing twrp via ADB while in bootloader. Once on, you can wipe stuff, and reflash your ROM from TWRP.
Click to expand...
Click to collapse
Thanks, but I did try that; adb said the flash worked, but it won't boot into recovery. Still bootloops at the logo.
OK I may post this question as a new post, but: To try to at least get a booting phone: Is there ANY stock ROM and Bootloader that I can flash that will still keep my phone UNLOCKED? I don't want to relock it and then have it locked forever (which I think the latest stock updates does),
SimpTheChimp said:
OK I may post this question as a new post, but: To try to at least get a booting phone: Is there ANY stock ROM and Bootloader that I can flash that will still keep my phone UNLOCKED? I don't want to relock it and then have it locked forever (which I think the latest stock updates does),
Click to expand...
Click to collapse
You can flash the latest firmware from Motorola and it won't lock your bootloader
I'll second that firmware flash. Bootloader doesn't get re-locked that way. Your TWRP file used may either have not been for quark phones, or was a corrupted file. I use version 3.1.0.0. Although the latest, and reported stable 'ver4' of that is out, 3.1.0.0 likes my Turbo.
Sent from my XT1254 using Tapatalk
I believe that if you can only get to the bootloader, you'd run fastboot commands not adb. Just want to make sure that's what you're​ doing.
Other than that, back up all the files you can get to through your PC and flash the stock image or run the Verizon repair assistant. Neither will relock your bootloader. You just get to start over from scratch, not necessarily a bad thing in situations like this.
Sent from my XT1254 using Tapatalk
SpyderPride said:
I believe that if you can only get to the bootloader, you'd run fastboot commands not adb. Just want to make sure that's what you're​ doing.
Other than that, back up all the files you can get to through your PC and flash the stock image or run the Verizon repair assistant. Neither will relock your bootloader. You just get to start over from scratch, not necessarily a bad thing in situations like this.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Spyder: Thanks, I did just that and it worked. Unfortunately, my new screen works but the digitizer doesn't. I.E. I can boot and see everything on the screen, but touching the screen yields nothing - can't scroll, can't select anything, can't even continue with the phone startup! I went through and double-checked all my connections and everything looks correct - just no digitizer.
Kinda strange that the screen works but the digitizer (touch portion) doesn't. Don't suppose you got any ideas on that?
You get the screen from a reputable seller? Did you do an all-in-one screen, or try to do an individual repair?
Sent from my XT1254 using Tapatalk
Einsteindks said:
You get the screen from a reputable seller? Did you do an all-in-one screen, or try to do an individual repair?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Yeah, the seller is an eBay 'company' but reputable (at least their rating is good); plus screen looked basically brand new when it arrived. It was screen+digitizer which I put on my old Turbo frame, reattached motherboard, battery, etc. Fairly experienced with taking the Turbo apart; have done so previously to install new battery.
Just strange that the screen works perfectly but no touch. I read somewhere else that sometimes pressing the top left corner of the screen (where it was mentioned that the digitizer exists) can possibly get it going - but not in my case. And as far as I can tell, there is only 1 connection of the screen to the motherboard, and I know that is connected properly.
So....
SimpTheChimp said:
Yeah, the seller is an eBay 'company' but reputable (at least their rating is good); plus screen looked basically brand new when it arrived. It was screen+digitizer which I put on my old Turbo frame, reattached motherboard, battery, etc. Fairly experienced with taking the Turbo apart; have done so previously to install new battery.
Just strange that the screen works perfectly but no touch. I read somewhere else that sometimes pressing the top left corner of the screen (where it was mentioned that the digitizer exists) can possibly get it going - but not in my case. And as far as I can tell, there is only 1 connection of the screen to the motherboard, and I know that is connected properly.
So....
Click to expand...
Click to collapse
Ribbon came not fully seated?
Sent from my DROID Turbo using Tapatalk
I have the same situation with my phone, is there any solution?

xt890: partition cid dead

Hello,
I still try to recover my motorola razer i XT890.
Now we will do it in a worse state, wrongly overwrote the cid partition
My phone was with bootloader unlocked but when I lost that partition
I'm blocked. It does not get to start neither in normal mode nor in bp tool always it is marked in the logo of intel, it does not have adb activated. I have backup of the original partition but fast does not let me write it for lack of permissions.
I was able to flash with a STOCK version I can enter the recovery
I made an update.zip file with this content:
updater-script
Code:
ui_print("Installing update.zip");
package_extract_file("cid.img", "/dev/block/mmcblk0p7");
ui_print("Flashed update.zip successfully");
Since it is not signed, it does not work.
This is the output I get from fastboot getvar all
Code:
bash-4.3# fastboot getvar all
(bootloader) version-bootloader: 0x2025
(bootloader) product: smi
(bootloader) secure: yes
(bootloader) rom-key: motorola-key
(bootloader) model-id: 0268
(bootloader) cid: dead
(bootloader) version: 0.5
(bootloader) uid: CFDE99E41C23C94DF17472715D60
(bootloader) max-download-size: 104857600
(bootloader) emmc-size: 8GB
(bootloader) qe: qe 1/1
(bootloader) unlocked: no
(bootloader) is-warranty-void: Not supported
(bootloader) ifwi: 42.26
(bootloader) cpu: Intel(R) Atom(TM) CPU Z2480 @ 2.00GHz
(bootloader) kernel: droidboot
(bootloader) battery: capacity: 100, voltage: 4320000, temperature: 370
(bootloader) modem-status: secure
all:
Finished. Total time: 0.336s
as you can see it says cid: dead
Any idea is well received
Thank you
Sorry for my English.
*

XZ1c bootloop after low storage, tried flashing, keeps on bootlooping

Hi,
been breaking my head about this strange problem for days now.:crying:
Device: G8441
State of device before incident: Bootloader locked, Developer Options off, all stock/Playstore. Aka off the shelf.
What happened: Went into bootloop (black Sony on white background) after device ran short of internal storage while attempting to install an app from the Playstore (it went into pending and gave me a storage warning). Upon then the device became laggy, so I rebooted. Phone never came back to life. I took many photos that day, and upon getting a storage warning earlier I had changed the camera save location to SD. The battery was at about 30%.
When it happened: 17/02/2019, at that point I am pretty sure I was up-to-date with OTA updates.
With the bootlooping phone I am able to connect Flashmode (green LED) and Fastboot mode (blue LED).
I could get the following info from Fastboot:
PS C:\Users\bkt\Desktop\platform-tools> fastboot getvar all
(bootloader) hw-revision:20001
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4178
(bootloader) version-baseband:1307-7511_47.2.A.6.30
(bootloader) version-bootloader:1306-5035_X_Boot_MSM8998_LA2.0_P_107
(bootloader) erase-block-size: 0x1000
(bootloader) logical-block-size: 0x1000
(bootloader) variant:MSM UFS
(bootloader) partition-type:xblbak:raw
(bootloader) partition-size:xblbak: 0x3F5000
(bootloader) partition-type:xbl:raw
(bootloader) partition-size:xbl: 0x3F5000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x587D76000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x138800000
(bootloader) partition-type:vendor:raw
(bootloader) partition-size:vendor: 0x60000000
(bootloader) partition-typeem:raw
(bootloader) partition-sizeem: 0x19000000
(bootloader) partition-type:rdimage:raw
(bootloader) partition-size:rdimage: 0x2000000
(bootloader) partition-type:fsmetadata:raw
(bootloader) partition-size:fsmetadata: 0x101000
(bootloader) partition-type:Qnovo:raw
(bootloader) partition-size:Qnovo: 0x1800000
(bootloader) partition-type:diag:raw
(bootloader) partition-size:diag: 0x2000000
(bootloader) partition-type:appslog:raw
(bootloader) partition-size:appslog: 0x1000000
(bootloader) partition-type:vbmeta:raw
(bootloader) partition-size:vbmeta: 0x10000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x17C00000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x1000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x200000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x200000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:FOTAKernel:raw
(bootloader) partition-size:FOTAKernel: 0x4000000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x1000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x20A4000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x1000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:bluetooth:raw
(bootloader) partition-size:bluetooth: 0x100000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:dsp:raw
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0x6E00000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x180000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:xflkeystorebak:raw
(bootloader) partition-size:xflkeystorebak: 0x20000
(bootloader) partition-type:xflkeystore:raw
(bootloader) partition-size:xflkeystore: 0x20000
(bootloader) partition-type:tzxflbak:raw
(bootloader) partition-size:tzxflbak: 0x80000
(bootloader) partition-type:tzxfl:raw
(bootloader) partition-size:tzxfl: 0x80000
(bootloader) partition-type:tzxflattestbak:raw
(bootloader) partition-size:tzxflattestbak: 0x80000
(bootloader) partition-type:tzxflattest:raw
(bootloader) partition-size:tzxflattest: 0x80000
(bootloader) partition-type:xflbak:raw
(bootloader) partition-size:xflbak: 0x1E00000
(bootloader) partition-type:xfl:raw
(bootloader) partition-size:xfl: 0x1E00000
(bootloader) partition-type:storsecbak:raw
(bootloader) partition-size:storsecbak: 0x20000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:devcfgbak:raw
(bootloader) partition-size:devcfgbak: 0x20000
(bootloader) partition-type:devcfg:raw
(bootloader) partition-size:devcfg: 0x20000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:cmnlib64bak:raw
(bootloader) partition-size:cmnlib64bak: 0x80000
(bootloader) partition-type:cmnlib64:raw
(bootloader) partition-size:cmnlib64: 0x80000
(bootloader) partition-type:cmnlibbak:raw
(bootloader) partition-size:cmnlibbak: 0x80000
(bootloader) partition-type:cmnlib:raw
(bootloader) partition-size:cmnlib: 0x80000
(bootloader) partition-type:keymasterbak:raw
(bootloader) partition-size:keymasterbak: 0x80000
(bootloader) partition-type:keymaster:raw
(bootloader) partition-size:keymaster: 0x80000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:ablbak:raw
(bootloader) partition-size:ablbak: 0x180000
(bootloader) partition-type:abl:raw
(bootloader) partition-size:abl: 0x180000
(bootloader) partition-typemicbak:raw
(bootloader) partition-sizemicbak: 0x80000
(bootloader) partition-typemic:raw
(bootloader) partition-sizemic: 0x80000
(bootloader) partition-type:hypbak:raw
(bootloader) partition-size:hypbak: 0x80000
(bootloader) partition-type:hyp:raw
(bootloader) partition-size:hyp: 0x80000
(bootloader) partition-type:tzbak:raw
(bootloader) partition-size:tzbak: 0x200000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x200000
(bootloader) partition-type:rpmbak:raw
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:raw
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:LTALabel:raw
(bootloader) partition-size:LTALabel: 0x1000000
(bootloader) partition-type:TA:raw
(bootloader) partition-size:TA: 0x200000
(bootloader) secure:yes
(bootloader) serialno:BH907G3J9E
(bootloader) serial:d45071fd
(bootloader) product:G8441
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.546s
Click to expand...
Click to collapse
What has been done so far: By now I have tried to flash almost a dozen different firmware FTF's obtained from Xperifirm, first trying Flashtool by @Androxyde and later Newflasher by @munjeni. I always excluded userdata.sin and most of the .ta files. The flashes seem to work fine as they finish normally and throw no error. But there has been never been a change to the bootloop whatsoever at all at any point.
Only in Flashtool I get some blue warnings about packages excluded from flash.
Strange: Fastboot keeps reading the baseband version as "(bootloader) version-baseband:1307-7511_47.2.A.6.30". However, Xperia Companion identifies it as "47.2.A.8.24-R3C".
It doesn't seem to matter which firmware version I try to flash, fastboot will always identify it as "47.2.A.6.30".
Only with the bootloader version I identified changes between "version-bootloader:1306-5035_X_Boot_MSM8998_LA2.0_P_107" and "(bootloader) version-bootloader:1306-5035_X_Boot_MSM8998_LA1.1_O_77".
I noticed that when plugged into the charger, the phone will attempt boot and go into bootloop. It won't show the Charging screen.
Goal: Get it to boot Android again, into any kind of firmware, to save the tons of non-backuped photos, and only then do a factory reset/Xperia Software Repair...
Question: What else can I try? Is the problem that my internal storage is full, and it is blocking the OS from booting, thus I need to free up space? Is it possible to flash a userdata.sin that only wipes storage partially? Or maybe a partition problem? Is it possible to flash a stock ROM that boots into Safe Mode directly, then stuff could be deleted slectively?
Am hoping to find advise from some experienced devs here.
You said you deleted most of the ta files. I thought you should delete all of them. Also delete persist.sin file. Other than that, I would do a clean wipe. Sorry about your files.
Milly7 said:
You said you deleted most of the ta files. I thought you should delete all of them. Also delete persist.sin file. Other than that, I would do a clean wipe. Sorry about your files.
Click to expand...
Click to collapse
Thanks a lot for your reply.
Yes, during the first few flash attempts I excluded all .ta files. After reading more in the forum I understood there are different opinions about their potential danger, especially since my device's bootloader is locked and Dev Options are off. Then I started to include those less dangerous .ta's during the flashs, like 'reset-non-secure-adb.ta' or the one in the boot folder, 'Lilac_XBootConfig_MiscTA.ta'.
I thought more about the moment the bootloop started and think maybe the Sony Power Saving mode got activated, since the battery was near 30%. Mmhhh
Yes, I am considering a clean software repair with Xperia Companion, too. I still want to try everything to get those photos. Thinking Software Repair -> Bootloader Unlock -> Root -> Internal Storage Raw Image -> Mount it -> Scan . . . damn
Thank you.
I have a similar problem. I bought a new phone because xz1c had memory issues. I was removing Facebook on Google play to save up space to install Samsung Switch. The device went into that bootloop you mentioned. However, I am not a proficient user like you, I can't perform any of the things you've mentioned. But I do recognize the blue and green flashes before the Sony sign. Then comes the black maintenance triangle, then android logo and reboot. A few times I have seen it pass on to xperia logo, but failed to boot every time.
The only goal is to get the device back on so I can transfer phonebook and messages because I don't have any backups. And they are important for me.
Any solutions?

Unable to boot with other image with fastboot

Hi there,
I would like to root my Nokia 8 phone as it went out of warranty. I am new to deep Android hacks so I am basically following the guide: How to root your Nokia 8. My bootloader is unlocked with the official procedure. The next step is to boot with a TWRP or a prerooted image and install Magisk.
Unfortunately when I use the fastboot utility, the loading is done corectly and the phone reboots but then gets stuck on the "Powered by Android" splashscreen. This is occuring with both twrp-3.2.3-0-NB1.img and twrp-3.2.3-1-NB1.img
Here is the content of "fastboot getvar all" if that's relevant:
Code:
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3792
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xCEC456000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xE0000000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:5
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:NB1GASxxxxxxxxxxx
(bootloader) product:QC_Reference_Phone
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) version:0.0
Has someone got the same error and solved it? Is there any way to print some debug information during the booting step?
Thanks,
MatPy
OK, I found an answer there: https://tmsp.io/fs/xda/nb1/README.txt
Temporary booting:
As of NB1-488G-0-00WW-B01 the command "fastboot boot" is broken and does
not work like it should. It will lock you in the "Powered by Android"
screen without actually booting the image you supplied. To exit the screen,
please do "fastboot reboot" and then flash the image you wanted to boot to
your active boot partition.
Click to expand...
Click to collapse
So you can't actually use TWRP without installing it with a up-to-date firmware. Why the Rooting Guide is not updated with this information? This isue is old as it appeared with the 2018-08 security patch.
MatPy said:
Hi there,
I would like to root my Nokia 8 phone as it went out of warranty. I am new to deep Android hacks so I am basically following the guide: How to root your Nokia 8. My bootloader is unlocked with the official procedure. The next step is to boot with a TWRP or a prerooted image and install Magisk.
Unfortunately when I use the fastboot utility, the loading is done corectly and the phone reboots but then gets stuck on the "Powered by Android" splashscreen. This is occuring with both twrp-3.2.3-0-NB1.img and twrp-3.2.3-1-NB1.img
Here is the content of "fastboot getvar all" if that's relevant:
Code:
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3792
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xCEC456000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xE0000000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:5
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:NB1GASxxxxxxxxxxx
(bootloader) product:QC_Reference_Phone
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) version:0.0
Has someone got the same error and solved it? Is there any way to print some debug information during the booting step?
Thanks,
MatPy
Click to expand...
Click to collapse
The only way to install the offical TWRP on Android 9 is to flash TWRP to boot slot B then install TWRP zip for both slots so slot A will receive TWRP. the only thing left is to switch back to slot A.

Question Root?

Is there anyone who has any boot.img or knows the correct procedure to root this thing?
kouzelnik3 said:
Is there anyone who has any boot.img or knows the correct procedure to root this thing?
Click to expand...
Click to collapse
I would install Magisk by following the official installation instructions. Let me know if you have any questions after reading through them.
ethical_haquer said:
I would install Magisk by following the official installation instructions. Let me know if you have any questions after reading through them.
Click to expand...
Click to collapse
Yeah, that's what I know, but I don't have that boot img or something, yet.
kouzelnik3 said:
Yeah, that's what I know, but I don't have that boot img or something, yet.
Click to expand...
Click to collapse
If you can dd the right partition from the tablet, you can have the boot image:
From adb shell, launch the comand "lsblk". You will get a list of partition currently on the tablet. The boot partition should be indicated one way or another.
From adb shell, "dd if=/dev/[insert-boot-partition-name] of=/storage/emulated/0/boot.img"
Tranfert the saved boot.img to your computer.
w1nst0n sm1th said:
If you can dd the right partition from the tablet, you can have the boot image:
From adb shell, launch the comand "lsblk". You will get a list of partition currently on the tablet. The boot partition should be indicated one way or another.
From adb shell, "dd if=/dev/[insert-boot-partition-name] of=/storage/emulated/0/boot.img"
Tranfert the saved boot.img to your computer.
Click to expand...
Click to collapse
Well, by this command I cannot see any boot.img partition, only few others, which is weird.
Also according to the "dd" command, it didn't work (screenshots) because of Permission denied.
Error message
kouzelnik3 said:
Well, by this command I cannot see any boot.img partition, only few others, which is weird.
Also according to the "dd" command, it didn't work (screenshots) because of Permission denied.
Click to expand...
Click to collapse
There is an error in your command:
It's "lsblk", not "ls -blk"
See here for a linux version:
lsblk
You may need to set developer options on the device before being able to run such a command :
Develloper Options
And here an explanation of the dd command:
dd
If you're not sure about dd (you should be very cautious with that command), post a picture of the result of the lsblk command and I will tell you the exact command for dd.
I long quit the android space, but I'm interrested by this tablet since Android 13 has a hypervisor normally included (able to run a virtual machine).
w1nst0n sm1th said:
There is an error in your command:
It's "lsblk", not "ls -blk"
See here for a linux version:
lsblk
You may need to set developer options on the device before being able to run such a command :
Develloper Options
And here an explanation of the dd command:
dd
If you're not sure about dd (you should be very cautious with that command), post a picture of the result of the lsblk command and I will tell you the exact command for dd.
I long quit the android space, but I'm interrested by this tablet since Android 13 has a hypervisor normally included (able to run a virtual machine).
Click to expand...
Click to collapse
I have set up the Developer options before, but when I use "lsblk" command, it says "/system/bin/sh: lsblk: inaccessible or not found" which is why I used "ls -lbk". Do you know what be an issue here?
I got same results even with my rooted OnePlus 10 Pro.
Well. Apparently, lsblk is not included.
You will have to wait for an update to be available on the telegram channel, unpack the update to extract the boot.img (init_boot.img).
See :
https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-13-a-10.4571171/
w1nst0n sm1th said:
Well. Apparently, lsblk is not included.
You will have to wait for an update to be available on the telegram channel, unpack the update to extract the boot.img (init_boot.img).
See :
https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-13-a-10.4571171/
Click to expand...
Click to collapse
I thought that. By the way, which telegram channel has those files?
w1nst0n sm1th said:
...
I long quit the android space, but I'm interrested by this tablet since Android 13 has a hypervisor normally included (able to run a virtual machine).
Click to expand...
Click to collapse
Too bad it's not the variant with more RAM & storage. I'm also very intrigued but know very little apart from couple YouTube videos.
While we try to gain root. Can we get instructions on how to unlock the bootloader so I don't have to have my storage wiped again when we do get root
I assume it is basic proces as on any other OP device. OEM unlock, fastboot mode and other fastboot flashing unlock, then yes. Someone can try.
Fastboot oem unlock does not work , Fastboot flashing unlock threw an error but said it was successful but did not wipe data. Manually wipped data and got stuck in a boot loop. Windows will not detect it in recovery mode and I can not get it back into bootloader mode.
XxBigBuckxX said:
Fastboot oem unlock does not work , Fastboot flashing unlock threw an error but said it was successful but did not wipe data. Manually wipped data and got stuck in a boot loop. Windows will not detect it in recovery mode and I can not get it back into bootloader mode.
Click to expand...
Click to collapse
Did you turn on OEM Unlock in developer options? And as you are stuck in bootloop without bootloader mode, I think the only option is service center.
kouzelnik3 said:
Did you turn on OEM Unlock in developer options? And as you are stuck in bootloop without bootloader mode, I think the only option is service center.
Click to expand...
Click to collapse
Yes I turned it on before unlocking bootloader, I paniced after it started to bootloop and relocked the bootloader after manually trying to wipe data which could be why I cant get into bootloader. I reached out to support hoping for a remote fix like the oneplus 10T but nothing. I could only get my pc to detect it in edl mode. I'm mailing it in today they didn't have any troubleshooting steps just going to RMA it.
XxBigBuckxX said:
Yes I turned it on before unlocking bootloader, I paniced after it started to bootloop and relocked the bootloader after manually trying to wipe data which could be why I cant get into bootloader. I reached out to support hoping for a remote fix like the oneplus 10T but nothing. I could only get my pc to detect it in edl mode. I'm mailing it in today they didn't have any troubleshooting steps just going to RMA it.
Click to expand...
Click to collapse
Well, trying to relock it was definitely the wrong move. RMA will solve it anyway.
I got my replacement today and it happened again. The only thing I had done was enable oem unlock. The only commands I ran
Code:
PS C:\Users\nate> adb devices
List of devices attached
49YLUKXKQSMBKB6T device
PS C:\Users\nate> adb reboot bootloader
PS C:\Users\nate> fastboot help
usage: fastboot [OPTION...] COMMAND...
flashing:
update ZIP Flash all partitions from an update.zip package.
flashall Flash all partitions from $ANDROID_PRODUCT_OUT.
On A/B devices, flashed slot is set as active.
Secondary images may be flashed to inactive slot.
flash PARTITION [FILENAME] Flash given partition, using the image from
$ANDROID_PRODUCT_OUT if no filename is given.
basics:
devices [-l] List devices in bootloader (-l: with device paths).
getvar NAME Display given bootloader variable.
reboot [bootloader] Reboot device.
locking/unlocking:
flashing lock|unlock Lock/unlock partitions for flashing
flashing lock_critical|unlock_critical
Lock/unlock 'critical' bootloader partitions.
flashing get_unlock_ability
Check whether unlocking is allowed (1) or not(0).
advanced:
erase PARTITION Erase a flash partition.
format[:FS_TYPE[:SIZE]] PARTITION
Format a flash partition.
set_active SLOT Set the active slot.
oem [COMMAND...] Execute OEM-specific command.
gsi wipe|disable Wipe or disable a GSI installation (fastbootd only).
wipe-super [SUPER_EMPTY] Wipe the super partition. This will reset it to
contain an empty set of default dynamic partitions.
create-logical-partition NAME SIZE
Create a logical partition with the given name and
size, in the super partition.
delete-logical-partition NAME
Delete a logical partition with the given name.
resize-logical-partition NAME SIZE
Change the size of the named logical partition.
snapshot-update cancel On devices that support snapshot-based updates, cancel
an in-progress update. This may make the device
unbootable until it is reflashed.
snapshot-update merge On devices that support snapshot-based updates, finish
an in-progress update if it is in the "merging"
phase.
fetch PARTITION OUT_FILE Fetch a partition image from the device.
boot image:
boot KERNEL [RAMDISK [SECOND]]
Download and boot kernel from RAM.
flash:raw PARTITION KERNEL [RAMDISK [SECOND]]
Create boot image and flash it.
--dtb DTB Specify path to DTB for boot image header version 2.
--cmdline CMDLINE Override kernel command line.
--base ADDRESS Set kernel base address (default: 0x10000000).
--kernel-offset Set kernel offset (default: 0x00008000).
--ramdisk-offset Set ramdisk offset (default: 0x01000000).
--tags-offset Set tags offset (default: 0x00000100).
--dtb-offset Set dtb offset (default: 0x01100000).
--page-size BYTES Set flash page size (default: 2048).
--header-version VERSION Set boot image header version.
--os-version MAJOR[.MINOR[.PATCH]]
Set boot image OS version (default: 0.0.0).
--os-patch-level YYYY-MM-DD
Set boot image OS security patch level.
Android Things:
stage IN_FILE Sends given file to stage for the next command.
get_staged OUT_FILE Writes data staged by the last command to a file.
options:
-w Wipe userdata.
-s SERIAL Specify a USB device.
-s tcp|udp:HOST[:PORT] Specify a network device.
-S SIZE[K|M|G] Break into sparse files no larger than SIZE.
--force Force a flash operation that may be unsafe.
--slot SLOT Use SLOT; 'all' for both slots, 'other' for
non-current slot (default: current active slot).
--set-active[=SLOT] Sets the active slot before rebooting.
--skip-secondary Don't flash secondary slots in flashall/update.
--skip-reboot Don't reboot device after flashing.
--disable-verity Sets disable-verity when flashing vbmeta.
--disable-verification Sets disable-verification when flashing vbmeta.
--fs-options=OPTION[,OPTION]
Enable filesystem features. OPTION supports casefold, projid, compress
--unbuffered Don't buffer input or output.
--verbose, -v Verbose output.
--version Display version.
--help, -h Show this message.
PS C:\Users\nate> fastboot flashing get_unlock_ability
(bootloader) unlock_ability is true
OKAY [ 0.003s]
Finished. Total time: 0.004s
PS C:\Users\nate> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
Finished. Total time: 15.144s
PS C:\Users\nate> fastboot getvar all
(bootloader) cpu-abi:arm64-v8a
(bootloader) snapshot-update-status:none
(bootloader) super-partition-name:super
(bootloader) is-logical:preloader_raw_b:no
(bootloader) is-logical:preloader_raw_a:no
(bootloader) is-logical:pi_img_a:no
(bootloader) is-logical:scp_a:no
(bootloader) is-logical:vcp_a:no
(bootloader) is-logical:dpm_b:no
(bootloader) is-logical:misc:no
(bootloader) is-logical:audio_dsp_a:no
(bootloader) is-logical:efuse:no
(bootloader) is-logical:connsys_wifi_a:no
(bootloader) is-logical:ocdt:no
(bootloader) is-logical:spmfw_b:no
(bootloader) is-logical:logo_b:no
(bootloader) is-logical:logo_a:no
(bootloader) is-logical:splash_odm:no
(bootloader) is-logical:sspm_b:no
(bootloader) is-logical:nvcfg:no
(bootloader) is-logical:connsys_bt_b:no
(bootloader) is-logical:vbmeta_b:no
(bootloader) is-logical:audio_dsp_b:no
(bootloader) is-logical:gpueb_b:no
(bootloader) is-logical:boot_para:no
(bootloader) is-logical:dtbo_b:no
(bootloader) is-logical:proinfo:no
(bootloader) is-logical:mvpu_algo_b:no
(bootloader) is-logical:nvdata:no
(bootloader) is-logical:protect2:no
(bootloader) is-logical:connsys_wifi_b:no
(bootloader) is-logical:userdata:no
(bootloader) is-logical:lk_b:no
(bootloader) is-logical:tee_b:no
(bootloader) is-logical:otp:no
(bootloader) is-logical:sdb:no
(bootloader) is-logical:gz_a:no
(bootloader) is-logical:gpueb_a:no
(bootloader) is-logical:dram_para:no
(bootloader) is-logical:cdt_engineering_a:no
(bootloader) is-logical:boot_a:no
(bootloader) is-logical:mcupm_a:no
(bootloader) is-logical:oplus_custom:no
(bootloader) is-logical:sda:no
(bootloader) is-logical:vcp_b:no
(bootloader) is-logical:init_boot_b:no
(bootloader) is-logical:init_boot_a:no
(bootloader) is-logical:flashinfo:no
(bootloader) is-logical:frp:no
(bootloader) is-logical:vendor_boot_b:no
(bootloader) is-logical:dtbo_a:no
(bootloader) is-logical:protect1:no
(bootloader) is-logical:sspm_a:no
(bootloader) is-logical:oplusreserve3:no
(bootloader) is-logical:lk_a:no
(bootloader) is-logical:persist:no
(bootloader) is-logical:oplusreserve6:no
(bootloader) is-logical:boot_b:no
(bootloader) is-logical:scp_b:no
(bootloader) is-logical:expdb:no
(bootloader) is-logical:param:no
(bootloader) is-logical:mvpu_algo_a:no
(bootloader) is-logical:pi_img_b:no
(bootloader) is-logical:oplusreserve1:no
(bootloader) is-logical:vendor_boot_a:no
(bootloader) is-logical:dpm_a:no
(bootloader) is-logical:mcupm_b:no
(bootloader) is-logical:ccu_a:no
(bootloader) is-logical:seccfg:no
(bootloader) is-logical:vbmeta_vendor_b:no
(bootloader) is-logical:apusys_b:no
(bootloader) is-logical:para:no
(bootloader) is-logical:gz_b:no
(bootloader) is-logical:nvram:no
(bootloader) is-logical:cdt_engineering_b:no
(bootloader) is-logical:apusys_a:no
(bootloader) is-logical:vbmeta_system_b:no
(bootloader) is-logical:oplusreserve5:no
(bootloader) is-logical:spmfw_a:no
(bootloader) is-logical:ccu_b:no
(bootloader) is-logical:sdc:no
(bootloader) is-logical:tee_a:no
(bootloader) is-logical:connsys_bt_a:no
(bootloader) is-logical:sec1:no
(bootloader) is-logical:oplusreserve2:no
(bootloader) is-logical:metadata:no
(bootloader) is-logical:vbmeta_system_a:no
(bootloader) is-logical:super:no
(bootloader) is-logical:vbmeta_a:no
(bootloader) is-logical:vbmeta_vendor_a:no
(bootloader) is-logical:system_a:yes
(bootloader) is-logical:system_b:yes
(bootloader) is-logical:system_ext_a:yes
(bootloader) is-logical:system_ext_b:yes
(bootloader) is-logical:vendor_a:yes
(bootloader) is-logical:vendor_b:yes
(bootloader) is-logical:product_a:yes
(bootloader) is-logical:product_b:yes
(bootloader) is-logical:my_product_a:yes
(bootloader) is-logical:my_product_b:yes
(bootloader) is-logical:odm_a:yes
(bootloader) is-logical:odm_b:yes
(bootloader) is-logical:my_engineering_a:yes
(bootloader) is-logical:my_engineering_b:yes
(bootloader) is-logical:vendor_dlkm_a:yes
(bootloader) is-logical:vendor_dlkm_b:yes
(bootloader) is-logical:odm_dlkm_a:yes
(bootloader) is-logical:odm_dlkm_b:yes
(bootloader) is-logical:my_stock_a:yes
(bootloader) is-logical:my_stock_b:yes
(bootloader) is-logical:my_heytap_a:yes
(bootloader) is-logical:my_heytap_b:yes
(bootloader) is-logical:my_carrier_a:yes
(bootloader) is-logical:my_carrier_b:yes
(bootloader) is-logical:my_region_a:yes
(bootloader) is-logical:my_region_b:yes
(bootloader) is-logical:my_company_a:yes
(bootloader) is-logical:my_company_b:yes
(bootloader) is-logical:my_preload_a:yes
(bootloader) is-logical:my_preload_b:yes
(bootloader) is-logical:my_bigball_a:yes
(bootloader) is-logical:my_bigball_b:yes
(bootloader) is-logical:my_manifest_a:yes
(bootloader) is-logical:my_manifest_b:yes
(bootloader) battery-voltage:3
(bootloader) treble-enabled:true
(bootloader) is-userspace:yes
(bootloader) partition-size:preloader_raw_b:0x3FF000
(bootloader) partition-size:preloader_raw_a:0x3FF000
(bootloader) partition-size:pi_img_a:0x100000
(bootloader) partition-size:scp_a:0x600000
(bootloader) partition-size:vcp_a:0x600000
(bootloader) partition-size:dpm_b:0x400000
(bootloader) partition-size:misc:0x80000
(bootloader) partition-size:audio_dsp_a:0xC00000
(bootloader) partition-size:efuse:0x80000
(bootloader) partition-size:connsys_wifi_a:0x800000
(bootloader) partition-size:ocdt:0x800000
(bootloader) partition-size:spmfw_b:0x100000
(bootloader) partition-size:logo_b:0x2000000
(bootloader) partition-size:logo_a:0x2000000
(bootloader) partition-size:splash_odm:0x2580000
(bootloader) partition-size:sspm_b:0x100000
(bootloader) partition-size:nvcfg:0x2000000
(bootloader) partition-size:connsys_bt_b:0x800000
(bootloader) partition-size:vbmeta_b:0x800000
(bootloader) partition-size:audio_dsp_b:0xC00000
(bootloader) partition-size:gpueb_b:0x100000
(bootloader) partition-size:boot_para:0x100000
(bootloader) partition-size:dtbo_b:0x800000
(bootloader) partition-size:proinfo:0x300000
(bootloader) partition-size:mvpu_algo_b:0x4000000
(bootloader) partition-size:nvdata:0x4000000
(bootloader) partition-size:protect2:0x800000
(bootloader) partition-size:connsys_wifi_b:0x800000
(bootloader) partition-size:userdata:0x19DB7F8000
(bootloader) partition-size:lk_b:0x500000
(bootloader) partition-size:tee_b:0x500000
(bootloader) partition-size:otp:0x2B00000
(bootloader) partition-size:gz_a:0x2000000
(bootloader) partition-size:gpueb_a:0x100000
(bootloader) partition-size:dram_para:0x1900000
(bootloader) partition-size:cdt_engineering_a:0xC80000
(bootloader) partition-size:boot_a:0x4000000
(bootloader) partition-size:mcupm_a:0x100000
(bootloader) partition-size:oplus_custom:0x100000
(bootloader) partition-size:vcp_b:0x600000
(bootloader) partition-size:init_boot_b:0x800000
(bootloader) partition-size:init_boot_a:0x800000
(bootloader) partition-size:flashinfo:0x1000000
(bootloader) partition-size:frp:0x100000
(bootloader) partition-size:vendor_boot_b:0x4000000
(bootloader) partition-size:dtbo_a:0x800000
(bootloader) partition-size:protect1:0x800000
(bootloader) partition-size:sspm_a:0x100000
(bootloader) partition-size:oplusreserve3:0x4000000
(bootloader) partition-size:lk_a:0x500000
(bootloader) partition-size:oplusreserve6:0x4000000
(bootloader) partition-size:boot_b:0x4000000
(bootloader) partition-size:scp_b:0x600000
(bootloader) partition-size:expdb:0x8000000
(bootloader) partition-size:param:0x100000
(bootloader) partition-size:mvpu_algo_a:0x4000000
(bootloader) partition-size:pi_img_b:0x100000
(bootloader) partition-size:oplusreserve1:0x800000
(bootloader) partition-size:vendor_boot_a:0x4000000
(bootloader) partition-size:dpm_a:0x400000
(bootloader) partition-size:mcupm_b:0x100000
(bootloader) partition-size:ccu_a:0x400000
(bootloader) partition-size:seccfg:0x800000
(bootloader) partition-size:vbmeta_vendor_b:0x800000
(bootloader) partition-size:apusys_b:0x400000
(bootloader) partition-size:para:0x80000
(bootloader) partition-size:gz_b:0x2000000
(bootloader) partition-size:nvram:0x4000000
(bootloader) partition-size:cdt_engineering_b:0xC80000
(bootloader) partition-size:apusys_a:0x400000
(bootloader) partition-size:vbmeta_system_b:0x800000
(bootloader) partition-size:oplusreserve5:0x2000000
(bootloader) partition-size:spmfw_a:0x100000
(bootloader) partition-size:ccu_b:0x400000
(bootloader) partition-size:tee_a:0x500000
(bootloader) partition-size:connsys_bt_a:0x800000
(bootloader) partition-size:sec1:0x200000
(bootloader) partition-size:metadata:0x2000000
(bootloader) partition-size:vbmeta_system_a:0x800000
(bootloader) partition-size:vbmeta_a:0x800000
(bootloader) partition-size:vbmeta_vendor_a:0x800000
(bootloader) partition-size:system_a:0x2E961000
(bootloader) partition-size:system_b:0x0
(bootloader) partition-size:system_ext_a:0x3D2E6000
(bootloader) partition-size:system_ext_b:0x0
(bootloader) partition-size:vendor_a:0x421DF000
(bootloader) partition-size:vendor_b:0x0
(bootloader) partition-size:product_a:0x1CA000
(bootloader) partition-size:product_b:0x0
(bootloader) partition-size:my_product_a:0x13813000
(bootloader) partition-size:my_product_b:0x0
(bootloader) partition-size:odm_a:0x46C6C000
(bootloader) partition-size:odm_b:0x0
(bootloader) partition-size:my_engineering_a:0x52000
(bootloader) partition-size:my_engineering_b:0x0
(bootloader) partition-size:vendor_dlkm_a:0x3589000
(bootloader) partition-size:vendor_dlkm_b:0x0
(bootloader) partition-size:odm_dlkm_a:0x55000
(bootloader) partition-size:odm_dlkm_b:0x0
(bootloader) partition-size:my_stock_a:0x1EAA9000
(bootloader) partition-size:my_stock_b:0x0
(bootloader) partition-size:my_heytap_a:0x2CAE2000
(bootloader) partition-size:my_heytap_b:0x0
(bootloader) partition-size:my_carrier_a:0x52000
(bootloader) partition-size:my_carrier_b:0x0
(bootloader) partition-size:my_region_a:0x376000
(bootloader) partition-size:my_region_b:0x0
(bootloader) partition-size:my_company_a:0x52000
(bootloader) partition-size:my_company_b:0x0
(bootloader) partition-size:my_preload_a:0x253000
(bootloader) partition-size:my_preload_b:0x0
(bootloader) partition-size:my_bigball_a:0x2BF47000
(bootloader) partition-size:my_bigball_b:0x0
(bootloader) partition-size:my_manifest_a:0x58000
(bootloader) partition-size:my_manifest_b:0x0
(bootloader) version-vndk:31
(bootloader) has-slot:preloader_raw:yes
(bootloader) has-slot:pi_img:yes
(bootloader) has-slot:scp:yes
(bootloader) has-slot:vcp:yes
(bootloader) has-slot:dpm:yes
(bootloader) has-slot:misc:no
(bootloader) has-slot:audio_dsp:yes
(bootloader) has-slot:efuse:no
(bootloader) has-slot:connsys_wifi:yes
(bootloader) has-slot:ocdt:no
(bootloader) has-slot:spmfw:yes
(bootloader) has-slot:logo:yes
(bootloader) has-slot:splash_odm:no
(bootloader) has-slot:sspm:yes
(bootloader) has-slot:nvcfg:no
(bootloader) has-slot:connsys_bt:yes
(bootloader) has-slot:vbmeta:yes
(bootloader) has-slot:gpueb:yes
(bootloader) has-slot:boot_para:no
(bootloader) has-slot:dtbo:yes
(bootloader) has-slot:proinfo:no
(bootloader) has-slot:mvpu_algo:yes
(bootloader) has-slot:nvdata:no
(bootloader) has-slot:protect2:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:lk:yes
(bootloader) has-slot:tee:yes
(bootloader) has-slot:otp:no
(bootloader) has-slot:sdb:no
(bootloader) has-slot:gz:yes
(bootloader) has-slot:dram_para:no
(bootloader) has-slot:cdt_engineering:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:mcupm:yes
(bootloader) has-slot:oplus_custom:no
(bootloader) has-slot:sda:no
(bootloader) has-slot:init_boot:yes
(bootloader) has-slot:flashinfo:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:vendor_boot:yes
(bootloader) has-slot:protect1:no
(bootloader) has-slot:oplusreserve3:no
(bootloader) has-slot:persist:no
(bootloader) has-slot:oplusreserve6:no
(bootloader) has-slot:expdb:no
(bootloader) has-slot:param:no
(bootloader) has-slot:oplusreserve1:no
(bootloader) has-slot:ccu:yes
(bootloader) has-slot:seccfg:no
(bootloader) has-slot:vbmeta_vendor:yes
(bootloader) has-slot:apusys:yes
(bootloader) has-slot:para:no
(bootloader) has-slot:nvram:no
(bootloader) has-slot:vbmeta_system:yes
(bootloader) has-slot:oplusreserve5:no
(bootloader) has-slot:sdc:no
(bootloader) has-slot:sec1:no
(bootloader) has-slot:oplusreserve2:no
(bootloader) has-slot:metadata:no
(bootloader) has-slot:super:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:system_ext:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:product:yes
(bootloader) has-slot:my_product:yes
(bootloader) has-slot:odm:yes
(bootloader) has-slot:my_engineering:yes
(bootloader) has-slot:vendor_dlkm:yes
(bootloader) has-slot:odm_dlkm:yes
(bootloader) has-slot:my_stock:yes
(bootloader) has-slot:my_heytap:yes
(bootloader) has-slot:my_carrier:yes
(bootloader) has-slot:my_region:yes
(bootloader) has-slot:my_company:yes
(bootloader) has-slot:my_preload:yes
(bootloader) has-slot:my_bigball:yes
(bootloader) has-slot:my_manifest:yes
(bootloader) security-patch-level:2023-03-05
(bootloader) vendor-fingerprint:oplus/ossi/ossi:12/SP1A.210812.016/1679153745760:user/release-keys
(bootloader) hw-revision:0
(bootloader) current-slot:a
(bootloader) serialno:49YLUKXKQSMBKB6T
(bootloader) product:ossi
(bootloader) version-os:12
(bootloader) first-api-level:31
(bootloader) slot-count:2
(bootloader) max-download-size:0x10000000
(bootloader) version:0.4
(bootloader) version-baseband:
(bootloader) secure:yes
(bootloader) dynamic-partition:true
(bootloader) system-fingerprint:oplus/ossi/ossi:12/SP1A.210812.016/1679153745760:user/release-keys
(bootloader) version-bootloader:unknown
(bootloader) unlocked:no
all:
Finished. Total time: 1.938s
PS C:\Users\nate> fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.001s
Ater that reboot just right back into the bootloop
Right after that? You basically just rebooted to bootloader, fastboot and then back to the system, but instead of booting, bootloop again? That's even more weird.
kouzelnik3 said:
Right after that? You basically just rebooted to bootloader, fastboot and then back to the system, but instead of booting, bootloop again? That's even more weird.
Click to expand...
Click to collapse
Yeah , I am pretty confused. Service center is not able to help me again yet (Only provide refund which is not what I want) because the previous service request is still open stuck on the device inspection stage. I am just trying to figure out stuff on my own at the moment untill that gets resolved.
I was able to figure a few more things out but not familiar with MTK as I am edl but I went down that path. I was able to get into preloader mode and also downloader mode. I switched over to linux and used mtkclient and it was detecing the device but giving watchdog errors.

Categories

Resources