Database Develop

[Q] bootloader failed to start

hello XDA community,
i have a weird problem with my m7. one day after a reboot the phone just didn't boot and went straight to bootloader. i've tried installing original RUU, and after rebooting bootloader the phone just didn't came back on and the RUU failed to proceed. when holding PWR+DOWN buttons , i've managed to get to HBOOT menu but every choice i make there freezes the phone on that same screen. i haven't messed with the phone at all(locked bootloader,S-On etc.) so i'm clueless about what to do.
here' are the details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.631.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4144mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
and here is the error when trying to get into RUU mode :
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) Start Verify: 3
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
can anyone please help? is it bricked?
thanks alot in advance!

H1PpoN said:
hello XDA community,
i have a weird problem with my m7. one day after a reboot the phone just didn't boot and went straight to bootloader. i've tried installing original RUU, and after rebooting bootloader the phone just didn't came back on and the RUU failed to proceed. when holding PWR+DOWN buttons , i've managed to get to HBOOT menu but every choice i make there freezes the phone on that same screen. i haven't messed with the phone at all(locked bootloader,S-On etc.) so i'm clueless about what to do.
here' are the details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.631.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4144mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
and here is the error when trying to get into RUU mode :
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(876): error 2
(bootloader) Start Verify: 3
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
can anyone please help? is it bricked?
thanks alot in advance!
Click to expand...
Click to collapse
What RUU did you try to run and where did you get it?
See if you can use this procedure to do a factory reset:
Performing a factory reset using hardware buttons​If you can’t turn HTC One on or access settings, you can still perform a factory reset by using the hardware buttons on HTC One.
Important: The Fast boot option in Settings > Power must not be selected.
> Press and hold the VOLUME DOWN button, and then press and hold the POWER button.
> Wait for the screen with the three Android images to appear, and then release the POWER and VOLUME DOWN buttons.
> Press VOLUME DOWN to select FACTORY RESET, and then press the POWER button.
You might try this post: http://forum.xda-developers.com/showthread.php?t=2770684

majmoz said:
What RUU did you try to run and where did you get it?
See if you can use this procedure to do a factory reset:
Performing a factory reset using hardware buttons​If you can’t turn HTC One on or access settings, you can still perform a factory reset by using the hardware buttons on HTC One.
Important: The Fast boot option in Settings > Power must not be selected.
> Press and hold the VOLUME DOWN button, and then press and hold the POWER button.
> Wait for the screen with the three Android images to appear, and then release the POWER and VOLUME DOWN buttons.
> Press VOLUME DOWN to select FACTORY RESET, and then press the POWER button.
You might try this post: http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Thank you for the reply!
i've tried this method of factory reset - as i said - after pressing PWR button when factory reset highlighted, the phone freezes and i have to hard reset it (long press pwr button for ~20 sec).
i've got the RUU from here : http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/

H1PpoN said:
Thank you for the reply!
i've tried this method of factory reset - as i said - after pressing PWR button when factory reset highlighted, the phone freezes and i have to hard reset it (long press pwr button for ~20 sec).
i've got the RUU from here : http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Click to expand...
Click to collapse
You would not be able to run that RUU since it is a lower version than your phone. You are S-ON and can only run RUU and firmware that are the same version or higher. I don't think there is a RUU for your version.

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?

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?

Upgrade to Android 10 with my Mi A2 resulted on a bootloop.

Hello everyone. I have a Mi A2. There's been like a week ago or more that popped out on my phone an update to Android 10. I downloaded it, and when i pressed to reboot the system, the phone tried to boot but failed. When i put the phone to charge, it starts to bootloop. When it's not charging, it tries to boot one time and then turns off. I can get to Fastboot thru volume down + power buttons, but it gets stuck on the rabbit screen fixing the android robot. I've downloaded ADB, XiaomiFlash, the ROMs, all the stuff to recover or format the system. All commands with fastboot give me errors. I can't change the partition to "b" 'cause it says that it is in "lock state". When i try to unlock it (fastboot flashing unlock_critical), it says that Flashing Unlock it's not allowed. I've been like close to 6 hours on the pc today trying to fix this **** and tried almost everything. Can anyone help me? I saw some things on YouTube but it would require me to open the phone, but i don't have the tools, neither can buy them ('cause COVID-19). I'm not feeling tempted to send the phone to someone to fix it. Neither wan't to buy a new one. It was a system update, for christ sakes.

You could read this forum and get answers - bootloops are often after OTA, especially with OTA to still buggy Android Q.
So, summarizing answers you could find here:
1. AndroidOne for MiA2 uses A/B partitioning scheme, developed specifically to automatically return to previously installed Android version (in X slot) after OTA update to Y slot fails.
So You are to continue rebooting (bootlooping) with external power ON, until phone reboots to opposite slot. People wrote that extracting SIM helps to minimize number of reboots.
2. Switching slots via fastboot command, as well as flashing, is blocked until phone is fully unlocked (has unlocked boot and critical partitions). Only information command work, e.g. "fastboot getvar {...}".
3. Unlock is enabled only if phone has "OEM unlock" allowed in developers' options.
4. Without unlock, and being unable (or not patient enough) to reboot to previous slot, the only method left is disassembling phone and using TestPoint/Edl method.
Having written this, I expect that you will search for used keywords in these forums and the net, - and thus will do your homework yourself, - or bring phone to service.

There is a way that it seems to work holding the +/- button and power at the same time, it can make the phone change slots

Aerobatic said:
You could read this forum and get answers - bootloops are often after OTA, especially with OTA to still buggy Android Q.
So, summarizing answers you could find here:
1. AndroidOne for MiA2 uses A/B partitioning scheme, developed specifically to automatically return to previously installed Android version (in X slot) after OTA update to Y slot fails.
So You are to continue rebooting (bootlooping) with external power ON, until phone reboots to opposite slot. People wrote that extracting SIM helps to minimize number of reboots.
2. Switching slots via fastboot command, as well as flashing, is blocked until phone is fully unlocked (has unlocked boot and critical partitions). Only information command work, e.g. "fastboot getvar {...}".
3. Unlock is enabled only if phone has "OEM unlock" allowed in developers' options.
4. Without unlock, and being unable (or not patient enough) to reboot to previous slot, the only method left is disassembling phone and using TestPoint/Edl method.
Having written this, I expect that you will search for used keywords in these forums and the net, - and thus will do your homework yourself, - or bring phone to service.
Click to expand...
Click to collapse
First of all, thanks for answering so quickly. I was so stressed out after spending + than 6 hours at night, i know nothing about these stuff, so i had to start from 0.
1. I didn't knew that the looping was the phone trying to get back to the previous stable system. Right now, i've put it with external power on and took out the SIM. Will let there for a while.
2. Later i'll give you the information about "getvar", but i've tried that already yesterday, it was getting me some kind of unknown error.
3. Yes, almost all videos on YouTube guide people thru this part, but since i can't access developer's option cause the phone won't boot, it's impossible for me to do that.
4. I will continue searching. Also will try to buy a tool to fix it myself.

jeangraff30 said:
There is a way that it seems to work holding the +/- button and power at the same time, it can make the phone change slots
Click to expand...
Click to collapse
Thanks for aswering. I've already tried that, no response. :crying:

your phone will only be with test point, when it works again leave the bootloader option enabled, so you can make the phone work again when there is a problem

Hello everyone. I've got an update. I've plugged the phone in fastboot mode without SIM (idk if that's the cause) and manage to get a result on getvar all.
(bootloader) crc:1
(bootloader) anti:1
(bootloader) token:8O5E0UEyE3RmcpC88tTv0VrHObU=
(bootloader) hw-revision:10000
(bootloader) unlocked:no
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4300
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xBB77F7E00
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-size:vendor_b: 0x80000000
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-size:vendor_a: 0x80000000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xC0000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xC0000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x4000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x4000000
(bootloader) partition-type:minidump:raw
(bootloader) partition-size:minidump: 0x8000000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b: 0xC000000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a: 0xC000000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-typeersistbak:raw
(bootloader) partition-sizeersistbak: 0x2000000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x4000000
(bootloader) partition-type:mdtp_b:raw
(bootloader) partition-size:mdtp_b: 0x2000000
(bootloader) partition-type:mdtp_a:raw
(bootloader) partition-size:mdtp_a: 0x2000000
(bootloader) partition-type:bk1:raw
(bootloader) partition-size:bk1: 0x700000
(bootloader) partition-type:bluetooth_b:raw
(bootloader) partition-size:bluetooth_b: 0x100000
(bootloader) partition-type:dsp_b:raw
(bootloader) partition-size:dsp_b: 0x1000000
(bootloader) partition-type:dsp_a:raw
(bootloader) partition-size:dsp_a: 0x1000000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x800000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x800000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x800000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x800000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x400000
(bootloader) partition-type:xbl_b:raw
(bootloader) partition-size:xbl_b: 0x380000
(bootloader) partition-type:xbl_a:raw
(bootloader) partition-size:xbl_a: 0x380000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:bluetooth_a:raw
(bootloader) partition-size:bluetooth_a: 0x100000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b: 0x100000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a: 0x100000
(bootloader) partition-type:mdtpsecapp_b:raw
(bootloader) partition-size:mdtpsecapp_b: 0x400000
(bootloader) partition-type:mdtpsecapp_a:raw
(bootloader) partition-size:mdtpsecapp_a: 0x400000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b: 0x400000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a: 0x400000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b: 0x100000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a: 0x100000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:abl_b:raw
(bootloader) partition-size:abl_b: 0x100000
(bootloader) partition-type:abl_a:raw
(bootloader) partition-size:abl_a: 0x100000
(bootloader) partition-type:cmnlib64_b:raw
(bootloader) partition-size:cmnlib64_b: 0x100000
(bootloader) partition-type:cmnlib_b:raw
(bootloader) partition-size:cmnlib_b: 0x100000
(bootloader) partition-type:cmnlib64_a:raw
(bootloader) partition-size:cmnlib64_a: 0x100000
(bootloader) partition-type:cmnlib_a:raw
(bootloader) partition-size:cmnlib_a: 0x100000
(bootloader) partition-typemic_b:raw
(bootloader) partition-sizemic_b: 0x80000
(bootloader) partition-typemic_a:raw
(bootloader) partition-sizemic_a: 0x80000
(bootloader) partition-type:hyp_b:raw
(bootloader) partition-size:hyp_b: 0x80000
(bootloader) partition-type:hyp_a:raw
(bootloader) partition-size:hyp_a: 0x80000
(bootloader) partition-type:rpm_b:raw
(bootloader) partition-size:rpm_b: 0x80000
(bootloader) partition-type:rpm_a:raw
(bootloader) partition-size:rpm_a: 0x80000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-typeraw
(bootloader) partition-size 0x20000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-size:vbmeta_b: 0x10000
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-size:vbmeta_a: 0x10000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x5000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x8000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x2000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:switch:raw
(bootloader) partition-size:switch: 0x2000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:3305a5d
(bootloader) product:jasmine
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.649s
Also, i've managed to (idk how exactly either, i was pressing the buttons) freeze the androidone screen while bootloop.

Hey everyone! I've managed to fix my phone thru test point. Like in this video: https://www.youtube.com/watch?v=5JaSIKoDDGg&t=6s
For anyone trying to do this, if u are getting errors on XiaomiFlash, move the ROM folder to C:/ and rename it to "ROM".
Also, the problematic update was the november one, that caused the bootloop. I'll probably won't be able to update my phone anymore right?
Thanks to everyone!

Regular OTA updates still possible
Hey, went through something similar back in early 2019. Of course you can update your phone. Allow unlocking and debugging and then wait if they pull and fix the OTA update and try again and if that does not happen wait till they release a stable fastboot ROM image that is already updated past the current dodgy update and manually update your phone and then continue with regular OTA updates.
good luck!

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.