After breaking 2 Galaxy Grand devices, I got my hands on a Latin American Moto G 2015.
The first thing that I tried (as usual) was installing TWRP and Rooting it. My surprise came when I tried to unlock the bootloader: it was already unlocked.
I got the device from my dad. He doesn't know anything other than using the Play Store to install apps.
As I assume, the device came from the company that he works. So that makes more strange that the device came unlocked since day zero.
justalemon said:
After breaking 2 Galaxy Grand devices, I got my hands on a Latin American Moto G 2015.
The first thing that I tried (as usual) was installing TWRP and Rooting it. My surprise came when I tried to unlock the bootloader: it was already unlocked.
I got the device from my dad. He doesn't know anything other than using the Play Store to install apps.
As I assume, the device came from the company that he works. So that makes more strange that the device came unlocked since day zero.
Click to expand...
Click to collapse
Although this is possible, it is more likely you would be struck by lightning while being bitten by a shark... What is the Bootloader Status #?
acejavelin said:
What is the Bootloader Status #?
Click to expand...
Click to collapse
Let's say that is unlocked because fastboot oem device-info and *#*#7378423#*#* failed to check the bootloader status (before and after).
When I tried to install TWRP I knew that was unlocked by default.
justalemon said:
Let's say that is unlocked because fastboot oem device-info and *#*#7378423#*#* failed to check the bootloader status (before and after).
When I tried to install TWRP I knew that was unlocked by default.
Click to expand...
Click to collapse
But in fastboot, what is the Bootloader Status?
acejavelin said:
But in fastboot, what is the Bootloader Status?
Click to expand...
Click to collapse
I can't check the Bootloader Status other than "trial and error". Fastboot shows:
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
justalemon said:
I can't check the Bootloader Status other than "trial and error". Fastboot shows:
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.007s
Click to expand...
Click to collapse
You are overthinking it... I just meant from the fastboot screen, it shows it in the bottom section, just power off and press POWER+VOL DN to bring up the screen.
Since we are here, lets see the output of 'fastboot getvar all" but mask out your imei number.
acejavelin said:
since we are here, lets see the output of 'fastboot getvar all" but mask out your imei number.
Click to expand...
Click to collapse
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-80.CC
(bootloader) product: osprey
(bootloader) board: osprey
(bootloader) secure: no
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x5
(bootloader) emmc: 16GB Samsung REV=07 PRV=01 TYPE=57
(bootloader) ram: 1024MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8916
(bootloader) serialno: ZY2223HLV8
(bootloader) cid: 0x000C
(bootloader) channelid: 0x13
(bootloader) uid: B93DA60E00000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Dec 7 19:16:28 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/osprey_retla/osprey_umts:
(bootloader) ro.build.fingerprint[1]: 6.0/MPI24.65-33.1-2/3:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.51.2.osprey_retla
(bootloader) ro.build.version.full[1]: .retla.en.01
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
(bootloader) version-baseband[0]: M8916_2020629.41.03.21.51R OSPREY_NIIL
(bootloader) version-baseband[1]: A_CUST
(bootloader) kernel.version[0]: Linux version 3.10.107-r20-g15931b738759
(bootloader) kernel.version[1]: -04999-gae8e6d5ec254 ([email protected]) (
(bootloader) kernel.version[2]: gcc version 6.3.1 20170404 (Linaro GCC 6
(bootloader) kernel.version[3]: .3-2017.05) ) #4 SMP PREEMPT Wed Aug 2 0
(bootloader) kernel.version[4]: 0:49:13 EDT 2017
(bootloader) sbl1.git: git=MBM-NG-V80.CC-0-g7abea31
(bootloader) rpm.git: git=MBM-NG-V80.CC-0-g932f716
(bootloader) tz.git: git=MBM-NG-V80.CC-0-ga1c5ae6
(bootloader) hyp.git: git=MBM-NG-V80.CC-0-ga1c5ae6
(bootloader) aboot.git: git=MBM-NG-V80.CC-0-gdfaac1d
(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:misc: raw
(bootloader) partition-type:padA: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:padB: 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:cid: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-type:persist: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:ssd: 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:customize: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x00000000027e0000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-size:DDR: 0x0000000000020000
(bootloader) partition-size:aboot: 0x0000000000113000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000008c000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-size:padA: 0x000000000036f000
(bootloader) partition-size:abootBackup: 0x0000000000113000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000008c000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:padB: 0x000000000022f000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000300000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:logo: 0x0000000000400000
(bootloader) partition-size:clogo: 0x0000000000400000
(bootloader) partition-size:persist: 0x0000000000800000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:recovery: 0x0000000001019000
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:padC: 0x000000000087e000
(bootloader) partition-size:sp: 0x0000000000800000
(bootloader) partition-size:keystore: 0x0000000000800000
(bootloader) partition-size:oem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:customize: 0x0000000002000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-size:system: 0x0000000091000000
(bootloader) partition-size:userdata: 0x00000002b3de0000
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: niicl
all: listed above
finished. total time: 0.408s
justalemon said:
Code:
(bootloader) unlocked: [B]Not supported[/B]
(bootloader) securestate: [B]Engineering[/B]
(bootloader) iswarrantyvoid: [B]Not supported[/B]
(bootloader) mot_sst:[B] 1[/B]
Click to expand...
Click to collapse
Hmm... Kind of what I suspected, this device is NOT unlocked... it has an Engineering Bootloader, and the only way to get that is to send it in for repair and have it sent back in error because they didn't finish it.
This topic (Engineering Bootloader) has been revisited many times, there are several threads here discussing it... Basically you are partially unlocked in a way intended for Moto to use a proprietary process to flash it back to stock and maintain the warranty, but they didn't complete the process and return the bootloader to a locked state.
Flashing ROMs and other things will be problematic, because although it appears "unlocked" it is actually in an engineering state and although that sounds good, we have seen a handful of bricked devices because it.
Moto has addressed this in this thread on their official forums (which also contains links to several threads on XDA as well), and customer service should be contacted so the device can be returned to repair to be properly flashed.
Looks like a factory repair problem but the device was never sent to Motorola/Lenovo for repairs.
justalemon said:
Looks like a factory repair problem but the device was never sent to Motorola/Lenovo for repairs.
Click to expand...
Click to collapse
Crazy then... I suppose it's possible it was shipped that way, although it is the first one we have heard of sold that way.
Just use caution when flashing anything, especially custom ROMs, the chance of bricking is high.
Yeah, but i wanted a Moto for the stock rom so i'm good with it.
TWRP, Magisk, SuperSu and No-Frills we're installed without problems.
So many thanks for the help.
justalemon said:
Yeah, but i wanted a Moto for the stock rom so i'm good with it.
TWRP, Magisk, SuperSu and No-Frills we're installed without problems..
Click to expand...
Click to collapse
on stock???
I'm totally astonished as well @acejavelin. I've been with Motorola/Lenovo for over 7 years now and I've never seen a device mistakenly shipped out in this manner.
KrisM22 said:
on stock???
Click to expand...
Click to collapse
I wanted a "pure and clean Android" (no manufacturer or carrier customizations) from the day that I received the device, that means no risky or beta roms.
justalemon said:
I wanted a "pure and clean Android" (no manufacturer or carrier customizations) from the day that I received the device, that means no risky or beta roms.
Click to expand...
Click to collapse
I'm just surprised you were able to install majisk and SuperSU on stock!
MotoJunkie01 said:
I'm totally astonished as well @acejavelin. I've been with Motorola/Lenovo for over 7 years now and I've never seen a device mistakenly shipped out in this manner.
Click to expand...
Click to collapse
A strange device used by a strange guy is not that bad.
Back to the topic, if you guys need more info from the device just ask for it.
justalemon said:
A strange device used by a strange guy is not that bad.
Back to the topic, if you guys need more info from the device just ask for it.
Click to expand...
Click to collapse
@justalemon, would you be willing to provide me with image dumps from your device? Namely, /rpm, /aboot, /sbl1, /tz & /utags. Thanks in advance.
I've got the same device and
(bootloader) unlocked: not supported
(Bootloader) securestate: engineering
I have spent the last couple of days trying to figure out how to restore my Mi A1 to a state where it can boot into a ROM. Currently, it's stuck in a boot loop.
Earlier in the week I followed the guide to go from stock to treble, but then decided to go back to stock. I used MiFlash to flash to stock and that's when it started to boot loop. I realized I hadn't used the TWRP with TISSOT manager to de-treble-partition the device and I also let MiFlash lock the bootloader.
I have removed the back cover from the device to get it into EDL mode, but am not sure how to flash a bootable ROM so I can unlock the bootloader and boot into TWRP. I have tried re-flashing stock but it just boot loops again.
Any suggestions?
In addition to the above, here's the output of 'fastboot getvar all':
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:0
(bootloader) variant:QRD eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:MSM8953_TISSOT2.0_20180405144344
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1fe00000
(bootloader) slot-count:2
(bootloader) current-slot:_a
(bootloader) slot-retry-count:_b:0
(bootloader) slot-success:_b:No
(bootloader) slot-active:_b:No
(bootloader) slot-unbootable:_b:No
(bootloader) slot-retry-count:_a:7
(bootloader) slot-success:_a:No
(bootloader) slot-active:_a:Yes
(bootloader) slot-unbootable:_a:No
(bootloader) has-slot:userdata: No
(bootloader) has-slot:logdump: No
(bootloader) has-slot:dpo: No
(bootloader) has-slot:msadp: No
(bootloader) has-slot:apdp: No
(bootloader) has-slot:keymasterbak: No
(bootloader) has-slot:keymaster: No
(bootloader) has-slot:cmnlib64bak: No
(bootloader) has-slot:cmnlib64: No
(bootloader) has-slot:cmnlibbak: No
(bootloader) has-slot:cmnlib: No
(bootloader) has-slot:lksecappbak: No
(bootloader) has-slot:lksecapp: No
(bootloader) has-slot:mcfg: No
(bootloader) has-slot:syscfg: No
(bootloader) has-slot:mdtp: No
(bootloader) has-slot:dip: No
(bootloader) has-slot:mota: No
(bootloader) has-slot:limits: No
(bootloader) has-slot:config: No
(bootloader) has-slot:keystore: No
(bootloader) has-slot:misc: No
(bootloader) has-slotersist: No
(bootloader) has-slot:system: Yes
(bootloader) has-slot:devinfo: No
(bootloader) has-slot:boot: Yes
(bootloader) has-slot:abootbak: No
(bootloader) has-slot:aboot: No
(bootloader) has-slot:splash: No
(bootloader) has-slot:sec: No
(bootloader) has-slot:fsg: No
(bootloader) has-slotDR: No
(bootloader) has-slot:modemst2: No
(bootloader) has-slot:modemst1: No
(bootloader) has-slot:dsp: No
(bootloader) has-slot:devcfgbak: No
(bootloader) has-slot:devcfg: No
(bootloader) has-slot:tzbak: No
(bootloader) has-slot:tz: No
(bootloader) has-slot:rpmbak: No
(bootloader) has-slot:rpm: No
(bootloader) has-slot:sbl1bak: No
(bootloader) has-slot:sbl1: No
(bootloader) has-slot:ssd: No
(bootloader) has-slot:fsc: No
(bootloader) has-slot:modem: Yes
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache:
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xcd3779e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) crc:1
(bootloader) serialno:3cf21e885904
(bootloader) kernel:lk
(bootloader) product:tissot
I want test EDL mode with cable EDL
What procedure for this?
Thanks for reply
laugeek57 said:
I want test EDL mode with cable EDL
What procedure for this?
Thanks for reply
Click to expand...
Click to collapse
I didn't have an EDL cable so I shorted the test points after pulling the back cover off.
Tried the method from [GUIDE] Rooting your Essential PH-1
Cant load twrp at all as the error is "Requested download size is more than max allowed"
[email protected]:/home/d/Desktop/platform-tools# fastboot flash boot_a twrp-3.2.3-0-mata.img
Sending 'boot_a' (48712 KB) FAILED (remote: 'Requested download size is more than max allowed
does the same for patched boots with TWRP
fastboot flash boot patched_boot.img
which previously worked great (Sept release) now no longer works at all. Phone goes into a boot loop and never loads the system. Can get into fastboot and recovery where I can factory reset the phone. Phone will boot into android if factory reset.
also tried fastboot flash boot_a patched_boot.img from both slot a and b and flashing b from slot a
also tried multiple know good cords
fastboot getvar all
(bootloader) version:0.5
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4104
(bootloader) version-baseband:2.0.c4-M2.0.5
(bootloader) version-bootloader:mata-84f7cce
(bootloader) variantPENAM
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1987357000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x100000000
(bootloader) has-slot:nvdef:yes
(bootloader) has-slot:dsp:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:abl:yes
(bootloader) has-slot:mdtp:yes
(bootloader) has-slot:mdtpsecapp:yes
(bootloader) has-slot:bluetooth:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slotmic:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:_a
(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:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialnoM1LHMAXXXXXXXXX
(bootloader) product:Mata
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
fastboot --version
fastboot version 28.0.1-4986621
I currently managed to get rooted Sept 36 on slot a and a non rooted dec (latest) on slot b. Just need to figure out how to get the Dec. rooted as the listed methods don't work. Neither Dec Magisk patched boot.img (bootloops) or TWRP (too big)
Sept release was patched with NLbeev's PH1-sep-pat_boot-mgk.img
Have you tried to patch the boot.img with the twrp installer zip off of the twrp site?
I am on rooted (no TWRP) December update.
- Start over by flashing the BTS;
- Download the stock boot image, move it to your device and patch it with Magisk;
- Move it back to your PC;
- Fastboot flash it to replace the stock boot image on your device;
- Use the hardware keys to reboot your device;
- Reboot again, confirm your build.
Sent from my PH-1 using Tapatalk
ok i need help i did exactly what you said but it wont work if i am root wifi not working if i flash it with the stock ota flashed with magisk but with all the stuff that come wih the bts it work wifi work but not rooted so i dont know what going on i tried for hours without working so im about to throw this phone in the wall....please help me someone:crying:
Hi there,
im trying to fix an htc u ultra. the problem is a endless bootloop.
Recovery and Download mode doesnt works but still the fastboot.
when i try to boot the phone into dl or recovery mode it still restarts after some seconds.
when i try to get sone informations with htc_fastboot getvar all i got this result
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) boot-mode:FASTBOOT
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xdbf000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xdc000000
(bootloader) serialno:CENSORED
all:
finished. total time: 0.397s
htc_fastboot finished. total time: 7.437s
i have the stock rom but i dont know how to flash because the dl mode doesnt works..
the bootloader is locked and S-ON
Hi there,
I hope there are some experts present that are willing to help me because I think i messed up. After my redmi note 7 was unable to connect with 3G or 4G networks for over a month and even a factory reset didnt fix it, I was thinking about flashing a new custom rom like lineage or similar (the only solution that seems to have fixed these connection issues for some people)
I knew that in some redmi phones the bootloder is locked but I couldn't remember if i unlocked it a few years ago already. "fastboot oem device-info" command gave this message
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.048s]
finished. total time: 0.054s
so in my opinion i was all set up, but the next step is where everything turned sour. I downloaded the twrp recovery.img file for redmi note 7 (lavender) from their official website and followed the guide until:
5. Flash recovery onto your device (replace <recovery_filename> with the actual filename!):
fastboot flash recovery <recovery_filename>.img
Click to expand...
Click to collapse
after my command "fastboot flash recovery twrp.img" I got the message "flashing successfull OKAY" followed by a "too many open files in system" error. Since then I can't boot my phone anymore except into the fastboot screen. Recovery menu doesn't boot either. The Device is still recognized by my pc while in fastboot but the only command that seems to work now is "fastboot devices" which shows the phone.
Is there any way to revive the phone without doing some circuit board surgery or am I out of luck?
Hi it seems like a few more commands are still working "getvar all" gave me this log file. No idea if it helps
(bootloader) crc:1
(bootloader) anti:4
(bootloader) DP:0x0
(bootloader) token:VQEBIgEQhgkJViwWK+EoHYAEQhxzOgMIbGF2ZW5kZXICBMighLI=
(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:4238
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x56FBF7E00
(bootloader) partition-type:cust:raw
(bootloader) partition-size:cust: 0x34000000
(bootloader) partition-type:vendor:raw
(bootloader) partition-size:vendor: 0x80000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xE0000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:recovery:raw
(bootloader) partition-size:recovery: 0x4000000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0xC000000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-typeersistbak:raw
(bootloader) partition-sizeersistbak: 0x2000000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x4000000
(bootloader) partition-type:dtbobak:raw
(bootloader) partition-size:dtbobak: 0x800000
(bootloader) partition-type:dtbo:raw
(bootloader) partition-size:dtbo: 0x800000
(bootloader) partition-type:bk2:raw
(bootloader) partition-size:bk2: 0x1000000
(bootloader) partition-type:mdtp:raw
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:bk1:raw
(bootloader) partition-size:bk1: 0x1800000
(bootloader) partition-type:dsp:raw
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x800000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x800000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x800000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x800000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x400000
(bootloader) partition-type:xblbak:raw
(bootloader) partition-size:xblbak: 0x380000
(bootloader) partition-type:xbl:raw
(bootloader) partition-size:xbl: 0x380000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:bluetooth:raw
(bootloader) partition-size:bluetooth: 0x100000
(bootloader) partition-type:keymasterbak:raw
(bootloader) partition-size:keymasterbak: 0x100000
(bootloader) partition-type:keymaster:raw
(bootloader) partition-size:keymaster: 0x100000
(bootloader) partition-type:mdtpsecappbak:raw
(bootloader) partition-size:mdtpsecappbak: 0x400000
(bootloader) partition-type:mdtpsecapp:raw
(bootloader) partition-size:mdtpsecapp: 0x400000
(bootloader) partition-type:tzbak:raw
(bootloader) partition-size:tzbak: 0x400000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x400000
(bootloader) partition-type:devcfg:raw
(bootloader) partition-size:devcfg: 0x100000
(bootloader) partition-type:devcfgbak:raw
(bootloader) partition-size:devcfgbak: 0x100000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:ablbak:raw
(bootloader) partition-size:ablbak: 0x100000
(bootloader) partition-type:abl:raw
(bootloader) partition-size:abl: 0x100000
(bootloader) partition-type:cmnlib64bak:raw
(bootloader) partition-size:cmnlib64bak: 0x100000
(bootloader) partition-type:cmnlib64:raw
(bootloader) partition-size:cmnlib64: 0x100000
(bootloader) partition-type:cmnlibbak:raw
(bootloader) partition-size:cmnlibbak: 0x100000
(bootloader) partition-type:cmnlib:raw
(bootloader) partition-size:cmnlib: 0x100000
(bootloader) partition-typemicbak:raw
(bootloader) partition-sizemicbak: 0x80000
(bootloader) partition-typemic:raw
(bootloader) partition-sizemic: 0x80000
(bootloader) partition-type:hypbak:raw
(bootloader) partition-size:hypbak: 0x80000
(bootloader) partition-type:hyp:raw
(bootloader) partition-size:hyp: 0x80000
(bootloader) partition-type:rpmbak:raw
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:raw
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:storsecbak:raw
(bootloader) partition-size:storsecbak: 0x20000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:vbmetabak:raw
(bootloader) partition-size:vbmetabak: 0x10000
(bootloader) partition-type:vbmeta:raw
(bootloader) partition-size:vbmeta: 0x10000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x5000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x8000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x2000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:switch:raw
(bootloader) partition-size:switch: 0x2000
(bootloader) secure:yes
(bootloader) serialno:87e1ca97
(bootloader) product:lavender
(bootloader) max-download-size:402653184
(bootloader) kernel:uefi
all:
finished. total time: 0.557s
Click to expand...
Click to collapse
Check if this tool helps you revive your device back to normal state
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
www.xiaomitool.com
Tavero said:
Hi it seems like a few more commands are still working "getvar all" gave me this log file. No idea if it helps
Click to expand...
Click to collapse
mvikrant97 said:
Check if this tool helps you revive your device back to normal state
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
www.xiaomitool.com
Click to expand...
Click to collapse
Thanks,
But during flashing I got this error:
Fastboot flash all failed, exit code: 1, output: Missmaching image and device
What img do i have to pick? there my model is M1901F7G
Do you know a recovery.img that is actually working? Official TWRP and orange fox are both not working.
Tavero said:
Thanks,
But during flashing I got this error:
Fastboot flash all failed, exit code: 1, output: Missmaching image and device
What img do i have to pick? there my model is M1901F7G
Do you know a recovery.img that is actually working? Official TWRP and orange fox are both not working.
Click to expand...
Click to collapse
I will get back to you on this tomorrow.
I figured I try XiaMiTool again and found the correct image in that list (I think) which was actually called lavender Redmi note 7 (not redmi 7)
I got a different error though:
Fastboot flash all failed, exit code: 1, output: "Flash xbl error"
Tavero said:
I figured I try XiaMiTool again and found the correct image in that list (I think) which was actually called lavender Redmi note 7 (not redmi 7)
I got a different error though:
Fastboot flash all failed, exit code: 1, output: "Flash xbl error"
Click to expand...
Click to collapse
I have a tool called unlock tool which can flash your device in edl mode.
I can flash your device if it is Lavender. I have access to auth flash your device.
mvikrant97 said:
I have a tool called unlock tool which can flash your device in edl mode.
View attachment 5918089
I can flash your device if it is Lavender. I have access to auth flash your device.
View attachment 5918093
Click to expand...
Click to collapse
Hi there,
Well I am out of ideas. No matter what kind of recovery images i tried to flash, Im always getting the same error "too many open files in system"
If you think your method could be successfull I can try it. I really dont know what else i can do.
Tavero said:
Hi there,
Well I am out of ideas. No matter what kind of recovery images i tried to flash, Im always getting the same error "too many open files in system"
If you think your method could be successfull I can try it. I really dont know what else i can do.
Click to expand...
Click to collapse
Please follow this post and let me know if it works and then I'll help you out.
Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing
Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing Modified by Zesuga Features: Free auth bypass (EDL Mobile) No need credit balance or activation Free unlock EDL Auth device and flash Only need to boot the device in EDL mode What's new...
forum.xda-developers.com