Related
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!!!
Long story short, I softbricked a Razer 1 by using Razer's own flash_all batch/shell script. At this point I can't determine exactly when the "oh ****" happened, but I've tried a lot of things and have been asking in the Newbie sticky post as well. Basically, I have the OEM factory defaults archive which supposedly will at least get a recovery partition and image back so I can move forward, but I only have fastboot/Download Mode. I can issue nearly any command I've tried to it, but the biggest issue right now is that it won't recognize or respond or accept any slot changes and a "fastboot getvar slot" returns an empty field. When I try setting the slot to a or b, or when I just do --set-active=other, I get an error that this device does not support slots. Obviously that's bad because this device does indeed us slot partitioning and has no true recovery partition.
What should I try? I have mkbootimg, abootimg, a Windows or Linux box with each able to manipulate Android devices and I even have Android Studio setup on my Windows PC. Magisk looks promising since I understand the concepts of tar and cpio as a linux admin, but obviously that's meaningless until I can boot into some kind of recovery. The device does still know its serial number, so I'm assuming the firmware flashed manufacturer stuff and hopefully any kind of PGP or cert or key is all still intact and untouched.
EDIT UPDATE:
< waiting for any device >
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4127
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC72DD7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xE0000000
(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:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:181812V00402779
(bootloader) product:cheryl
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) version:0.0
all:
Finished. Total time: 0.032s
That is now my current getvar output, and it looks fine, but now I cannot set_active to _b and after the reboot, it seems to revert back to slot a automatically, like it is trying to enter recovery, but cannot.
Replying to bump and update:
Several attempts at running flash_all.bat from Razer, I can get as far as the first reboot in the script before it hangs and no longer takes input. I think that's because the stupid script isn't properly setting the active slot and it tries to flash partitions on the active slot (slot a in this case). So I am now going to manually run each command, but alternate active slots each time and see. This is new output of "getvar all"
< waiting for any device >
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4127
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC72DD7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xE0000000
(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:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:181812V00402779
(bootloader) product:cheryl
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) version:0.0
all:
Finished. Total time: 0.032s
hey guys, when it comes to all of this i would say i am beyond a newb. so if i violate any protocol i plead ignorance and hope that you will bear with me. i have my disable sister who lives with me and i am responsible for who has had a government phone for years. just recently the powers that be in our great government who are in charge of how our tax dollars are spent somehow decided that one government phone was not enough for her.
to make a long story short she received a second phone out of nowhere that i now have the opportunity to play with.
it is a UMX U683CL and i can find nothing on the web to help me gain root. so i pose to you good people to share whatever links, knowledge and wisdom you can to teach me to pull the stock rom so that a possible custom recovery can be developed and then achieve root.
once again if i have violated any protocol i apologize, please correct me. and thank you in advance for any help>
bigsteve62275
I with you....
If anyone could help us root this phone that would be amazing! i ended up with three of these things lol
Umx u683cl
If it helps you might search for ANS UL40 root info.....when I check my IMEI online it comes back to the ANS model.....and once it came back as
Brand:Teleepoch LTD Model:Lifesaver I thought that was odd. Nothing is available for the UMX that I've found. From what I was told by Assurance wireless they aren't able to unlock them either. None of the pay to unlock online companies can do it. These are really decent phones I suspect it's the service that makes them unusable.
ok what the heck is this (see attached) this is what i get when i run getvar all
Microsoft Windows [Version 10.0.18362.418]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4229940
(bootloader) variant:QRD eMMC
(bootloader) unlocked:yes
(bootloader) secure:no
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0xfa00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x313c79a00
(bootloader) partition-type:carrier:
(bootloader) partition-size:carrier: 0x3200000
(bootloader) partition-type:vendor:
(bootloader) partition-size:vendor: 0xfa00000
(bootloader) partition-type:config:
(bootloader) partition-size:config: 0x80000
(bootloader) partition-typeem:
(bootloader) partition-sizeem: 0x800000
(bootloader) partition-type:keystore:
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:splash:
(bootloader) partition-size:splash: 0xa00000
(bootloader) partition-type:ssd:
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:misc:
(bootloader) partition-size:misc: 0x800000
(bootloader) partition-type:modemst2:
(bootloader) partition-size:modemst2: 0x180000
(bootloader) partition-type:modemst1:
(bootloader) partition-size:modemst1: 0x180000
(bootloader) partition-typead:
(bootloader) partition-sizead: 0x100000
(bootloader) partition-type:apdp:
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:devcfg:
(bootloader) partition-size:devcfg: 0x40000
(bootloader) partition-type:tzbak:
(bootloader) partition-size:tzbak: 0x200000
(bootloader) partition-type:tz:
(bootloader) partition-size:tz: 0x200000
(bootloader) partition-type:rpmbak:
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:abootbak:
(bootloader) partition-size:abootbak: 0x100000
(bootloader) partition-type:aboot:
(bootloader) partition-size:aboot: 0x100000
(bootloader) partition-type:sbl1bak:
(bootloader) partition-size:sbl1bak: 0x80000
(bootloader) partition-type:sbl1:
(bootloader) partition-size:sbl1: 0x80000
(bootloader) partition-type:keymasterbak:
(bootloader) partition-size:keymasterbak: 0x80000
(bootloader) partition-type:keymaster:
(bootloader) partition-size:keymaster: 0x80000
(bootloader) partition-type:cmnlibbak:
(bootloader) partition-size:cmnlibbak: 0x40000
(bootloader) partition-type:cmnlib:
(bootloader) partition-size:cmnlib: 0x40000
(bootloader) partition-type:devinfo:
(bootloader) partition-size:devinfo: 0x100000
(bootloader) partition-type:recovery:
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6e00000
(bootloader) partition-typeersist:
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x5dc00000
(bootloader) partition-type:boot:
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-type:sec:
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:fsg:
(bootloader) partition-size:fsg: 0x180000
(bootloader) partition-typeDR:
(bootloader) partition-sizeDR: 0x8000
(bootloader) partition-type:modem:
(bootloader) partition-size:modem: 0x4200000
(bootloader) serialno:990b2328
(bootloader) kernel:lk
(bootloader) product:MSM8909
all:
finished. total time: 0.204s
C:\WINDOWS\system32>
I believe this device ships with an unlocked bootloader. Would be easy to root, methinks. Standard custom recovery flash and SuperSU or Magisk flashable ZIP should land the plane. TWRP builds are way more prevalent than before. Shouldn't be hard to port from the U673C if they have the same CPU.
---------- Post added at 06:09 AM ---------- Previous post was at 05:41 AM ----------
baileychic8 said:
If it helps you might search for ANS UL40 root info.....when I check my IMEI online it comes back to the ANS model.....and once it came back as
Brand:Teleepoch LTD Model:Lifesaver I thought that was odd. Nothing is available for the UMX that I've found. From what I was told by Assurance wireless they aren't able to unlock them either. None of the pay to unlock online companies can do it. These are really decent phones I suspect it's the service that makes them unusable.
Click to expand...
Click to collapse
The UL40 is not the same phone. They may have a similar processor, but they aren't nearly the same.
Figlet said:
I believe this device ships with an unlocked bootloader. Would be easy to root, methinks. Standard custom recovery flash and SuperSU or Magisk flashable ZIP should land the plane. TWRP builds are way more prevalent than before. Shouldn't be hard to port from the U673C if they have the same CPU.
The UL40 is not the same phone. They may have a similar processor, but they aren't nearly the same.
Click to expand...
Click to collapse
---------------------------------------
Hi Figlet! Could you give a newbie a little more info on the "Standard custom recovery" .. what and how should I do this for the Unimax U683CL? Thank you very much!
Basically, you just have to find a port of twrp or cwm recovery for this device and flash SuperSU or Magisk. You'll probably have to find someone willing to port the recovery image because I haven't seen any ports in my search, but I believe there are similar devices and twrp builder makes it pretty easy to make a recovery for any device. I'm not going to post a tutorial because there's plenty of information how to flash a custom recovery on any device.
Good luck!
Figlet said:
Basically, you just have to find a port of twrp or cwm recovery for this device and flash SuperSU or Magisk. You'll probably have to find someone willing to port the recovery image because I haven't seen any ports in my search, but I believe there are similar devices and twrp builder makes it pretty easy to make a recovery for any device. I'm not going to post a tutorial because there's plenty of information how to flash a custom recovery on any device.
Good luck!
Click to expand...
Click to collapse
Thanks very much for the reply and the info!! I'm off to hunt for a tutorial now lol. And "someone willing to port the recovery image..." which I have no idea what is. But, I will find out! Twrp builder, here I come. Thank you again!
Edit.. Oh, and I wanted to confirm something you said earlier. It does ship with an unlocked bootloader. Also, if it helps anyone, the "Secure Boot" setting is "Disabled", the bootloader version is blank, the "Variant" is "QRD eMMC", and the "Product Name" is "MSM8909".
Any news on this yet
Slimgig said:
Any news on this yet
Click to expand...
Click to collapse
I'd assume a good few months might take place before we hear anything on this device. If anyone needs cloud compute resources to compile code for this, id be glad to build a temporary VM with whatever specs necessary, depending on compute time & bandwidth required.
I'd also be glad to host any files until an official thread or GitHub is created
I will try and pull anything you need, just let me know what and probably how lol!
sc0rp1 said:
i have root on the phone!!!! You'll need to Reboot into EDL more and flash a custom boot img. im making a tutorial right now and will have everything up later this afternoon! Custom recovery will be on its way as well
Click to expand...
Click to collapse
whats up with that boot.img and recovery and how do you put it in edl mode i just got this phone today and i want to root it
Woo! Thank you! Very excited for this!!
sc0rp1 said:
i have root on the phone!!!! You'll need to Reboot into EDL more and flash a custom boot img. im making a tutorial right now and will have everything up later this afternoon! Custom recovery will be on its way as well
Click to expand...
Click to collapse
I at least need the recovery for this this phone don't have one so I can't flash magisk zip without a recovery its Android 8.1 the bootloader is already unlocked but no twrp and when i google search a bunch of clickbait sites come up for twrp.apk i do adb reboot recovery the phone restarts with the android guy saying no command
sc0rp1 said:
i have root on the phone!!!! You'll need to Reboot into EDL more and flash a custom boot img. im making a tutorial right now and will have everything up later this afternoon! Custom recovery will be on its way as well
Click to expand...
Click to collapse
Any updates on this? It's definitely been longer than that afternoon lol I'm anxiously awaiting a method to achieve root on this phone.
sc0rp1 said:
Here's TWRP as promised! https://forum.xda-developers.com/android/general/umx-u683cl-twrp-t4006993
Click to expand...
Click to collapse
Oh my heart! I think it just exploded a little bit! THANK YOU SO MUCH!! I can't wait to try this out. Seriously, thank you, millions of people have this phone, and are sick of it auto-installing apps and other such garbage.
guess i am way too stupid to pull this off. cant get anything to work at all. keep getting sahara fail and cant figure out how to flash .img at all
I learned not to call Assurance with an issue with the UMC U683CL. The support team had me call from another phone asked for the info and they took the phone I used to call and flipped the sim codes on both phones, cell numbers etc, now neither function. So, if there's a will there is a way. It's an Android which is great but the menus and apps just aren't all that great. The issue is, once you unlock, remove Google their just aren't any decent apps to install. Damn Google. Makes the man want to hurl.
bigsteve62275 said:
ok what the heck is this (see attached) this is what i get when i run getvar all
Microsoft Windows [Version 10.0.18362.418]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4229940
(bootloader) variant:QRD eMMC
(bootloader) unlocked:yes
(bootloader) secure:no
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0xfa00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x313c79a00
(bootloader) partition-type:carrier:
(bootloader) partition-size:carrier: 0x3200000
(bootloader) partition-type:vendor:
(bootloader) partition-size:vendor: 0xfa00000
(bootloader) partition-type:config:
(bootloader) partition-size:config: 0x80000
(bootloader) partition-typeem:
(bootloader) partition-sizeem: 0x800000
(bootloader) partition-type:keystore:
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:splash:
(bootloader) partition-size:splash: 0xa00000
(bootloader) partition-type:ssd:
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:misc:
(bootloader) partition-size:misc: 0x800000
(bootloader) partition-type:modemst2:
(bootloader) partition-size:modemst2: 0x180000
(bootloader) partition-type:modemst1:
(bootloader) partition-size:modemst1: 0x180000
(bootloader) partition-typead:
(bootloader) partition-sizead: 0x100000
(bootloader) partition-type:apdp:
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:devcfg:
(bootloader) partition-size:devcfg: 0x40000
(bootloader) partition-type:tzbak:
(bootloader) partition-size:tzbak: 0x200000
(bootloader) partition-type:tz:
(bootloader) partition-size:tz: 0x200000
(bootloader) partition-type:rpmbak:
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:abootbak:
(bootloader) partition-size:abootbak: 0x100000
(bootloader) partition-type:aboot:
(bootloader) partition-size:aboot: 0x100000
(bootloader) partition-type:sbl1bak:
(bootloader) partition-size:sbl1bak: 0x80000
(bootloader) partition-type:sbl1:
(bootloader) partition-size:sbl1: 0x80000
(bootloader) partition-type:keymasterbak:
(bootloader) partition-size:keymasterbak: 0x80000
(bootloader) partition-type:keymaster:
(bootloader) partition-size:keymaster: 0x80000
(bootloader) partition-type:cmnlibbak:
(bootloader) partition-size:cmnlibbak: 0x40000
(bootloader) partition-type:cmnlib:
(bootloader) partition-size:cmnlib: 0x40000
(bootloader) partition-type:devinfo:
(bootloader) partition-size:devinfo: 0x100000
(bootloader) partition-type:recovery:
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6e00000
(bootloader) partition-typeersist:
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x5dc00000
(bootloader) partition-type:boot:
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-type:sec:
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:fsg:
(bootloader) partition-size:fsg: 0x180000
(bootloader) partition-typeDR:
(bootloader) partition-sizeDR: 0x8000
(bootloader) partition-type:modem:
(bootloader) partition-size:modem: 0x4200000
(bootloader) serialno:990b2328
(bootloader) kernel:lk
(bootloader) product:MSM8909
all:
finished. total time: 0.204s
C:\WINDOWS\system32>
Click to expand...
Click to collapse
May I ask how you actually got to fastboot on the phone? It seems to be stuck on the UMX logo on most other folks.
I just got one of these, I'll try and find the source and maybe build a rom or something. The charger port is loose so I'll be a while before I can do anything substantial.
I unlocked bootloader long ago, however, it was with an older method I believe. The device appears to be unlocked (see below), but attempting to flash anything just freezes into eternity:
Any thoughts?
Code:
C:\platform-tools>adb devices
List of devices attached
LGUS9980af4c546 device
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot getvar all
(bootloader) eio_count:0
(bootloader) dm_count:0
(bootloader) lock_count:0
(bootloader) unlock_count:1
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4308
(bootloader) version-baseband:┼φ≈Qa⌡6C`⌡ⁿƒ
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x81800000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC92474000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x19F400000
(bootloader) secure:yes
(bootloader) serialno:LGUS9980af4c546
(bootloader) product:QC_Reference_Phone
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 0.047s
C:\platform-tools>fastboot flash recovery TWRP.img
Sending 'recovery' (30860 KB)
betam4x said:
I unlocked bootloader long ago, however, it was with an older method I believe. The device appears to be unlocked (see below), but attempting to flash anything just freezes into eternity:
Any thoughts?
Code:
C:\platform-tools>adb devices
List of devices attached
LGUS9980af4c546 device
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot getvar all
(bootloader) eio_count:0
(bootloader) dm_count:0
(bootloader) lock_count:0
(bootloader) unlock_count:1
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4308
(bootloader) version-baseband:┼φ≈Qa⌡6C`⌡ⁿƒ
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x81800000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC92474000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x19F400000
(bootloader) secure:yes
(bootloader) serialno:LGUS9980af4c546
(bootloader) product:QC_Reference_Phone
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 0.047s
C:\platform-tools>fastboot flash recovery TWRP.img
Sending 'recovery' (30860 KB)
Click to expand...
Click to collapse
Download both TWRP.zip on phone and TWRP.img to adb folder of PC. U then have to "fastboot boot TWRP.img" and once temp TWRP boots up, then use TWRP to install TWRP. ZIP as v30 does NOT have recovery partition.
HueyT said:
Download both TWRP.zip on phone and TWRP.img to adb folder of PC. U then have to "fastboot boot TWRP.img" and once temp TWRP boots up, then use TWRP to install TWRP. ZIP as v30 does NOT have recovery partition.
Click to expand...
Click to collapse
No luck so far, it just freezes on sending. Does the same thing if i try to re-unlock it as well.
betam4x said:
No luck so far, it just freezes on sending. Does the same thing if i try to re-unlock it as well.
Click to expand...
Click to collapse
Try another fresh laptop, cable, USB port, LG, Qualcomm drivers, latest minimal adb and fastboot
HueyT said:
Try another fresh laptop, cable, USB port, LG, Qualcomm drivers, latest minimal adb and fastboot
Click to expand...
Click to collapse
tried 3 different cables, multiple versions of the ports (1.1, 3.0, 3.1) and no dice on my main desktop, going to try another desktop in just a moment. Thanks!
It was my desktop. again. Managed to get TWRP on there, now just trying to get LineageOS to boot (right now it's showing the startup screen. Hoping it just takes a while on first boot). Thanks for your help! I should know better by now.
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