Guys please help... I'm desperate right now...
My father got an AT&T Moto E, I tried to flash 6.0 on it, The bootloader.img file flashed but nothing else flashed from that 6.0 firmwaRE.
I realised AT&T wont allow us to do that so I left the phone on 5.1...
Today, a security patch update dropped for the phone... I insalled it but it turned off and it can't boot anymore.
I can enter bootloader and use fastboot commands, but when I try to flash the stock firmware from AT&T using fastboot it says
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
and the bootloader log says
Invalid PIV signed system image
It seems to be a problem with signature verification or something related to it...
Im trying to flash this fitmware: SURNIA_ATT_5.1_LPI23.29-18.9-2_cid1_subsidy-ATT_CFC.xml.zip which is the last one available for this AT&T variant.
So, is there a way to flash this AT&T variant? I also tried RSD Lite but no success on recognizing the phone..
Any help will be appreciated... thanks in advance..
What is running on your XT1527 now (stock/factory rom 5.1 compatible for AT&T) ?? Bootloader status ?
One of my SIL has this and I just updated her's with the latest update, download OTA and just flashed/upgraded directly, took about 20 minutes - easy & didn't have any issues with it at all, nothing (as described). She is on T-Mobile and all is good.
Backup all important data & contents, especially those on the mSD card/storage partition, be sure to do a full wipe/factory reset before trying the upgrade. If necessary, do a basic setup as a new device, wait a little while for everything to be updated & settle down, reboot it for good measures & then do the system check for upgrade.
Of course, my own XT1521 not getting this & running Nougat 7.1.1 nicely - unlike the XT1527 that can't be rooted to run custom Rom's.
Letitride said:
What is running on your XT1527 now (stock/factory rom 5.1 compatible for AT&T) ?? Bootloader status ?
One of my SIL has this and I just updated her's with the latest update, download OTA and just flashed/upgraded directly, took about 20 minutes - easy & didn't have any issues with it at all, nothing (as described). She is on T-Mobile and all is good.
Backup all important data & contents, especially those on the mSD card/storage partition, be sure to do a full wipe/factory reset before trying the upgrade. If necessary, do a basic setup as a new device, wait a little while for everything to be updated & settle down, reboot it for good measures & then do the system check for upgrade.
Of course, my own XT1521 not getting this & running Nougat 7.1.1 nicely - unlike the XT1527 that can't be rooted to run custom Rom's.
Click to expand...
Click to collapse
This device was on 5.1 stock... as it is from AT&T, bootloader is locked. I can enter fastboot mode, so it is not bricked, but when I try to reflash the latest AT&T firmware available for this phone it keeps saying that prevalidation error and invalid piv signed system image, even though I have the exact same firmware that was running before the OTA dropped...
As the AT&T webpage for XT1527 states, this is the OTA I accepted on the device:
Release date: December 16, 2016
Android version: 5.1
Baseband version: M8916_2020602.05.03.21.07R
Build number: LPI23.29-18.9-6
File size: 48.38MB
System version: 23.211.6.en.US
But when I run the command mfastboot getvar all, the phone shows it has the LPI23.29-18.9-2 build number installed! So, something went wrong during the update that corrupted (I guess) the kernel, because the device can't boot up normally. Just stays as it was off. It can access fastboot mode via vol down + power buttons. Also, when you plug it to the wall charger, it shows the offline charging screen, with the big battery icon and everything...
So, should I wait for the official AT&T firmware image for this OTA? Since I cant flash anything on it because of that prevalidation error crap!
LOG OF THE PHONE
C:\XT1527>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-80.10
(bootloader) product: surnia
(bootloader) board: surnia
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Micron REV=06 PRV=12 TYPE=17
(bootloader) ram: 1024MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8916 ES1.0
(bootloader) serialno: TA3970BWQA
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: A5D76A1500000000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: Hidden
(bootloader) meid:
(bootloader) date: 01-09-2016
(bootloader) sku: XT1527
(bootloader) iccid: 89014103278783002002
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Dec 16 20: 0: 5 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/surnia_att/surnia_umts:5.
(bootloader) ro.build.fingerprint[1]: 1/LPIS23.29-18.9-2/2:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.201.2.surnia_att.
(bootloader) ro.build.version.full[1]: att.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.00.02.032.013
(bootloader) version-baseband[0]: M8916_2020602.05.03.21.07R SURNIA_ATT_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.49-gf2d7a94 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld52) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Mon Mar 28 02:49:46 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-V80.10-0-g8f1d925
(bootloader) rpm.git: git=MBM-NG-V80.10-0-g099cb06
(bootloader) tz.git: git=MBM-NG-V80.10-0-g434e28a
(bootloader) hyp.git: git=MBM-NG-V80.10-0-g434e28a
(bootloader) aboot.git: git=MBM-NG-V80.10-0-g43dddc5
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-typeDR: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:sec: raw
(bootloader) partition-type:factorytune1: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:modemst1: raw
(bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw
(bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw
(bootloader) partition-type:fsc: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:factorytune2: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-typeem: raw
(bootloader) partition-type:carrier: ext4
(bootloader) partition-type:system: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x0000000004000000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-sizeDR: 0x0000000000008000
(bootloader) partition-size:aboot: 0x0000000000100000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000007d000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:sec: 0x0000000000004000
(bootloader) partition-size:factorytune1: 0x0000000000371000
(bootloader) partition-sizeadA: 0x00000000001af000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:abootBackup: 0x0000000000100000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000007d000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-sizeadB: 0x000000000048f000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000180000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:logo: 0x0000000000400000
(bootloader) partition-size:clogo: 0x0000000000400000
(bootloader) partition-sizeersist: 0x0000000000800000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-size:boot: 0x0000000002000000
(bootloader) partition-size:recovery: 0x0000000001ffc000
(bootloader) partition-size:factorytune2: 0x0000000000a0e000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-sizeadC: 0x0000000000380000
(bootloader) partition-size:sp: 0x0000000001000000
(bootloader) partition-size:keystore: 0x0000000001000000
(bootloader) partition-sizeem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:system: 0x0000000071000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-size:userdata: 0x000000013ffe0000
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: att
all: listed above
finished. total time: 0.275s
MarckozZ said:
This device was on 5.1 stock... as it is from AT&T, bootloader is locked. I can enter fastboot mode, so it is not bricked, but ...
So, should I wait for the official AT&T firmware image for this OTA? Since I cant flash anything on it because of that prevalidation error crap! ...
Click to expand...
Click to collapse
With the bootloader locked, there's not much you can do, whether the downloaded update is corrupted or not - not as easy to find & erase that "update" and start over. Wait for a newer OTA and then, cross your fingers & cycle thru the cautions & warnings; and, hit that "Go" or "Yes" bottom and hopefully the magic will take care of itself.
My SIL's XT1527 did fine with the AT&T update, and, she's on T-Mo USA network - so far so good, no complaints and just works.
Letitride said:
With the bootloader locked, there's not much you can do, whether the downloaded update is corrupted or not - not as easy to find & erase that "update" and start over. Wait for a newer OTA and then, cross your fingers & cycle thru the cautions & warnings; and, hit that "Go" or "Yes" bottom and hopefully the magic will take care of itself.
My SIL's XT1527 did fine with the AT&T update, and, she's on T-Mo USA network - so far so good, no complaints and just works.
Click to expand...
Click to collapse
Could you help me with something? Can you tell me which build number does her phone have right now? Go to Settings > About phone and please tell me the build number and build date under kernel version... And if you have time, use fastboot and /fastboot getvar all, so I can see the exact version... maybe that can help me figure this out! Thanks in advance...
Here's the link to the screenshot of her XT1527 after it updated - I took a screenshot afterward, just in case.
https://goo.gl/photos/38HQicN1bq6KzQoC8
It looked identical to what you have ?? Her Moto E is working just fine as I would've heard otherwise, (she's on T-Mobile) been a few days now. I won't get a chance to do anything or run those command until this Saturday when we gather. I suspect your download might've been corrupted and/or somehow one of the extracted file or those on the device had error.
So glad that mine (as a backup) is XT1521 and bootloader unlocked, now running custom Nougat 7.1.1 (ResurrectionRemix) and it's on T-Mobile also. Maybe time to look for one of these pre-owned ones on eBay.
Letitride said:
Here's the link to the screenshot of her XT1527 after it updated - I took a screenshot afterward, just in case.
https://goo.gl/photos/38HQicN1bq6KzQoC8
It looked identical to what you have ?? Her Moto E is working just fine as I would've heard otherwise, (she's on T-Mobile) been a few days now. I won't get a chance to do anything or run those command until this Saturday when we gather. I suspect your download might've been corrupted and/or somehow one of the extracted file or those on the device had error.
So glad that mine (as a backup) is XT1521 and bootloader unlocked, now running custom Nougat 7.1.1 (ResurrectionRemix) and it's on T-Mobile also. Maybe time to look for one of these pre-owned ones on eBay.
Click to expand...
Click to collapse
Thanks a LOT!! I'm looking forward to your meeting with your SIL LOL... My dad's had a different build number and kernel date, thats all. Everything else was the same..
Please, If you could do that command thing I'll be so thankful, so I can complete my research on what happened and how to fix this thing!
Up to now, all I have discovered is this:
* If you try to turn on the phone using the power button, the screen will stay off, as if it was hardbricked...
* To see some sign of life, the only way to turn this phone on is pressing vol down + power, so then I can enter fastboot mode.
* In fastboot mode I can't enter recovery mode: fastboot screen just freezes until you do the vol down + power combination. The same thing happens when you select "START" option in fastboot mode.As the screen freezes or stays off when trying to boot up, I assume that the kernel got corrupted.
* Only way to turn the phone off is selecting the POWER OFF option in fastboot. If the phone is off and I plug it into the wall charger, it will turn on showing the M logo as usual and then the big battery charging, but thats all. (Who is in charge of the offline battery animation? logo.img? boot.img? bootloader.img?)
* Flashing using fastboot.exe or mfastboot.exe doesn't help at all. Despite the fact I can flash bootloader.img and logo.img, I can't flash gpt.bin nor boot.img or the system sparsechunks due to "Preflash validation failed" error, even though I have the exact same firmware the phone had before the OTA (and it is the same firmware that the phone says it has installed when running the getvar all command). I'm still able to run erase userdata and erase cache commands with an OKAY as answer, but still the phone doesn't boot up.
So... I'm trapped with this situation! I gave my dad my Moto G3 as a compensation LOL!
Please, remember to do the /fastboot getvar all to your SIL's phone this saturday! Please!!!
Related
So, last night i tried to install LineageOS on a surnia, flashed TWRP using the official file twrp-3.2.1-0-surnia.img i tried to make a factory reset before installing rom and gapps and told me it couldnt mount anything so i formated data tipyng yes and all that worked, i installed the rom + gapps, all good, after that it couldnt boot i was stuck on bootloader. So i downloaded a couple of stock roms and flashed them using the Stock Firmware Flasher from the forum, some of the roms boot up and everything works except gsm signal, i said some since no stock 6.0 rom has worked only 5.1 and 5.0.
This is what fastboot says:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-80.10
(bootloader) product: surnia
(bootloader) board: surnia
(bootloader) secure: no
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Samsung REV=07 PRV=0B TYPE=57
(bootloader) ram: 1024MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8916 ES1.0
(bootloader) serialno: NSYB210239
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: A63F150100000000000000000000
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1
(bootloader) max-download-size: 268435456
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Nov 11 10:36:33 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/surnia_retus/surnia_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPIS23.29-18.9-6/4:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.211.6.surnia_retu
(bootloader) ro.build.version.full[1]: s.retus.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.00.02.032.013
(bootloader) version-baseband: M8916_2020602.05.03.21.07B DFLT_FSG
(bootloader) kernel.version[0]: Linux version 3.10.49-g5f7e9895 (hudsonc
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Nov 11 03:51:20 CST 201
(bootloader) kernel.version[3]: 6
(bootloader) sbl1.git: git=MBM-NG-V80.10-0-g8f1d925
(bootloader) rpm.git: git=MBM-NG-V80.10-0-g099cb06
(bootloader) tz.git: git=MBM-NG-V80.10-0-g434e28a
(bootloader) hyp.git: git=MBM-NG-V80.10-0-g434e28a
(bootloader) aboot.git: git=MBM-NG-V80.10-0-g43dddc5
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-type:DDR: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:sec: raw
(bootloader) partition-type:factorytune1: raw
(bootloader) partition-type:padA: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-type:padB: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:modemst1: raw
(bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw
(bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw
(bootloader) partition-type:fsc: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-type:persist: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:factorytune2: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:padC: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-type:oem: raw
(bootloader) partition-type:carrier: ext4
(bootloader) partition-type:system: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x0000000004000000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-size:DDR: 0x0000000000008000
(bootloader) partition-size:aboot: 0x0000000000100000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000007d000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:sec: 0x0000000000004000
(bootloader) partition-size:factorytune1: 0x0000000000371000
(bootloader) partition-size:padA: 0x00000000001af000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:abootBackup: 0x0000000000100000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000007d000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-size:padB: 0x000000000048f000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000180000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:logo: 0x0000000000400000
(bootloader) partition-size:clogo: 0x0000000000400000
(bootloader) partition-size:persist: 0x0000000000800000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-size:boot: 0x0000000002000000
(bootloader) partition-size:recovery: 0x0000000001ffc000
(bootloader) partition-size:factorytune2: 0x0000000000a0e000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:padC: 0x0000000000380000
(bootloader) partition-size:sp: 0x0000000001000000
(bootloader) partition-size:keystore: 0x0000000001000000
(bootloader) partition-size:oem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:system: 0x0000000071000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-size:userdata: 0x000000013efe0000
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.416s
Heres a pic on the phone in BL mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And heres in android showing imei 0 after tying *#06*
These are the roms ive tried so far:
- SURNIA_USC_5.1_LPI23.29-15_cid9_subsidy-DEFAULT_CFC.xml - My first chice since i remember something like "surnia_usc" on CPUz when i received the phone.
- SURNIA_RETUS_5.1_LPIS23.29-18.9-2_cid9_subsidy-DEFAULT_CFC.xml - The last i installed in wich i am right now.
- XT1524_RETGBALL_MOTOE2(4G-LTE)_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml
- XT1524_SURNIA_RETES_6.0_MPI24.65-39_cid7_subsidy-DEFAULT_CFC.xml
- XT1527_SURNIA_AMXLA_6.0_MPI24.65-39_cid12_subsidy-DEFAULT_CFC.xml - Wont boot, stays forever on boot animation.
- XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml - Wont boot, stays forever on boot animation
And also tried this modem:
xt1526_BasebandUpdater - Intall via TWRP
Sorry for my english, greetings from venezuela.
You should try to aquire a modem.img and fsg.mbn that someone with the same device has pulled from their already activated device. It should restore your imei. They won't help if they haven't been pulled from an already activated device.
Edit: you should not have flashed the baseband updater for an xt1526. That is a cdma device, your is gsm and not compatible.
Edit: maybe look here: https://forum.xda-developers.com/moto-e-2015/general/moto-e-2015-modems-t3296044
Punktilious said:
You should try to aquire a modem.img and fsg.mbn that someone with the same device has pulled from their already activated device. It should restore your imei. They won't help if they haven't been pulled from an already activated device.
Edit: you should not have flashed the baseband updater for an xt1526. That is a cdma device, your is gsm and not compatible.
Edit: maybe look here: https://forum.xda-developers.com/moto-e-2015/general/moto-e-2015-modems-t3296044
Click to expand...
Click to collapse
Thanks, since i have no idea what XT.... is this one ive throw pretty much anything to it, as yo ucan see in the pics is like a pre-production surnia.
I also tried those modems in the thread you provided, no luck. Right now the phone has some Android 6.0 stock rom (cant remember wich one) is rooted and i even tried xposed and all his imei modules, still no signal. Everything else works
mauriciognr said:
Thanks, since i have no idea what XT.... is this one ive throw pretty much anything to it, as yo ucan see in the pics is like a pre-production surnia.
I also tried those modems in the thread you provided, no luck. Right now the phone has some Android 6.0 stock rom (cant remember wich one) is rooted and i even tried xposed and all his imei modules, still no signal. Everything else works
Click to expand...
Click to collapse
Use a terminal emulator, you have to be rooted and type su, then getprop and copy and paste the output in a text file and upload it here.
Same problem from last one year on my moto e xt1527,no signal
Never mind that getprop output. Your device is a retail us xt1527.
Edit: I may be wrong, that might be showing retus because you flashed that firmware.
---------- Post added at 04:44 PM ---------- Previous post was at 04:44 PM ----------
gsohi2011 said:
Same problem from last one year on my moto e xt1527,no signal
Click to expand...
Click to collapse
Did you fix it?
Edit: maybe @MotoJunkie01 can help?
This should be the firmware: https://firmware.center/firmware/Mo...23.29-18.9-2_cid9_subsidy-DEFAULT_CFC.xml.zip What you said above that you tried last.
No man not yet
---------- Post added at 04:53 PM ---------- Previous post was at 04:48 PM ----------
No man not yet
@mauriciognr what carrier do you have?
I see part of your problem. Your using the official TWRP. squid2's twrp works better. https://www.google.com/url?sa=t&sou...ChAB&usg=AOvVaw3gAWwS-4f_K0-InSF5z9RY&cf=1[/url]
Eeit: Did you try: fastboot erase modem st1 and fastboot erase modem st2? While on stock, after flashing the modem not a custom rom.
Or: fastboot oem fb_mode_clear after flashing the whole stock firmware. If rhose commands weren't ran when you flashed with the flash tool, that can also cause problems.
Punktilious said:
@mauriciognr what carrier do you have?
I see part of your problem. Your using the official TWRP. squid2's twrp works better. https://www.google.com/url?sa=t&sou...ChAB&usg=AOvVaw3gAWwS-4f_K0-InSF5z9RY&cf=1[/url]
Eeit: Did you try: fastboot erase modem st1 and fastboot erase modem st2? While on stock, after flashing the modem not a custom rom.
Or: fastboot oem fb_mode_clear after flashing the whole stock firmware. If rhose commands weren't ran when you flashed with the flash tool, that can also cause problems.
Click to expand...
Click to collapse
Ive been using the firmware flasher to install stock roms, and im pretty sure ive read fastboot erase modem st1 and fastboot erase modem st2 on the log.
I also tried flashing modems from here with no luck whatsoever.
Anyway im gonna try to flash another stock rom and after that run fastboot oem fb_mode_clear
Ok so.
- I flashed XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml and ran fastboot oem fb_mode_clear... no signal.
- Tried to install the TWRP you mentioned but it fails to boot to recovery, had to flash official twrp.
- I flashed XT1527-AMXLA_6.0.zip modem and still no sginal.
- I rooted with SuperSu and installed terminal emulator to run getprop.
View attachment 4403899
Flashed TWRP now I have no recovery at all and it just reboots when I try going to recovery on Moto G Power.
I got the zip from the Moto TWRP thread and it's twrp 3.5 supposedly the latest.
I've been flashing it with the file on my PC "fastboot flash recovery c:\recovery.img" where can I place the recovery on my phone so I can flash it from the phone. I don't know the path for the phone directories so can't qualify its pathname on the phone.
piiman said:
Flashed TWRP now I have no recovery at all and it just reboots when I try going to recovery on Moto G Power.
I got the zip from the Moto TWRP thread and it's twrp 3.5 supposedly the latest.
I've been flashing it with the file on my PC "fastboot flash recovery c:\recovery.img" where can I place the recovery on my phone so I can flash it from the phone. I don't know the path for the phone directories so can't qualify its pathname on the phone.
Click to expand...
Click to collapse
I'm having something close to this, though mine is blackview. I'm guessing this is a new problem as mine happen about a week now and I've gat sleepless night ransacking the internet with no success yet.
I unlocked my BV9600pro with Android8.1 bootloader using fastboot then flashed on it TWRP before I learnt I just could have patched the Boot.img and flash in to get root, which I’ve done, now the device is rooted and when I’m trying to boot to recovery it display Orange State and goes to No Command screen.
I have tried some keys combinations on the No Command screen like the Vol+ and Power button but the device booted to bootloader options and when I selected recovery mode again I was back to Orange State and to no command, then I tried vol- and power button but that booted to Orange State then normal boot.
I edited lk.img and flashed on my bv9600pro it just remove the Orange State Display but won't still give access to recovery, I had to reflash on the device the stock lk.img and stock recovery.img and still can't boot to recovery. I'm guessing it's all as a result of the unlocking. Please any other way to fix this to enable me access recovery with the root?
I actually want to have the TWRP on the device to allow Nandroid backup and eaisily flashing on the device my custom ROMs.
piiman said:
Flashed TWRP now I have no recovery at all and it just reboots when I try going to recovery on Moto G Power.
I got the zip from the Moto TWRP thread and it's twrp 3.5 supposedly the latest.
I've been flashing it with the file on my PC "fastboot flash recovery c:\recovery.img" where can I place the recovery on my phone so I can flash it from the phone. I don't know the path for the phone directories so can't qualify its pathname on the phone.
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
Rukkyakakporo said:
I'm having something close to this, though mine is blackview. I'm guessing this is a new problem as mine happen about a week now and I've gat sleepless night ransacking the internet with no success yet.
I unlocked my BV9600pro with Android8.1 bootloader using fastboot then flashed on it TWRP before I learnt I just could have patched the Boot.img and flash in to get root, which I’ve done, now the device is rooted and when I’m trying to boot to recovery it display Orange State and goes to No Command screen.
I have tried some keys combinations on the No Command screen like the Vol+ and Power button but the device booted to bootloader options and when I selected recovery mode again I was back to Orange State and to no command, then I tried vol- and power button but that booted to Orange State then normal boot.
I edited lk.img and flashed on my bv9600pro it just remove the Orange State Display but won't still give access to recovery, I had to reflash on the device the stock lk.img and stock recovery.img and still can't boot to recovery. I'm guessing it's all as a result of the unlocking. Please any other way to fix this to enable me access recovery with the root?
I actually want to have the TWRP on the device to allow Nandroid backup and eaisily flashing on the device my custom ROMs.
Click to expand...
Click to collapse
more likely the unofficial twrp. The unlocking shouldn't cause issues since its unlockable by Moto itself. .
Mine seem to flash the recovery very quickly (under 2 secs) so I'm wondering if I have the proper rights and it isn't actually writing the .img file but just guessing.
thanks for the reply
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-borneo_retail-bfe8cf6b47-201209
(bootloader) product: borneo
(bootloader) board: borneo
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4x DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: ZY22BVJSBS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 6F15AE13
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 804474880
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 356891111389229
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 02-28-2021
(bootloader) sku: XT2117-4
(bootloader) carrier_sku: XT2117-4
(bootloader) battid: SB18C77591
(bootloader) battery-voltage: 4327
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retus
(bootloader) ro.build.fingerprint[0]: motorola/borneo_retail/borneo:10/Q
(bootloader) ro.build.fingerprint[1]: ZB30.Q4-43-35/7ad68:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.8.15.r1-06600-KAMORTA.0
(bootloader) version-baseband: HA10_18.534.02.57R BORNEO_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.19.95-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.16 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Wed Dec 9 02:44
(bootloader) kernel.version[3]: :38 CST 2020
(bootloader) git:xbl: MBM-3.0-borneo_retail-9304f2ad5-201209
(bootloader) git:xbl_config: MBM-3.0-borneo_retail-9304f2ad5-201209
(bootloader) git:abl: MBM-3.0-borneo_retail-bfe8cf6b47-201209
(bootloader) git:rpm: MBM-3.0-borneo_retail-6b0a297-201209
(bootloader) git:tz: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:hyp: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:devcfg: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:keymaster: MBM-3.0-borneo_retail-3b8c7a4-201209
(bootloader) git:storsec: MBM-3.0-borneo_retail-3b8c7a4-201209
(bootloader) git:uefisecapp: MBM-3.0-borneo_retail-3b8c7a4-201209
(bootloader) gitrov: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:qupfw: MBM-3.0-borneo_retail-f07d142-201209
(bootloader) frp-state: protected (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86870
(bootloader) primary-display: djn_nt36672a_video_display
(bootloader) secondary-display:
all: listed above
finished. total time: 0.091s
piiman said:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-borneo_retail-bfe8cf6b47-201209
(bootloader) product: borneo
(bootloader) board: borneo
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4x DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: ZY22BVJSBS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 6F15AE13
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 804474880
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 356891111389229
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 02-28-2021
(bootloader) sku: XT2117-4
(bootloader) carrier_sku: XT2117-4
(bootloader) battid: SB18C77591
(bootloader) battery-voltage: 4327
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retus
(bootloader) ro.build.fingerprint[0]: motorola/borneo_retail/borneo:10/Q
(bootloader) ro.build.fingerprint[1]: ZB30.Q4-43-35/7ad68:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.8.15.r1-06600-KAMORTA.0
(bootloader) version-baseband: HA10_18.534.02.57R BORNEO_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.19.95-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.16 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Wed Dec 9 02:44
(bootloader) kernel.version[3]: :38 CST 2020
(bootloader) git:xbl: MBM-3.0-borneo_retail-9304f2ad5-201209
(bootloader) git:xbl_config: MBM-3.0-borneo_retail-9304f2ad5-201209
(bootloader) git:abl: MBM-3.0-borneo_retail-bfe8cf6b47-201209
(bootloader) git:rpm: MBM-3.0-borneo_retail-6b0a297-201209
(bootloader) git:tz: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:hyp: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:devcfg: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:keymaster: MBM-3.0-borneo_retail-3b8c7a4-201209
(bootloader) git:storsec: MBM-3.0-borneo_retail-3b8c7a4-201209
(bootloader) git:uefisecapp: MBM-3.0-borneo_retail-3b8c7a4-201209
(bootloader) gitrov: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:qupfw: MBM-3.0-borneo_retail-f07d142-201209
(bootloader) frp-state: protected (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86870
(bootloader) primary-display: djn_nt36672a_video_display
(bootloader) secondary-display:
all: listed above
finished. total time: 0.091s
Click to expand...
Click to collapse
Where did you find Twrp for borneo?
Rukkyakakporo said:
I'm having something close to this, though mine is blackview. I'm guessing this is a new problem as mine happen about a week now and I've gat sleepless night ransacking the internet with no success yet.
I unlocked my BV9600pro with Android8.1 bootloader using fastboot then flashed on it TWRP before I learnt I just could have patched the Boot.img and flash in to get root, which I’ve done, now the device is rooted and when I’m trying to boot to recovery it display Orange State and goes to No Command screen.
I have tried some keys combinations on the No Command screen like the Vol+ and Power button but the device booted to bootloader options and when I selected recovery mode again I was back to Orange State and to no command, then I tried vol- and power button but that booted to Orange State then normal boot.
I edited lk.img and flashed on my bv9600pro it just remove the Orange State Display but won't still give access to recovery, I had to reflash on the device the stock lk.img and stock recovery.img and still can't boot to recovery. I'm guessing it's all as a result of the unlocking. Please any other way to fix this to enable me access recovery with the root?
I actually want to have the TWRP on the device to allow Nandroid backup and eaisily flashing on the device my custom ROMs.
Click to expand...
Click to collapse
This is a forum for Moto G Power (2021)
Try asking in
General Questions and Answers
This forum is for all questions, big or small, you might have. Please read the rules in this forum before submitting any Q&A.This forum is a Questions section, which means each reply is treated as an answer that can be up/down voted by the community. Then, the original poster can choose the best...
forum.xda-developers.com
sd_shadow said:
Where did you find Twrp for borneo?
Click to expand...
Click to collapse
don't remember but it was from XDA and I think it was this thread https://forum.xda-developers.com/t/sofia-p-r-recovery-wip-twrp-3-4-0-0.4128353/ and the zip was
twrp-3.5.0-0-rav-sofia.img <- most recent
piiman said:
don't remember but it was from XDA and I think it was this thread https://forum.xda-developers.com/t/sofia-p-r-recovery-wip-twrp-3-4-0-0.4128353/ and the zip was
twrp-3.5.0-0-rav-sofia.img <- most recent
Click to expand...
Click to collapse
That's not for your device
sd_shadow said:
That's not for your device
Click to expand...
Click to collapse
Then which is? Trying to find this stuff is a nightmare. and is there a way to go back?
piiman said:
Then which is? Trying to find this stuff is a nightmare. and is there a way to go back?
Click to expand...
Click to collapse
If you have a windows pc try LMSA'S flash rescue
Download firmware with lmsa
Then flash with lmsa or just find the firmware folder and reflash recovery.img
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
If you just want to root.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
If you have a windows pc try LMSA'S flash rescue
Download firmware with lmsa
Then flash with lmsa or just find the firmware folder and reflash recovery.img
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
Will try later, thanks for your insight.
sd_shadow said:
If you just want to root.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Was hoping to use twrp for that but I guess I'll have to do it this way. Thanks
sd_shadow said:
If you have a windows pc try LMSA'S flash rescue
Download firmware with lmsa
Then flash with lmsa or just find the firmware folder and reflash recovery.img
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
went looking for this and when I enter the serial number it says no products found. Now what? I copied the serial number from the VAR's I posted above is that the correct serial number?
piiman said:
went looking for this and when I enter the serial number it says no products found. Now what? I copied the serial number from the VAR's I posted above is that the correct serial number?
Click to expand...
Click to collapse
No go direct to rescue, the serial thing is stupid
sd_shadow said:
No go direct to rescue, the serial thing is stupid
Click to expand...
Click to collapse
Thanks I'll give that a try
sd_shadow said:
No go direct to rescue, the serial thing is stupid
Click to expand...
Click to collapse
OK I have the firmware downloaded and it's in XML format. How can I get the recovery.img out of that so I can flash it?
piiman said:
OK I have the firmware downloaded and it's in XML format. How can I get the recovery.img out of that so I can flash it?
Click to expand...
Click to collapse
.xml is a text format, if you used lmsa it would be a folder, if you downloaded from somewhere else it will be a .zip
sd_shadow said:
.xml is a text format, if you used lmsa it would be a folder, if you downloaded from somewhere else it will be a .zip
Click to expand...
Click to collapse
I used LMSA and the xml file acts like a folder can I just copy it out of there?
Hello Everyone.
This is my first post so please if i did anything wrong or posted this in the wrong place please let me know.
I have a Moto G Pure that im trying to root. I have to unlock the bootloader first from what i gather. I downloaded the adb, fastboot and drivers for the phone installed everything and went on motos website and used there bootloader unlock string tool and it says "your device does not qualify for bootloader unlocking". Not sure why that's coming up? Does anyone know a work around by chance? Here is the Unlock Data, the sting I used and the getvar info.
C:\\Desktop\platform-tools>fastboot oem get_unlock_data
(bootloader) Unlock data:
(bootloader) 3A85832508840061#5A593232444C4B
(bootloader) 474433006D6F746F2067200000#F797
(bootloader) DDD03416481B0F85B69548533550013
(bootloader) 97C6CAAC01B02F6D820BD2048F29F#0
(bootloader) DF077A6F1E7E5E80000000000000000
OKAY [ 0.050s]
Finished. Total time: 0.052
3A85832508840061#5A593232444C4B474433006D6F746F2067200000#F797DDD03416481B0F85B6954853355001397C6CAAC01B02F6D820BD2048F29F#0DF077A6F1E7E5E80000000000000000
C:\\Desktop\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ellis_a-320aeee45-211101
(bootloader) product: ellis
(bootloader) board: ellis
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 4
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DX68MB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG N NVM DIE=512Mb M5=01 M6=07 M7=00 M8=0E
(bootloader) cpu: MT6762G
(bootloader) serialno: XXXXXXXXXX
(bootloader) cid: 0x0001
(bootloader) channelid: 0x88
(bootloader) uid: 0DF077A6F1E7E5E8000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-18-2021
(bootloader) sku: XT2163-6
(bootloader) carrier_sku: XT2163-6
(bootloader) battid: SB18D15249
(bootloader) iccid: 89012803320393497037
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 15 12:24:29 UTC 2022"
(bootloader) ro.build.fingerprint[0]: motorola/ellis_a/ellis:11/RRH31.Q3
(bootloader) ro.build.fingerprint[1]: -46-50-2/20fec:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.mtk: alps-mp-r0.mp1.tc2sp-V1.66
(bootloader) version-baseband: MT6762_TC2.PR2.SP.V8.2.P20.01.66.54R
(bootloader) kernel.version[0]: Linux version 4.19.127+ ([email protected]
(bootloader) kernel.version[1]: build) (Android (6443078 based on r38390
(bootloader) kernel.version[2]: 2) clang version 11.0.1 (https://android
(bootloader) kernel.version[3]: .googlesource.com/toolchain/llvm-project
(bootloader) kernel.version[4]: b397f81060ce6d701042b782172ed13bee898b7
(bootloader) kernel.version[5]: 9), LLD 11.0.1 (/buildbot/tmp/tmp6_m7QH
(bootloader) kernel.version[6]: b397f81060ce6d701042b782172ed13bee898b79
(bootloader) kernel.version[7]: )) #1 SMP PREEMPT Mon Nov 1 05:00:56 CDT
(bootloader) kernel.version[8]: 2021
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: attpre
(bootloader) current-slot: a
(bootloader) running-boot-lun: 1
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 1
(bootloader) slot-retry-count:_b: 7
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28D31556
(bootloader) is-userspace: no
(bootloader) is-logical:
(bootloader) snapshot-update-status: none
all: listed above
Finished. Total time: 0.078s
Any pointers would surly be appreciated. Been pulling my hair out. haha!
Thanks for reading!
-BB
@Biggitybaked
The model you have (XT2163-6) is the AT&T variant of the Moto G Pure. The carrier doesn't allow unlocking the bootloader.
With that said, you can give an unofficial MediaTek reverse engineering tool named MTKClient a try. Only proceed if you know what you're doing.
That's what I figured. Ill never buy as phone from a carrier again. Thank you for confirming. And ima look into that MTKClient and see if I can do it. Wish me luck. haha!
Have you tested the mtkclient, work ?
meegosgift said:
Have you tested the mtkclient, work ?
Click to expand...
Click to collapse
The main issue preventing mtk client from working seems to be this: I have no clue on how to make my XT2163-2 phone enter the MediaTek ... brom mode!
There's a program it may not technically be for your peticular phone, so not responsible for any damage or problems I'm just saying I think it's like mtk auth bypass tool, it can get you to brom mode,
But ... what are the prerequisites (along with that app from MediaTek) for making the phone enter brom mode? Without JTAG, serial interface or "test points". A way for mere mortals like me, to allow me to unlock the damn bootloader, which Motorola (aka Lenovo) was plotting with Verizons, to keep us, legitimate owners of their stupid phones, out of the bootloader...
how to boot to brom on this phone? anyone figured it out?
smihaila said:
The main issue preventing mtk client from working seems to be this: I have no clue on how to make my XT2163-2 phone enter the MediaTek ... brom mode!
Click to expand...
Click to collapse
When using mtk client, power off the phone and disconnect the usb. While off, hold both VOL - & VOL + then plug in the usb while the client is running. Mtk client will automatically recognize your device I've used the same method for all versions of mtk devices with 100% success. The partitions pull as bin files but i just use a converter to solve that issue
yah2000 said:
how to boot to brom on this phone? anyone figured it out?
Click to expand...
Click to collapse
While Mtk client is running:
1. Power off device & disconnect the usb
2. Plug in usb while holding VOL - & VOL +
Mtk Client will automatically recognize mtk device
Biggitybaked said:
Hello Everyone.
This is my first post so please if i did anything wrong or posted this in the wrong place please let me know.
I have a Moto G Pure that im trying to root. I have to unlock the bootloader first from what i gather. I downloaded the adb, fastboot and drivers for the phone installed everything and went on motos website and used there bootloader unlock string tool and it says "your device does not qualify for bootloader unlocking". Not sure why that's coming up? Does anyone know a work around by chance? Here is the Unlock Data, the sting I used and the getvar info.
C:\\Desktop\platform-tools>fastboot oem get_unlock_data
(bootloader) Unlock data:
(bootloader) 3A85832508840061#5A593232444C4B
(bootloader) 474433006D6F746F2067200000#F797
(bootloader) DDD03416481B0F85B69548533550013
(bootloader) 97C6CAAC01B02F6D820BD2048F29F#0
(bootloader) DF077A6F1E7E5E80000000000000000
OKAY [ 0.050s]
Finished. Total time: 0.052
3A85832508840061#5A593232444C4B474433006D6F746F2067200000#F797DDD03416481B0F85B6954853355001397C6CAAC01B02F6D820BD2048F29F#0DF077A6F1E7E5E80000000000000000
C:\\Desktop\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ellis_a-320aeee45-211101
(bootloader) product: ellis
(bootloader) board: ellis
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 4
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DX68MB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG N NVM DIE=512Mb M5=01 M6=07 M7=00 M8=0E
(bootloader) cpu: MT6762G
(bootloader) serialno: XXXXXXXXXX
(bootloader) cid: 0x0001
(bootloader) channelid: 0x88
(bootloader) uid: 0DF077A6F1E7E5E8000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-18-2021
(bootloader) sku: XT2163-6
(bootloader) carrier_sku: XT2163-6
(bootloader) battid: SB18D15249
(bootloader) iccid: 89012803320393497037
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 15 12:24:29 UTC 2022"
(bootloader) ro.build.fingerprint[0]: motorola/ellis_a/ellis:11/RRH31.Q3
(bootloader) ro.build.fingerprint[1]: -46-50-2/20fec:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.mtk: alps-mp-r0.mp1.tc2sp-V1.66
(bootloader) version-baseband: MT6762_TC2.PR2.SP.V8.2.P20.01.66.54R
(bootloader) kernel.version[0]: Linux version 4.19.127+ ([email protected]
(bootloader) kernel.version[1]: build) (Android (6443078 based on r38390
(bootloader) kernel.version[2]: 2) clang version 11.0.1 (https://android
(bootloader) kernel.version[3]: .googlesource.com/toolchain/llvm-project
(bootloader) kernel.version[4]: b397f81060ce6d701042b782172ed13bee898b7
(bootloader) kernel.version[5]: 9), LLD 11.0.1 (/buildbot/tmp/tmp6_m7QH
(bootloader) kernel.version[6]: b397f81060ce6d701042b782172ed13bee898b79
(bootloader) kernel.version[7]: )) #1 SMP PREEMPT Mon Nov 1 05:00:56 CDT
(bootloader) kernel.version[8]: 2021
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: attpre
(bootloader) current-slot: a
(bootloader) running-boot-lun: 1
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 1
(bootloader) slot-retry-count:_b: 7
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28D31556
(bootloader) is-userspace: no
(bootloader) is-logical:
(bootloader) snapshot-update-status: none
all: listed above
Finished. Total time: 0.078s
Any pointers would surly be appreciated. Been pulling my hair out. haha!
Thanks for reading!
-BB
Click to expand...
Click to collapse
Successfully rooted my Moto G Pure (RRHS31.Q3-46-110-13):
OEM unlock was grayed out, so I used Motorola RSA to download the stock ROM, then after locating the ROM files, used Magisk 25.2 to patch the boot.img. I flashed the stock ROM using the RESCUE option in RSA then setup my phone once the process was complete. I enabled Developer Options as well as, the now available, OEM unlock and went through the steps to flash the patched boot.img from earlier. I've attached the stock boot and am currently using LSPosed in place of EdXposed
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
Moto G Pure - XT2163-4 root? is there a root out there? thx
alan2424m said:
Moto G Pure - XT2163-4 root? is there a root out there? thx
Click to expand...
Click to collapse
Yes. I'm currently using a Moto G Pure TMO (Ellis) updated to Android 12 (S3RH32.20-42-10-2-3) with Magisk 25.2. I'll include my boot.img below which is Android 12-4.19.191+ Magisk patched (25.2) with HuskyDG bootloop protection. I also used LSPosed 1.8.5 (6695) zygisk with [email protected] GS Ram Drive (20GB swap). I had to use Motorola's Rescue & Smart Assistant to re-flash my phone before I could toggle OEM unlock, then I used the generated key to unlock my bootloader.
KMerrimanJr said:
Yes. I'm currently using a Moto G Pure TMO (Ellis) updated to Android 12 (S3RH32.20-42-10-2-3) with Magisk 25.2. I'll include my boot.img below which is Android 12-4.19.191+ Magisk patched (25.2) with HuskyDG bootloop protection. I also used LSPosed 1.8.5 (6695) zygisk with [email protected] GS Ram Drive (20GB swap). I had to use Motorola's Rescue & Smart Assistant to re-flash my phone before I could toggle OEM unlock, then I used the generated key to unlock my bootloader.
Click to expand...
Click to collapse
thx man does it matter that mine is android version 11 XT2163-4?
i got it unlocked already
alan2424m said:
i got it unlocked already
Click to expand...
Click to collapse
No, mine started as Android 11 but Google recently release an Android 12 update for the XT2163-4. ELLIS_T_S3RH32.20_42_10_2_3_subsidy_TMO_UNI_RSU_QCOM_regulatory_DEFAULT_CFC.xml is the latest T-Mobile rom released by Google. Check out the site below to download the official ROM. All carriers are listed
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
alan2424m said:
thx man does it matter that mine is android version 11 XT2163-4
Click to expand...
Click to collapse
Android 12 tightened up on security so you might want to stay on 11. I use App Manager and overlayFS to "uninstall" any apps I don't want but I can't directly delete from the system dir. On 11 I could
KMerrimanJr said:
No, mine started as Android 11 but Google recently release an Android 12 update for the XT2163-4. ELLIS_T_S3RH32.20_42_10_2_3_subsidy_TMO_UNI_RSU_QCOM_regulatory_DEFAULT_CFC.xml is the latest T-Mobile rom released by Google. Check out the site below to download the official ROM. All carriers are listed
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
ok mine is boost mobile but that shouldnt change anything right?
here is mine ELLIS_T_RRHS31.Q3_46_110_13_subsidy_BOOST_DISH_SHORT_regulatory_DEFAULT_CFC.xml
yours is tmobile like i said hopefully that doesnt change anything
So I tried to flash a custom recovery and rom but when I flashed my rom it booted to boot loader and it said oem_locked when I had it unlocked 2 minutes ago. So I try to go into twrp and I can’t, says start up failed. I tried using the software but it said it can’t identify my device and it can’t fix anything. I also tried to flash stock rom via and but it said it can’t find and can’t mount any partitions. This leads me to believe that my partitions are gone or corrupt. Can anyone help? Im not sure the model number but I know the phone is a Moto g7 Power from t-mobile that was completely unlocked, boot loader and all.
Can you get into fastboot mode? Try using the command, fastboot getvar all, it should give you information about partitions available.
Try flashing one image at a time.
You probably need to use an unbrick firmware and (100)% the correct driver.
An unbrick software will format your device ssd and create all the partitions again.
JonasHS said:
Can you get into fastboot mode? Try using the command, fastboot getvar all, it should give you information about partitions available.
Try flashing one image at a time.
You probably need to use an unbrick firmware and (100)% the correct driver.
An unbrick software will format your device ssd and create all the partitions again.
Click to expand...
Click to collapse
I ran getvar and it spat out this.
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_t-16222030b3b-210202
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 751d40d
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-ocean_t-16222030b3b-210202
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) pcb-part-no:
Also when I try to run Motorola's software it does this
The second picture is what it says when I try to use manual. I click use anyway and it just goes back to saying not appropriate firmware.
Also trying to install the images one by one also didnt work.
Unbrick tools
Have your phone edl mode? Snapdragon =Qualcomm?
Once you have installed custom ROM, your partition should not be the same a / b order.
You are need to use moto's unbrick tool in edl.
JonasHS said:
Once you have installed custom ROM, your partition should not be the same a / b order.
You are need to use moto's unbrick tool in edl.
Click to expand...
Click to collapse
I tried to get into Edl mode but my phone doesn't have Edl mode
also that was Motorola's unbrick tool and it didn't work.
Your CPU is Qualcomm Snapdragon. You have it. Edl is same some bios on PC. Is built in your phone. Try to boot into it, your are need PC and USB and driver for edl.
I hope you know then you are in edl mode have your phone black screen.
JonasHS said:
Your CPU is Qualcomm Snapdragon. You have it. Edl is same some bios on PC. Is built in your phone. Try to boot into it, your are need PC and USB and driver for edl.
I hope you know then you are in edl mode have your phone black screen.
Click to expand...
Click to collapse
I tried. It said unknown command. I patched the fastboot exe to tell it to go to edl mode and it says unknown command.
that_one_gamer said:
I tried. It said unknown command. I patched the fastboot exe to tell it to go to edl mode and it says unknown command.
Click to expand...
Click to collapse
I have the driver and everything. Doesn’t work.
Fastboot can't reboot you into edl, you are need to connect phone to USB to PC and hold vol - and vol+ and power on same time and see device on PC
Have you never used del before?
JonasHS said:
Have you never used del before?
Click to expand...
Click to collapse
I tried doing that and it just goes to the boot loader.
JonasHS said:
Click to expand...
Click to collapse
That’s not edl mode. That’s bootloader. Plus that’s what I did and the software didn’t work. I included screenshots in one of the other reply’s.
You don't understand How did you think android come on SSD. Factory install it with download mode.
JonasHS said:
You don't understand How did you think android come on SSD. Factory install it with download mode.
Click to expand...
Click to collapse
I do understand, the software does not allow me to reflash with download mode. If I try to reflash manually it fails because partitions cannot be mounted.
This is what the software says
that_one_gamer said:
This is what the software says
Click to expand...
Click to collapse
Look at the screenshots. And I also cannot access recovery mode.
So this is my phone, i succefully boot twrp, and it didnt do anything and just made this "fastboot loop"
I tried "fastboot erase data" i get this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://gyazo.com/16ae3403faf584982f12437c6c061492
Then i tried "fastboot erase cache" and i the same error.
I tried "fastboot erase userdata" and i get this:
https://gyazo.com/37c8681728e0025c8894e483384b00e5
I tried flash/boot twrp again and it doesnt do anything.
And finaly i let the battery drop to 0, i have the 0% battery starting screen, then when i charge the phone up, it just go straight to fastboot mode.
I really hope someone will be able to help me!!
Eeehm... Product name: holi?
The Nord 2 doesn't have a "holi" chip, which is qualcomm. It has an mt6893 mediatek chip.
So if your *bootloader* reports this something has gone askew.
- You've either flashed a qcom bootloader onto an mtk phone and miraculously didn't brick your phone.
- Or you're a little lost, and actually you have a Nord N200 phone, which has a 'holi' chip.
Of course if you've flashed a TWRP recovery for the Nord 2, instead of Nord N200 they're vastly different and not surprised that doesn't boot.
Beanow said:
Eeehm... Product name: holi?
The Nord 2 doesn't have a "holi" chip, which is qualcomm. It has an mt6893 mediatek chip.
So if your *bootloader* reports this something has gone askew.
- You've either flashed a qcom bootloader onto an mtk phone and miraculously didn't brick your phone.
- Or you're a little lost, and actually you have a Nord N200 phone, which has a 'holi' chip.
Of course if you've flashed a TWRP recovery for the Nord 2, instead of Nord N200 they're vastly different and not surprised that doesn't boot.
Click to expand...
Click to collapse
Weird, i bought it on amazon as a oneplus nord 2 ce 5g and i have the box of the nord 2 ce 5g
https://www.amazon.fr/dp/B07XXP3G92/ref=pe_27091421_487030221_TE_SCE_3p_dp_1
Well there you go. The CE variant is pretty different from the Nord 2 non-CE as well. You've mixed up the phone.
ALSO, you're probably still wrong about that.
The Nord CE 2 5G should have a mediatek chip. Not the qcom 'holi'.
Are you sure you don't have the Nord CE 2 Lite 5G? That at least has a qcom chip.
Yep that's what your ad says.
Honestly, you should probably be doing a little more research before flashing roms, if you're getting tripped up by marketing names.
Beanow said:
Well there you go. The CE variant is pretty different from the Nord 2 non-CE as well. You've mixed up the phone.
ALSO, you're probably still wrong about that.
The Nord 2 CE 5G should have a mediatek chip. Not the qcom 'holi'.
Are you sure you don't have the Nord 2 CE Lite 5G? That at least has a qcom chip.
Click to expand...
Click to collapse
oh yea ok, im dumb i have the Nord 2 CE Lite 5G i didnt do enough research, is there still a way to fix my phone?
je suis daccord said:
is there still a way to fix my phone?
Click to expand...
Click to collapse
Yes, so long as you don't mess up your ability to get into fastboot mode.
What you want, is to find out if you have a separate recovery partition.
For that, try fastboot getvar all and see if there's mention of recovery. (maybe dump it here)
Like has-slot:recovery: yes/no
Or partition-type:recovery_a/_b: raw data
Next, if you do not have a recovery partition, you'll want to restore your boot partition.
Either to a backup, maybe a magisk rooted one you had working before, or a stock image.
If you think you have a working boot.img. You can try it out with:
fastboot boot path-to-my-boot.img
If that looks good, flash with
fastboot flash boot path-to-my-boot.img
Beanow said:
Yes, so long as you don't mess up your ability to get into fastboot mode.
What you want, is to find out if you have a separate recovery partition.
For that, try fastboot getvar all and see if there's mention of recovery. (maybe dump it here)
Like has-slot:recovery: yes/no
Or partition-type:recovery_a/_b: raw data
Next, if you do not have a recovery partition, you'll want to restore your boot partition.
Either to a backup, maybe a magisk rooted one you had working before, or a stock image.
If you think you have a working boot.img. You can try it out with:
fastboot boot path-to-my-boot.img
If that looks good, flash with
fastboot flash boot path-to-my-boot.img
Click to expand...
Click to collapse
Code:
(bootloader) parallel-download-flash:yes
(bootloader) hw-revision:10000
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3736
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x1000
(bootloader) logical-block-size: 0x1000
(bootloader) variant:SM_ UFS
(bootloader) partition-type:oplusstanvbk_b:raw
(bootloader) partition-size:oplusstanvbk_b: 0x1400000
(bootloader) partition-type:DRIVER:raw
(bootloader) partition-size:DRIVER: 0x2000000
(bootloader) partition-type:oplusreserve5:raw
(bootloader) partition-size:oplusreserve5: 0x4000000
(bootloader) partition-type:oplusreserve4:raw
(bootloader) partition-size:oplusreserve4: 0x2000000
(bootloader) partition-type:oplusreserve3:raw
(bootloader) partition-size:oplusreserve3: 0x4000000
(bootloader) partition-type:oplusreserve2:raw
(bootloader) partition-size:oplusreserve2: 0x10000000
(bootloader) partition-type:oplusreserve1:raw
(bootloader) partition-size:oplusreserve1: 0x800000
(bootloader) partition-type:mdm1oemnvbktmp:raw
(bootloader) partition-size:mdm1oemnvbktmp: 0x200000
(bootloader) partition-type:mdm1m9kefsc:raw
(bootloader) partition-size:mdm1m9kefsc: 0x1000
(bootloader) partition-type:mdm1m9kefs2:raw
(bootloader) partition-size:mdm1m9kefs2: 0x200000
(bootloader) partition-type:mdm1m9kefs1:raw
(bootloader) partition-size:mdm1m9kefs1: 0x200000
(bootloader) partition-type:mdm1m9kefs3:raw
(bootloader) partition-size:mdm1m9kefs3: 0x200000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x20000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x300000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x300000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x300000
(bootloader) partition-type:oplusstanvbk_a:raw
(bootloader) partition-size:oplusstanvbk_a: 0x1400000
(bootloader) partition-type:oplusdycnvbk:raw
(bootloader) partition-size:oplusdycnvbk: 0x1400000
(bootloader) partition-type:ALIGN_TO_128K_2:raw
(bootloader) partition-size:ALIGN_TO_128K_2: 0x1A000
(bootloader) partition-type:vm-data:raw
(bootloader) partition-size:vm-data: 0x400000
(bootloader) partition-type:vm-keystore:raw
(bootloader) partition-size:vm-keystore: 0x20000
(bootloader) partition-type:catecontentfv:raw
(bootloader) partition-size:catecontentfv: 0x100000
(bootloader) partition-type:catefv:raw
(bootloader) partition-size:catefv: 0x80000
(bootloader) partition-type:secdata:raw
(bootloader) partition-size:secdata: 0x7000
(bootloader) partition-type:uefivarstore:raw
(bootloader) partition-size:uefivarstore: 0x80000
(bootloader) partition-type:multiimgoem_b:raw
(bootloader) partition-size:multiimgoem_b: 0x8000
(bootloader) partition-type:multiimgoem_a:raw
(bootloader) partition-size:multiimgoem_a: 0x8000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:modemdump:raw
(bootloader) partition-size:modemdump: 0x12C00000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:cateloader:raw
(bootloader) partition-size:cateloader: 0x200000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:oplus_sec_b:raw
(bootloader) partition-size:oplus_sec_b: 0xA00000
(bootloader) partition-type:splash_b:raw
(bootloader) partition-size:splash_b: 0x20A4000
(bootloader) partition-type:vendor_boot_b:raw
(bootloader) partition-size:vendor_boot_b: 0xA000000
(bootloader) partition-type:core_nhlos_b:raw
(bootloader) partition-size:core_nhlos_b: 0xAA00000
(bootloader) partition-type:uefisecapp_b:raw
(bootloader) partition-size:uefisecapp_b: 0x200000
(bootloader) partition-type:imagefv_b:raw
(bootloader) partition-size:imagefv_b: 0x200000
(bootloader) partition-type:dtbo_b:raw
(bootloader) partition-size:dtbo_b: 0x1800000
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-size:vbmeta_b: 0x10000
(bootloader) partition-type:qupfw_b:raw
(bootloader) partition-size:qupfw_b: 0x10000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b: 0x20000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0xA000000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b: 0x80000
(bootloader) partition-type:dsp_b:raw
(bootloader) partition-size:dsp_b: 0x2000000
(bootloader) partition-type:abl_b:raw
(bootloader) partition-size:abl_b: 0x100000
(bootloader) partition-type:bluetooth_b:raw
(bootloader) partition-size:bluetooth_b: 0x200000
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b: 0xB400000
(bootloader) partition-type:hyp_b:raw
(bootloader) partition-size:hyp_b: 0x80000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b: 0x400000
(bootloader) partition-type:rpm_b:raw
(bootloader) partition-size:rpm_b: 0x80000
(bootloader) partition-type:oplus_sec_a:raw
(bootloader) partition-size:oplus_sec_a: 0xA00000
(bootloader) partition-type:splash_a:raw
(bootloader) partition-size:splash_a: 0x20A4000
(bootloader) partition-type:vendor_boot_a:raw
(bootloader) partition-size:vendor_boot_a: 0xA000000
(bootloader) partition-type:featenabler_b:raw
(bootloader) partition-size:featenabler_b: 0x20000
(bootloader) partition-type:featenabler_a:raw
(bootloader) partition-size:featenabler_a: 0x20000
(bootloader) partition-type:uefisecapp_a:raw
(bootloader) partition-size:uefisecapp_a: 0x200000
(bootloader) partition-type:core_nhlos_a:raw
(bootloader) partition-size:core_nhlos_a: 0xAA00000
(bootloader) partition-type:imagefv_a:raw
(bootloader) partition-size:imagefv_a: 0x200000
(bootloader) partition-type:dtbo_a:raw
(bootloader) partition-size:dtbo_a: 0x1800000
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-size:vbmeta_a: 0x10000
(bootloader) partition-type:qupfw_a:raw
(bootloader) partition-size:qupfw_a: 0x10000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a: 0x20000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0xA000000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a: 0x80000
(bootloader) partition-type:dsp_a:raw
(bootloader) partition-size:dsp_a: 0x2000000
(bootloader) partition-type:abl_a:raw
(bootloader) partition-size:abl_a: 0x100000
(bootloader) partition-type:bluetooth_a:raw
(bootloader) partition-size:bluetooth_a: 0x200000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a: 0xB400000
(bootloader) partition-type:hyp_a:raw
(bootloader) partition-size:hyp_a: 0x80000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a: 0x400000
(bootloader) partition-type:rpm_a:raw
(bootloader) partition-size:rpm_a: 0x80000
(bootloader) partition-type:engineering_cdt_b:raw
(bootloader) partition-size:engineering_cdt_b: 0x100000
(bootloader) partition-type:dinfo:raw
(bootloader) partition-size:dinfo: 0x4000
(bootloader) partition-type:ocdt:raw
(bootloader) partition-size:ocdt: 0x20000
(bootloader) partition-type:engineering_cdt_a:raw
(bootloader) partition-size:engineering_cdt_a: 0x100000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:cdt:raw
(bootloader) partition-size:cdt: 0x20000
(bootloader) partition-type:ALIGN_TO_128K_1:raw
(bootloader) partition-size:ALIGN_TO_128K_1: 0x1A000
(bootloader) partition-type:xbl_config_b:raw
(bootloader) partition-size:xbl_config_b: 0x80000
(bootloader) partition-type:xbl_b:raw
(bootloader) partition-size:xbl_b: 0x600000
(bootloader) partition-type:xbl_config_a:raw
(bootloader) partition-size:xbl_config_a: 0x80000
(bootloader) partition-type:xbl_a:raw
(bootloader) partition-size:xbl_a: 0x600000
(bootloader) partition-type:userdata:f2fs
(bootloader) partition-size:userdata: 0x1A731B3000
(bootloader) partition-type:super:raw
(bootloader) partition-size:super: 0x29B000000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:metadata:ext4
(bootloader) partition-size:metadata: 0x1000000
(bootloader) partition-type:vm-system_b:raw
(bootloader) partition-size:vm-system_b: 0x8000000
(bootloader) partition-type:vm-system_a:raw
(bootloader) partition-size:vm-system_a: 0x8000000
(bootloader) partition-type:vbmeta_vendor_b:raw
(bootloader) partition-size:vbmeta_vendor_b: 0x10000
(bootloader) partition-type:vbmeta_vendor_a:raw
(bootloader) partition-size:vbmeta_vendor_a: 0x10000
(bootloader) partition-type:vbmeta_system_b:raw
(bootloader) partition-size:vbmeta_system_b: 0x10000
(bootloader) partition-type:vbmeta_system_a:raw
(bootloader) partition-size:vbmeta_system_a: 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:persist:raw
(bootloader) partition-size:persist: 0x2000000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:no
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(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:829711dd
(bootloader) product:holi
(bootloader) snapshot-update-status:none
(bootloader) is-userspace:no
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
all:
Finished. Total time: 0.233s
Ok so i have no recovery partition but i have this:
Code:
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:no
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(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:829711dd
(bootloader) product:holi
I can do something with it right?
Thanks a lot for your help by the way
Beanow said:
Yes, so long as you don't mess up your ability to get into fastboot mode.
What you want, is to find out if you have a separate recovery partition.
For that, try fastboot getvar all and see if there's mention of recovery. (maybe dump it here)
Like has-slot:recovery: yes/no
Or partition-type:recovery_a/_b: raw data
Next, if you do not have a recovery partition, you'll want to restore your boot partition.
Either to a backup, maybe a magisk rooted one you had working before, or a stock image.
If you think you have a working boot.img. You can try it out with:
fastboot boot path-to-my-boot.img
If that looks good, flash with
fastboot flash boot path-to-my-boot.img
Click to expand...
Click to collapse
i don't need twrp to boot an image?
je suis daccord said:
I can do something with it right?
Thanks a lot for your help by the way
Click to expand...
Click to collapse
You can boot/flash a working boot.img yes. Though I don't think I would switch A/B slots, unless you actually know what version of your OS and boot image is in those slots. Normally this would be an older version of the OS and may not boot either due to rollback protection.
je suis daccord said:
i don't need twrp to boot an image?
Click to expand...
Click to collapse
What you need is a boot image that boots!
There's no Nord CE 2 Lite 5G in either https://twrp.me/Devices/ or https://wiki.lineageos.org/devices/#oneplus, and XDA hasn't got a forum for it even.
So I'm guessing there may not be a TWRP build that will work for you atm.
If I was you, I would go back to a stock boot image.
If you don't have that.... why didn't you? Nobody told you about backups or gave you the disclaimers?
Jokes aside, get the FULL (like 4GB one) stock ROM from OnePlus support pages, or Oxygen Updater app using a second phone. Preferably the *version* that matches the update you have installed *exactly*.
Use one of many payload.bin extracting tools to split the file, and that should include a boot.img.
Then try fastboot boot boot.img with that file.
Note: do not flash any of the other partitions / img files!
Some of these include firmware and bootloaders that can definitely BRICK your phone.
Keep to just trying out boot.img
Beanow said:
You can boot/flash a working boot.img yes. Though I don't think I would switch A/B slots, unless you actually know what version of your OS and boot image is in those slots. Normally this would be an older version of the OS and may not boot either due to rollback protection.
What you need is a boot image that boots!
There's no Nord CE 2 Lite 5G in either https://twrp.me/Devices/ or https://wiki.lineageos.org/devices/#oneplus, and XDA hasn't got a forum for it even.
So I'm guessing there may not be a TWRP build that will work for you atm.
If I was you, I would go back to a stock boot image.
If you don't have that.... why didn't you? Nobody told you about backups or gave you the disclaimers?
Jokes aside, get the FULL (like 4GB one) stock ROM from OnePlus support pages, or Oxygen Updater app using a second phone. Preferably the *version* that matches the update you have installed *exactly*.
Use one of many payload.bin extracting tools to split the file, and that should include a boot.img.
Then try fastboot boot boot.img with that file.
Note: do not flash any of the other partitions / img files!
Some of these include firmware and bootloaders that can definitely BRICK your phone.
Keep to just trying out boot.img
Click to expand...
Click to collapse
I've found this:
OnePlus Nord CE 2 Lite 5G Firmware Flash File (Stock ROM | Android 12)
In this tutorial, we will share the latest OnePlus Nord CE 2 Lite 5G firmware flash file and guide you on how to install it on your device.Sometimes
www.getdroidtips.com
I dont know which version i have, so do i try the last one?
Beanow said:
You can boot/flash a working boot.img yes. Though I don't think I would switch A/B slots, unless you actually know what version of your OS and boot image is in those slots. Normally this would be an older version of the OS and may not boot either due to rollback protection.
What you need is a boot image that boots!
There's no Nord CE 2 Lite 5G in either https://twrp.me/Devices/ or https://wiki.lineageos.org/devices/#oneplus, and XDA hasn't got a forum for it even.
So I'm guessing there may not be a TWRP build that will work for you atm.
If I was you, I would go back to a stock boot image.
If you don't have that.... why didn't you? Nobody told you about backups or gave you the disclaimers?
Jokes aside, get the FULL (like 4GB one) stock ROM from OnePlus support pages, or Oxygen Updater app using a second phone. Preferably the *version* that matches the update you have installed *exactly*.
Use one of many payload.bin extracting tools to split the file, and that should include a boot.img.
Then try fastboot boot boot.img with that file.
Note: do not flash any of the other partitions / img files!
Some of these include firmware and bootloaders that can definitely BRICK your phone.
Keep to just trying out boot.img
Click to expand...
Click to collapse
OK first, thank you so much, it works but i don't have wifi, bluetooth, location etc...
I have this in the payload.bin
https://gyazo.com/14fff7b270aa0deb6b4a842ecb1a7905
je suis daccord said:
but i don't have wifi, bluetooth, location etc...
Click to expand...
Click to collapse
Have you tried to flash any other partitions before TWRP?
Or tried to use TWRP to install a custom ROM?
Also, now that you're booted to Stock. Go to settings and make sure you note what version you've actually installed. What model you have. Etc.
Beanow said:
Have you tried to flash any other partitions before TWRP?
Or tried to use TWRP to install a custom ROM?
Also, now that you're booted to Stock. Go to settings and make sure you note what version you've actually installed. What model you have. Etc.
Click to expand...
Click to collapse
No i didnt try to flash anything before twrp. Since i have no way to access internet on my phone, do i need to flash other .img?
Model: CPH2409
Version number: CPH2409_11_A.11
Radio version: Q_V1_P14,Q_V1_P14
kernel version:5.4.147-qgki-ga7a31d5b2a5d
je suis daccord said:
No i didnt try to flash anything before twrp. Since i have no way to access internet on my phone, do i need to flash other .img?
Click to expand...
Click to collapse
Eh, so your wifi etc never worked?
Beanow said:
Eh, so your wifi etc never worked?
Click to expand...
Click to collapse
No my wifi worked before i tried to flash twrp and boot boot.img
> CPH2409_11_A.11
So that's the version number you want to look for when searching for the OTA to extract. Which wasn't on the page you linked before (those were older). So you want to look for a newer version.
For some reason the support pages are woefully out of date too.
OnePlus Support Softwareupgrade - OnePlus (Global)
support softwareupgrade
www.oneplus.com
So try the Oxygen Updater app, maybe with USB tethering or a second phone?
Beanow said:
> CPH2409_11_A.11
So that's the version number you want to look for when searching for the OTA to extract. Which wasn't on the page you linked before (those were older). So you want to look for a newer version.
For some reason the support pages are woefully out of date too.
OnePlus Support Softwareupgrade - OnePlus (Global)
support softwareupgrade
www.oneplus.com
So try the Oxygen Updater app, maybe with USB tethering or a second phone?
Click to expand...
Click to collapse
i have no way to access internet on my phone so i may have to flash one of the .img i have in the last pictures to have wifi
(I tried to access internet by adb using gnirehtet, worked on my old phone but not on this one)
Beanow said:
> CPH2409_11_A.11
So that's the version number you want to look for when searching for the OTA to extract. Which wasn't on the page you linked before (those were older). So you want to look for a newer version.
For some reason the support pages are woefully out of date too.
OnePlus Support Softwareupgrade - OnePlus (Global)
support softwareupgrade
www.oneplus.com
So try the Oxygen Updater app, maybe with USB tethering or a second phone?
Click to expand...
Click to collapse
i have no solution do i try everything on this:
OnePlus Nord CE 2 Lite 5G Firmware Flash File (Stock ROM | Android 12)
In this tutorial, we will share the latest OnePlus Nord CE 2 Lite 5G firmware flash file and guide you on how to install it on your device.Sometimes
www.getdroidtips.com
i tried to just do bluetooth.img but im now in bootloop but i can escape it in fastboot
edit: back again with the same problem, should i try the things said on the website
je suis daccord said:
i have no solution do i try everything on this:
OnePlus Nord CE 2 Lite 5G Firmware Flash File (Stock ROM | Android 12)
In this tutorial, we will share the latest OnePlus Nord CE 2 Lite 5G firmware flash file and guide you on how to install it on your device.Sometimes
www.getdroidtips.com
i tried to just do bluetooth.img but im now in bootloop but i can escape it in fastboot
edit: back again with the same problem, should i try the things said on the website
Click to expand...
Click to collapse
I wouldn't touch other partitions with a 10 foot pole.
Let me see if I can get the latest OTA link.
CPH2409_11_A.11
This should be it right?
md5 0a0e62d410dc3b87e8dcb25a2d35be1b
INI:
FILE_HASH=GQ07CR7r9sT+uds2JpIUn6AgZG82OGteiLC9cTZBDO4=
FILE_SIZE=4043941458
METADATA_HASH=61VbswdVcMAxU4VYOqRNdtkTNL4VPt/Ytz1y19TNc3Q=
METADATA_SIZE=163860
oplus_separate_soft=21341
security_patch_vendor=2022-08-05
oplus_update_engine_verify_disable=0
security_patch=2022-08-05
oplus_rom_version=V12.1
ota_target_version=CPH2409_11.A.11_0110_202208262346