Database Info

Boot stuck at LG logo. Download mode Send Command returns nothing.

What started with non-functional BT (other thread in this forum) is now a seemingly (soft?) bricked device. Here's my situation:
- dd'd a ZV9 rootedsystem.img (I was already running a ZV9 rooted system) hoping would fix my BT problems
- Instead boot now stuck at LG logo
- Can boot recovery
- Can start DL mode
- Have a backup of system.img but Send_Command.exe does nothing regardless cmd sent except LEAVE which reboots
- Factory reset, wiped cache, etc etc.
Why doesn't send command in dl mode work anymore?!?! Going insane. Please help!

Do you have the stock system.img or rootedsystem.img in internal storage?
Enviado desde mi LG-H955 mediante Tapatalk

pelelademadera said:
Do you have the stock system.img or rootedsystem.img in internal storage?
Enviado desde mi LG-H955 mediante Tapatalk
Click to expand...
Click to collapse
Yes, rootedsystem.img and backup system.img in internal storage. But I can't seem to access it.

hallucinate said:
Yes, rootedsystem.img and backup system.img in internal storage. But I can't seem to access it.
Click to expand...
Click to collapse
Poibt absolutly to the directory... But if you wipe data, or factory reset... You erase the img...
Enviado desde mi LG-H955 mediante Tapatalk

pelelademadera said:
Poibt absolutly to the directory... But if you wipe data, or factory reset... You erase the img...
Enviado desde mi LG-H955 mediante Tapatalk
Click to expand...
Click to collapse
Yep... factory reset / wiped data. Sounds like I'm screwed then.

In the same boat. if anyone finds a fix please help. I feel like my system partition is corrupted

Unfortunately, I ended up shipping to LG service. If LG would realize how much money they're losing out on by keeping their bootloader locked, it seems a likely enough incentive.
Anyway, if I had been able to use Send_Command, I'd have attempted what these guys are doing over in this thread. http://forum.xda-developers.com/g-flex2/help/to-unbrick-g-flex-2-ls996-t3286105 Have yet to see why in the world Send_Command stopped working though. Corrupt system partition as you @x4gvnferdy suggested seems as likely as any idea, but how dd failed so silently yet catastrophically I can't fathom.

Anyway, if I had been able to use Send_Command, I'd have attempted what these guys are doing over in this thread. http://forum.xda-developers.com/g-flex2/help/to-unbrick-g-flex-2-ls996-t3286105 Have yet to see why in the world Send_Command stopped working though. Corrupt system partition as you @x4gvnferdy suggested seems as likely as any idea, but how dd failed so silently yet catastrophically I can't fathom.[/QUOTE]
If you did the factory reset, you lost your rooted system.img and on this occasion the dd command wasn't working. It couldn't have executed something being removed off.
If you gonna do something kinda tricky, make sure to have system.img on your internal as there have been lot of us being forced to send the devive back to LG as none have seemed to figure this out. I've heard that in US guys get the device back in a week, I was without that 30 days. I gave upon any mod on my H955. Just rooted it again, put xposed on and finito. This snazzy phone is doomed because of no bootloader unlocked nor we get Android M as I fear. Globally it didn't bring money LG expected so they really don't care what we think.

I have the same issue. After flashing with dd, my phone now boots up to a No Command screen. I can enter recovery and download mode, but Send_Command.exe no longer works.

If u could boot into DL why don't you just try LG Mobile Support Tool or LGUP?

Hard bricked (dead) mi4i

does any one know a detailed methord to unbrick... a Hard bricked device....
it got hard Bricked while flashing stock miui....
I can not get into fastboot mode...
Hard Bricked.....

your device have a red blinking LED?
can your computer / laptop detect your phone?
if yes
do a fastboot again... , or do it 1 by 1
"Fastboot flash system system.img" and so on

We can't kill qualcomm devices...They can be saved from any stage...Use Qfil to flash(if fastboot mode is not working)...

mi 4i does not boot up
My mi 4i does not boot up does not going to fast boot when i connect it to pc no charging symbol bt pc showd usb device doesnot recognise code 43

Install mi4i Qualcomm drivers and flash using latest miflash tool.
Flash tool will recognize the device as com 10 or com 30 or something like that

Sharath007 said:
We can't kill qualcomm devices...They can be saved from any stage...Use Qfil to flash(if fastboot mode is not working)...
Click to expand...
Click to collapse
hello
I have a bricked Mi4i I am trying to restore, can u help me with the steps required to use Qfil; as in what files to download and stuff like that? I downloaded the QFIL, installed the drivers( my phone shows up in Device Manage>Port>Qualcomm HS-USB Diagnostics 9006)
Thank you for your help.

faizauthar12 said:
your device have a red blinking LED?
can your computer / laptop detect your phone?
if yes
do a fastboot again... , or do it 1 by 1
"Fastboot flash system system.img" and so on
Click to expand...
Click to collapse
Hello @faizauthar12.
Can you help me with the steps required to unbrick a hardbricked Mi4i?
The phone had the red led blinking and no mi logo, no recovery and no fastboot.
it is recognized by my pc as Qualcomm HS-USB Diagnostics 9006.
and when I connect to the PC, it shows 4 drives that says it needs to be formatted.
Any help is appreciated. Thank you very much.
Regards
Regan

faizauthar12 said:
your device have a red blinking LED?
can your computer / laptop detect your phone?
if yes
do a fastboot again... , or do it 1 by 1
"Fastboot flash system system.img" and so on
Click to expand...
Click to collapse
Hello @faizauthar12.
Can you help me with the steps required to unbrick a hardbricked Mi4i?
The phone had the red led blinking and no mi logo, no recovery and no fastboot.
it is recognized by my pc as Qualcomm HS-USB Diagnostics 9006.
and when I connect to the PC, it shows 4 drives that says it needs to be formatted.
Any help is appreciated. Thank you very much.
Regards
Regan

reganEZ said:
Hello @faizauthar12.
Can you help me with the steps required to unbrick a hardbricked Mi4i?
The phone had the red led blinking and no mi logo, no recovery and no fastboot.
it is recognized by my pc as Qualcomm HS-USB Diagnostics 9006.
and when I connect to the PC, it shows 4 drives that says it needs to be formatted.
Any help is appreciated. Thank you very much.
Regards
Regan
Click to expand...
Click to collapse
flash your phone with fastboot ROM by usign Xiaomi Mi flash tools

reganEZ said:
Hello @faizauthar12.
Can you help me with the steps required to unbrick a hardbricked Mi4i?
The phone had the red led blinking and no mi logo, no recovery and no fastboot.
it is recognized by my pc as Qualcomm HS-USB Diagnostics 9006.
and when I connect to the PC, it shows 4 drives that says it needs to be formatted.
Any help is appreciated. Thank you very much.
Regards
Regan
Click to expand...
Click to collapse
Happened for me once. Refer this
http://en.miui.com/forum.php?mod=viewthread&tid=474376&mobile=2
You can find videos on QPST in YouTube.

faizauthar12 said:
flash your phone with fastboot ROM by usign Xiaomi Mi flash tools
Click to expand...
Click to collapse
When i try that, the phone is detected as 12345...and then the status bar reaches 100% but nothing else happens. How long does it take for it to flash? any particular miflash tools version or ROM versions?
Thank you
---------- Post added at 12:39 PM ---------- Previous post was at 11:53 AM ----------
Sharath007 said:
Happened for me once. Refer this
http://en.miui.com/forum.php?mod=viewthread&tid=474376&mobile=2
You can find videos on QPST in YouTube.
Click to expand...
Click to collapse
When i try the QFIL method, it says "cant switch to EDL mode or something"
Any help?
Thanks in advance

here is the screenshot btw

reganEZ said:
here is the screenshot btw
Click to expand...
Click to collapse
Seems like you are flashing Android lollipop. Have you tried flashing miui 8 or 9 on Android M using miflash.
Also use old miflash tool, to avoid any compatibility issues.

Sharath007 said:
Seems like you are flashing Android lollipop. Have you tried flashing miui 8 or 9 on Android M using miflash.
Also use old miflash tool, to avoid any compatibility issues.
Click to expand...
Click to collapse
Ok I will try that too. When u say old miflash which version wud u recommend?

reganEZ said:
Ok I will try that too. When u say old miflash which version wud u recommend?
Click to expand...
Click to collapse
Miui 8 or 9 fastboot rom contains repair scripts as well. When you flash them, it should solve issues if any.
Use any of 2015 year releases like
MiFlash 2015.06.01.0
Load all files properly and also use flash all while flashing. It should work.

Sharath007 said:
Miui 8 or 9 fastboot rom contains repair scripts as well. When you flash them, it should solve issues if any.
Use any of 2015 year releases like
MiFlash 2015.06.01.0
Load all files properly and also use flash all while flashing. It should work.
Click to expand...
Click to collapse
I tried this too. it takes about 114 seconds and says operation completed successfully but the phone wont still boot up

reganEZ said:
I tried this too. it takes about 114 seconds and says operation completed successfully but the phone wont still boot up
Click to expand...
Click to collapse
For final attempts ...
1.Use different usb cable and try or other desktop.
2. Connect phone by press and holding vol up and vol down and power buttons , wait until you hear sound and then flash . If no use, try different combinations like holding volume up alone
3. Use QPST method for flashing(this is how i unbricked my mobile after flashing wrong bootloader)

Try flashing MIUI fastboot ROM using "command prompt", instead of Mi flastool, you can find the procedure of it on miui forum..

[Guide] Root twrp Firmware for Xiaomi MI 5X [tiffany]

Guide for MI 5X users-
This is a Step by Step by Step guide for MI 5X users to Install twrp obtain Root Right Flash Firmware etc......i already Share a guide on My blog [Stupdroid] and Finally Here with You..
Disclaimer-
Code:
i am not Responsible for any Damage to your Phone, Dead SD card, etc...
How to Install twrp and Root MI 5X
Download MI 5X toolkit From here https://forum.xda-developers.com/mi-5x/development/twrp-mi-5x-tiffany-t3655722
unlock bootloader from Here http://en.miui.com/unlock/
then run exe file from toolkit folder and Follow screen Instructions...
type 41 hit enter to flash twrp, just after flashing the recovery your phone booted in twrp so type 45 and hit enter it will transfer Require files to your Phone.
Go to backup tab and create a nandroid backup
then Do a factory reset
Go to Install tab/From SD card/ locate No verity and flash
again Go to Install/ From SD card Locate magisk Flash
reboot System Now.....
if not bootup again flash noverity....
Done. Successfully Rooted......
How to unbrick Flash official Firmware-
official way...
Note- you can use below Method [unofficial way] to unbrick Without locking the Bootloader [100% working]
Download official fastboot ROM From here http://en.miui.com/a-234.html
Extract inside a Folder
Run MI flash Locate Extracted Folder
Reboot phone in bootloader and Connect to PC with USB
on MI flash Click Flash
Wait For Success.....
Done...
unofficial way.
How to Flash Latest update without locking the Bootloader-
Don't worry i prepare a tool which is able to flash full Xiaomi ROM Without Locking the Bootloader
1. Download one Click Flash xiaomi from http://www.mediafire.com/file/0vs9h6afy9i8icj/flash_xiaomi.rar
2. Download Latest fastboot ROM from Here http://en.miui.com/a-234.html
3. Extract Xiaomi ROM [images]] in one click tool folder
4. reboot phone to fastboot mod and connect to pc with usb
5. Run flash xiaomi, wait for success. Done You have Latest ROM Without Locking the Bootloader but it will erase all data of phone because this is a Full ROM. again flash twrp using above step or you can delete recovery.img file from rom folder during flashing to skip the recovery flashing.
Convert China ROM to Global [MIUI 9]-
1. you have Flash latest China ROM without Locking the Bootloader using above steps
2. flash supersu/magisk to Root again because Root is lossed after flashing the Complete ROM
3. Go to root explorer/ system/ build.prop/ edit build.prop and add below values
Code:
ro.product.mod_device=scorpio_mam_global
ro.product.locale.language=it
ro.product.locale.region=IT
persist.sys.timezone=Europe/Rome
persist.sys.language=it
persist.sys.region=IT
ro.product.locale.language=it
Change values according your country save and reboot all chines content are removed... Done.
if you have Dead MI 5X follow this Guide....
https://forum.xda-developers.com/mi-5s/how-to/how-to-flash-hard-bricked-mi-5s-mi-5s-t3490252

Network disconnect continuously
Hi , i purchaged mi 5x from china n using in india. Here reliance jio network constantly disconnected . How can i fix it? Please help me.. all other sim work perfectly in mi 5x and Jio sim work perfectly in other mi device.
---------- Post added at 04:11 PM ---------- Previous post was at 03:59 PM ----------
And my second question , how to edit build pro for india.. cause many useful app does not work due to chines locale...thank you

did they block this recently? because i have permission and i always get error

I thought I was doing something wrong, until I realized there's a bit of a wait between flashing twrp and rebooting.

Yay, I got nice brick.
All I see is Linux penguin sitting in the middle of the screen.
What I did was copying .img files from tiffany images .tgz to Flash Xiaomi folder, because in the description didn´t say Copy folder named images...

I need "emmc_appsboot.mbn" file from a working MD E2 devices.
Any body can help me pls. My mi5x device is now on black secreen. Not openning..
it became after load orijinal rom onto oxygen boot.
Any body can help me pls
I need "emmc_appsboot.mbn" file from a working MD E2 devices.

Work in my device.
Thanks for sharing.

Brick
Do not follow the unofficial way described above. you will surely get a brick
i have experienced a lot of trouble by folllowing that unofficial way. A lots of error will occurred and will get a penguin screen with no fastboot or anything else. So be careful before use it.

I need your help/opinion | MIUI 9 on Mi A1 Project (Take #26427372872637473)

Hi there,
You probably are tired of seeing these kinds of threads (MIUI 9 on tissot) but I really want to help.
I did some research and:
It's not worth it to use this A/B partitioning for Custom ROMs
Flashing gpt-both.bin actually brings the normal partitions from the Mi 5X to the Mi A1
Now, it doesn't stop there.
In the past some people here posted with their hard bricked phones after trying to flash the 5X firmware. But they did the same thing:
Flash gpt-both.bin from Mi 5X using fastboot
Used Mi Flash Tool to flash the Mi 5X firmware (which locked their bootloader, the ROM didn't boot, they were stuck at the boot logo of the 5X, but fastboot actually detected their phones as tiffany and not tissot. unfortunately since the flash tool locked their bootloader, they weren't able to make any additional operations)
But there is one guy on YouTube who got MIUI 9 working by flashing the full 5X firmware using a Ufi Box - directly onto the EMMC. Many people don't believe it but I do since he even showed his IMEI and it really is a Mi A1 shipped to Indonesia.
He has a pretty bad English and he doesn't comment. He only said how he done it - he backed up QCN and used Ufi Box. But he also finished with "sometimes firmware not compatible with ur device, its make it hard bricked".
So I need your help with the following question: if the device gets a completely stock firmware, fresh from the Mi 5X, why did it work with the guy's Ufi Box and it didn't work with the guys using Mi Flash Tool. And about this "sometimes firmware not compatible", what defines whether it will be compatible with an exact Mi A1 and not compatible with another?

I wonder why the Mi Flash Tool would lock the bootloader. Aren't there multiple scripts for flashing, one that locks the BL, and others that don't? Or does all of them lock?

nicolasmart said:
Hi there,
You probably are tired of seeing these kinds of threads (MIUI 9 on tissot) but I really want to help.
I did some research and:
It's not worth it to use this A/B partitioning for Custom ROMs
Flashing gpt-both.bin actually brings the normal partitions from the Mi 5X to the Mi A1
Now, it doesn't stop there.
In the past some people here posted with their hard bricked phones after trying to flash the 5X firmware. But they did the same thing:
Flash gpt-both.bin from Mi 5X using fastboot
Used Mi Flash Tool to flash the Mi 5X firmware (which locked their bootloader, the ROM didn't boot, they were stuck at the boot logo of the 5X, but fastboot actually detected their phones as tiffany and not tissot. unfortunately since the flash tool locked their bootloader, they weren't able to make any additional operations)
But there is one guy on YouTube who got MIUI 9 working by flashing the full 5X firmware using a Ufi Box - directly onto the EMMC. Many people don't believe it but I do since he even showed his IMEI and it really is a Mi A1 shipped to Indonesia.
He has a pretty bad English and he doesn't comment. He only said how he done it - he backed up QCN and used Ufi Box. But he also finished with "sometimes firmware not compatible with ur device, its make it hard bricked".
So I need your help with the following question: if the device gets a completely stock firmware, fresh from the Mi 5X, why did it work with the guy's Ufi Box and it didn't work with the guys using Mi Flash Tool. And about this "sometimes firmware not compatible", what defines whether it will be compatible with an exact Mi A1 and not compatible with another?
Click to expand...
Click to collapse
Gpt will repartition device

nicolasmart said:
Hi there,
You probably are tired of seeing these kinds of threads (MIUI 9 on tissot) but I really want to help.
I did some research and:
It's not worth it to use this A/B partitioning for Custom ROMs
Flashing gpt-both.bin actually brings the normal partitions from the Mi 5X to the Mi A1
Now, it doesn't stop there.
In the past some people here posted with their hard bricked phones after trying to flash the 5X firmware. But they did the same thing:
Flash gpt-both.bin from Mi 5X using fastboot
Used Mi Flash Tool to flash the Mi 5X firmware (which locked their bootloader, the ROM didn't boot, they were stuck at the boot logo of the 5X, but fastboot actually detected their phones as tiffany and not tissot. unfortunately since the flash tool locked their bootloader, they weren't able to make any additional operations)
But there is one guy on YouTube who got MIUI 9 working by flashing the full 5X firmware using a Ufi Box - directly onto the EMMC. Many people don't believe it but I do since he even showed his IMEI and it really is a Mi A1 shipped to Indonesia.
He has a pretty bad English and he doesn't comment. He only said how he done it - he backed up QCN and used Ufi Box. But he also finished with "sometimes firmware not compatible with ur device, its make it hard bricked".
So I need your help with the following question: if the device gets a completely stock firmware, fresh from the Mi 5X, why did it work with the guy's Ufi Box and it didn't work with the guys using Mi Flash Tool. And about this "sometimes firmware not compatible", what defines whether it will be compatible with an exact Mi A1 and not compatible with another?
Click to expand...
Click to collapse
He repartition his mobile using ufi box , mi flash tool didn't repartition a device

nicolasmart said:
Hi there,
You probably are tired of seeing these kinds of threads (MIUI 9 on tissot) but I really want to help.
I did some research and:
It's not worth it to use this A/B partitioning for Custom ROMs
Flashing gpt-both.bin actually brings the normal partitions from the Mi 5X to the Mi A1
Now, it doesn't stop there.
In the past some people here posted with their hard bricked phones after trying to flash the 5X firmware. But they did the same thing:
Flash gpt-both.bin from Mi 5X using fastboot
Used Mi Flash Tool to flash the Mi 5X firmware (which locked their bootloader, the ROM didn't boot, they were stuck at the boot logo of the 5X, but fastboot actually detected their phones as tiffany and not tissot. unfortunately since the flash tool locked their bootloader, they weren't able to make any additional operations)
But there is one guy on YouTube who got MIUI 9 working by flashing the full 5X firmware using a Ufi Box - directly onto the EMMC. Many people don't believe it but I do since he even showed his IMEI and it really is a Mi A1 shipped to Indonesia.
He has a pretty bad English and he doesn't comment. He only said how he done it - he backed up QCN and used Ufi Box. But he also finished with "sometimes firmware not compatible with ur device, its make it hard bricked".
So I need your help with the following question: if the device gets a completely stock firmware, fresh from the Mi 5X, why did it work with the guy's Ufi Box and it didn't work with the guys using Mi Flash Tool. And about this "sometimes firmware not compatible", what defines whether it will be compatible with an exact Mi A1 and not compatible with another?
Click to expand...
Click to collapse
May be after re partitioning, while using the Mi Flash tool, we can replace the stock recovery with the TWRp for tiffany, and flash the ROM. Once the flashing is done, we boot into recovery, flash some lazy-flasher.zip or something which disables dm-verify flag during boot and hence the ROM might boot right?
Just my idea. Kindly let me know if it works. :fingers-crossed:

UFI box is powerful hardware base tool... Used widely by phone technician in Indonesia and Malaysia and Singapore. So it cant be compared with flashing tool like Mi flash tools.

awandroid89 said:
UFI box is powerful hardware base tool... Used widely by phone technician in Indonesia and Malaysia and Singapore. So it cant be compared with flashing tool like Mi flash tools.
Click to expand...
Click to collapse
Yeah, and it's not really cheap.
Sent from my Mi A1 using XDA Labs

awandroid89 said:
UFI box is powerful hardware base tool... Used widely by phone technician in Indonesia and Malaysia and Singapore. So it cant be compared with flashing tool like Mi flash tools.
Click to expand...
Click to collapse
Gpt.bin enough for repartition of our device to mi 5x , i looking for any mi 5x owner give me that file
Procedure is simple
Boot into twrp
Connect mobile with pc
Open adb folder and give following command in commad promot
Adb shell "dd if=/dev/block/mmcblk0 of=/sdcard/gpt.bin bs=512 count=34"
It save gpt.bin in you internal
Please upload here any mi 5x user , and yes then we can get recovery partition but we lost A/B

your point is correct that partition slots is not necessary for roms

I just hope someone get a TWRP falshable zip to get the a/b into 1. I remember from mi Mi3 days, there was a guy who did it so the system partition was 1.2bg and not 500+ in each partition. This multiple partiyon thing is a pain.
I am unable to find the thread but it's here somewhere. I however, was able to find this if this helps.
https://forum.xda-developers.com/xiaomi-mi-3/general/howto-resize-extend-partition-capacity-t3011918

zeyaan said:
I just hope someone get a TWRP falshable zip to get the a/b into 1. I remember from mi Mi3 days, there was a guy who did it so the system partition was 1.2bg and not 500+ in each partition. This multiple partiyon thing is a pain.
I am unable to find the thread but it's here somewhere. I however, was able to find this if this helps.
https://forum.xda-developers.com/xiaomi-mi-3/general/howto-resize-extend-partition-capacity-t3011918
Click to expand...
Click to collapse
i had a Mi3 as well and i remember doing this

this is what i did
I saw this video and i remembered that i have bst box
I already deep flashed mi 5x rom
I just got my device hard bricked ( dead boot)
Can not get into fastboot, recovery or EDL mode
When i press power botton i got vibration and no thing else
I could not even charge it
So i just need to repartition my device so i could flash mi 5x and boot successful
Do you know how to repartition my device?
Sorry for my bad language

Okay, since there are multiple ways of porting MIUI, and the most obvious way (using the stock 5X rom) does not
seem to work straight without causing bricked phones, why not do it the way it has been done for years now, which is
taking a AOSP base rom image for our phone (which we do have) and copying files from a MIUI phone, as hardware-close as possible (we are in the fine situation of having the most hardware-like MIUI phone there ever was) to the base and doing the port this way.
I have little knowledge about how the partitions work with this phone but unless I try, I guess I´ll never find out.
As you see I am willing to start at least something, maybe there is someone who wants to join the ride and support me with knowledge, advice and so on..
I am not a rom dev, I have started porting MIUI 8 to my S7 (building it from source and fighting my way through tons of rejects) until someone came up with MIUI for the s7 and I eventually lost interest in the whole thing... so I don´t want to raise anybodys expectations here like many already did and came up with nothing in the end.
I just want to try and do at least something... Any advice on the partition issue?

Bro it might help Look. He converted kenzo to kate they both are identifical device with partition change like mi a1 and mi 5x.
Readcarefully :-
(Try it only if u know how to unbrick bcoz using firehose progmammer to flash is dangerous it force install without verifying )
https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-convert-kenzo-to-kate-t3455369

Found a tool to reparation any device. Check this out.
https://forum.xda-developers.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036

Our partitition table:
Code:
Found valid GPT with protective MBR; using GPT
Disk /dev/block/bootdevice/mmcblk0: 122142720 sectors, 2296M
Logical sector size: 512
Disk identifier (GUID):
Partition table holds up to 52 entries
First usable sector is 34, last usable sector is 122142686
Number Start (sector) End (sector) Size Name
1 131072 303103 84.0M modem_a
2 303104 475135 84.0M modem_b
3 524288 524289 1024 fsc
4 524290 524305 8192 ssd
5 524306 525329 512K sbl1
6 525330 526353 512K sbl1bak
7 526354 527377 512K rpm
8 527378 528401 512K rpmbak
9 528402 532497 2048K tz
10 532498 536593 2048K tzbak
11 536594 537105 256K devcfg
12 537106 537617 256K devcfgbak
13 537618 570385 16.0M dsp
14 570386 573457 1536K modemst1
15 573458 576529 1536K modemst2
16 655360 655423 32768 DDR
17 655424 658495 1536K fsg
18 658496 658527 16384 sec
19 786432 808959 11.0M splash
20 917504 919551 1024K aboot
21 919552 921599 1024K abootbak
22 921600 1052671 64.0M boot_a
23 1052672 1183743 64.0M boot_b
24 1183744 1185791 1024K devinfo
25 1185792 7477247 3072M system_a
26 7477248 13768703 3072M system_b
27 13893632 13959167 32.0M persist
28 13959168 13961215 1024K misc
29 13961216 13962239 512K keystore
30 13962240 13962303 32768 config
31 14024704 14024767 32768 limits
32 14155776 14156799 512K mota
33 14156800 14158847 1024K dip
34 14158848 14224383 32.0M mdtp
35 14224384 14225407 512K syscfg
36 14225408 14233599 4096K mcfg
37 14286848 14287103 128K lksecapp
38 14287104 14287359 128K lksecappbak
39 14287360 14287871 256K cmnlib
40 14287872 14288383 256K cmnlibbak
41 14288384 14288895 256K cmnlib64
42 14288896 14289407 256K cmnlib64bak
43 14289408 14289919 256K keymaster
44 14289920 14290431 256K keymasterbak
45 14417920 14418431 256K apdp
46 14418432 14418943 256K msadp
47 14418944 14418959 8192 dpo
48 14418960 14550031 64.0M logdump
49 14550032 122142686 51.3G userdata

I also tried to know if mi 5x rom will fit to mi a1 i flashed mi 5x rom via edl mode. Happens it locks bootloader recovery can be accessed but booting the device stock at mi logo and reboot again and again
Any One tried getting ramdisk of boot.img of Mi 5x rom and put it on Mi A1 Boot Img just like porting it?

Miui 5x
Hello everybody! I started to port MIUI from 5X. Spent 5 days on bringing the boot and systems in line with the A/B structure, everything seems to be right.
I learned all the patches of the bootloader (lk), kernel and system, about A/B structure to find necessary files, and port update system A/B, selinux staff, and other corrections, but it do not want to start at my 8.0.
Everything is safe, no firmware or bootloader here will not be affected, only boot.img and system.img are flashed.
If anyone wants to participate, I post images for unpacking and picking, maybe I missed something ... in the archive, two unpretentious utilities for unpacking, just drag&drop the image of boot and systems to these programs.
Manual:
1. loading in Fastboot
2. check the current active slot (for example A)
Code:
fastboot getvar current-slot
3. Sew the boot and systems in the opposite slot
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash system_b system.img
4. Activates this slot
Code:
fastboot set_active b
5. reboot
Code:
fastboot reboot
Link:
https://mega.nz/#!8FACAZLK!WE6rSzuOknc3HvGBRc_3ATs8VdZXwEChocN4AsHjh78
new boot: https://mega.nz/#!YFB0xRgb!m3zutkPVVN_cbH297PY1fSHiz3tpmGLWulcxh6tEHZ4
The updated kernel, the phone is now in the booting well, at least something, then at the initial level everything is fine, then you need to pick the system.
My problem, I cant to get a logcat from initial booting to find crash problem.
Todo: https://mega.nz/#!wEI0lJLY!ufpMIO52ZVKl7_pAlzkUxqJ3C9Ldtflv3FYZY_kuoZ0

amar2cool99 said:
Gpt.bin enough for repartition of our device to mi 5x , i looking for any mi 5x owner give me that file
Procedure is simple
Boot into twrp
Connect mobile with pc
Open adb folder and give following command in commad promot
Adb shell "dd if=/dev/block/mmcblk0 of=/sdcard/gpt.bin bs=512 count=34"
It save gpt.bin in you internal
Please upload here any mi 5x user , and yes then we can get recovery partition but we lost A/B
Click to expand...
Click to collapse
Surely if you ask for help in the 5x forum someone can provide the necessary file.
Enviado desde mi Mi A1 mediante Tapatalk

xezrunner said:
I wonder why the Mi Flash Tool would lock the bootloader. Aren't there multiple scripts for flashing, one that locks the BL, and others that don't? Or does all of them lock?
Click to expand...
Click to collapse
All the scripts have "fastboot oem lock" (or at least as far as I'm concerned). I don't know why.
Uvneshkumar said:
May be after re partitioning, while using the Mi Flash tool, we can replace the stock recovery with the TWRp for tiffany, and flash the ROM. Once the flashing is done, we boot into recovery, flash some lazy-flasher.zip or something which disables dm-verify flag during boot and hence the ROM might boot right?
Just my idea. Kindly let me know if it works. :fingers-crossed:
Click to expand...
Click to collapse
IDK if it will work - I don't think the dm-verity will be broken since after a full reflash your device becomes a tiffany and the 5X firmware becomes the valid one - dm-verity is 100% OK with that.
amar2cool99 said:
Gpt.bin enough for repartition of our device to mi 5x , i looking for any mi 5x owner give me that file
Procedure is simple
....
Please upload here any mi 5x user , and yes then we can get recovery partition but we lost A/B
Click to expand...
Click to collapse
Why do you need someone to give you the gpt from the 5X? It's present in every fastboot ROM of the 5X.
mokahabashy said:
I saw this video and i remembered that i have bst box
I already deep flashed mi 5x rom
I just got my device hard bricked ( dead boot)
Can not get into fastboot, recovery or EDL mode
When i press power botton i got vibration and no thing else
I could not even charge it
So i just need to repartition my device so i could flash mi 5x and boot successful
Do you know how to repartition my device?
Sorry for my bad language
Click to expand...
Click to collapse
Dead giveaway - if you can't even get into EDL mode then you probably can't do anything about it but get a new phone.
maitrot said:
Okay, since there are multiple ways of porting MIUI, and the most obvious way (using the stock 5X rom) does not
seem to work straight without causing bricked phones, why not do it the way it has been done for years now, which is
taking a AOSP base rom image for our phone (which we do have) and copying files from a MIUI phone, as hardware-close as possible (we are in the fine situation of having the most hardware-like MIUI phone there ever was) to the base and doing the port this way.
I have little knowledge about how the partitions work with this phone but unless I try, I guess I´ll never find out.
As you see I am willing to start at least something, maybe there is someone who wants to join the ride and support me with knowledge, advice and so on..
I am not a rom dev, I have started porting MIUI 8 to my S7 (building it from source and fighting my way through tons of rejects) until someone came up with MIUI for the s7 and I eventually lost interest in the whole thing... so I don´t want to raise anybodys expectations here like many already did and came up with nothing in the end.
I just want to try and do at least something... Any advice on the partition issue?
Click to expand...
Click to collapse
MIUI 8 for S7 - Off-topic.
Hawiie13 said:
I also tried to know if mi 5x rom will fit to mi a1 i flashed mi 5x rom via edl mode. Happens it locks bootloader recovery can be accessed but booting the device stock at mi logo and reboot again and again
Any One tried getting ramdisk of boot.img of Mi 5x rom and put it on Mi A1 Boot Img just like porting it?
Click to expand...
Click to collapse
Did you use QFIL/MiFlash or Mi Flash Tool? I'm telling you - Mi Flash Tool won't help you. Only MiFlash/QFIL have chances of actually flashing the Mi 5X firmware and getting it to work. Do it on your own risk though. If you want to go back to stock AndroidOne just go to EDL again and use MiFlash/QFIL to flash tissot QFIL image.
miroslav_mm said:
Hello everybody! I started to port MIUI from 5X. Spent 5 days on bringing the boot and systems in line with the A/B structure, everything seems to be right.
I learned all the patches of the bootloader (lk), kernel and system, about A/B structure to find necessary files, and port update system A/B, selinux staff, and other corrections, but it do not want to start at my 8.0.
Everything is safe, no firmware or bootloader here will not be affected, only boot.img and system.img are flashed.
If anyone wants to participate, I post images for unpacking and picking, maybe I missed something ... in the archive, two unpretentious utilities for unpacking, just drag&drop the image of boot and systems to these programs.
Manual:
1. loading in Fastboot
2. check the current active slot (for example A)
Code:
fastboot getvar current-slot
3. Sew the boot and systems in the opposite slot
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash system_b system.img
4. Activates this slot
Code:
fastboot set_active b
5. reboot
Code:
fastboot reboot
Link:
https://mega.nz/#!8FACAZLK!WE6rSzuOknc3HvGBRc_3ATs8VdZXwEChocN4AsHjh78
new boot: https://mega.nz/#!YFB0xRgb!m3zutkPVVN_cbH297PY1fSHiz3tpmGLWulcxh6tEHZ4
The updated kernel, the phone is now in the booting well, at least something, then at the initial level everything is fine, then you need to pick the system.
My problem, I cant to get a logcat from initial booting to find crash problem.
Todo: https://mega.nz/#!wEI0lJLY!ufpMIO52ZVKl7_pAlzkUxqJ3C9Ldtflv3FYZY_kuoZ0
Click to expand...
Click to collapse
WOWOOWO!!! Holy ****! You made MIUI booting on our Mi A1??? Please create another thread pointing that 'cause you might have just made the best ROM for our device yet!

[Recovery][cv1] TWRP 3.2.3.0 For LM-X210 Devices

Compatible Devices:
LG K8+
LG Aristo 2, 2+
LG K9
LG Phoenix 4
Thanks to @AustinGarrick1818 who discovered that this TWRP originally started and developed for the Aristo 2, by @messi2050 and @armandop_, then later updated to the latest version by @tecknight, was able to be flash on the Phoenix 4 leading to the idea that any cv1 device is cable of a ROOT method/TWRP Recovery.
Pre-Requisites:
USB Debugging Enabled​
OEM Unlock Enabled​
ADB/Fastboot Device Drivers​
Your Phone/Brain​
Hey guys! Just a heads up, I'm not responsible for any bricked devices or broken devices. So flash at your own risk! This TWRP has the Oreo Kernel from the Aristo 2's Oreo Firmware release.
Downloads
Latest Recovery by @tecknight Here --> https://www.androidfilehost.com/?fid=11410963190603906754​Latest USB Drivers --> https://www.lg.com/us/support/software-firmware-drivers​
Instructions:
1. Install the ADB Drivers from above. If you have them don't bother. Just move on. If you don't then make sure to install them somewhere easily accessible, as your gonna want to get to them easily.
2. Place the TWRP image in the ADB Folder for later use and plug your phone into your PC. Then press (Shift+Right Click) and select "Open Command Prompt Here".
3. After that type the next few lines of code:
Code:
adb devices
Code:
adb reboot bootloader
4. It should boot into fastboot mode. From there type:
Code:
fasboot devices
Code:
fastboot flashing unlock
5. To prevent fastboot from encrypting cache and data type:
Code:
fastboot erase userdata
Code:
fastboot erase cache
6.Remember the Recovery image? Rename it to rec.img and flash it like this:
Code:
fastboot flash recovery rec.img
7. Now that you've flashed TWRP test it:
Code:
fastboot reboot recovery
NOTE: Anytime you boot up your phone you will get a message saying that the bootloader is locked and you need to lock it. Don't do it. If you do then you phone will soft brick and get stuck in a bootloop. Just let it boot.
8. If you did everything right you should be brought to TWRP.
PLEASE LEAVE A THANKS! THANKS!

Downgrade?
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...

tdawgg777 said:
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
Click to expand...
Click to collapse
Yah, it's still like that unfortunately. But you can downgrade to Nougat with LG Uppercut. You should just flash the TWRP on Nougat firmware because it's not locked. So when you downgrade just follow these steps to get Oreo. Also don't install Tec's version of Oreo Firmware. Just jump to my other thread for my Custom Stock ROM. Tec's flashes Oreo Firmware with Oreo Stock Rooted. But mine just flashes the nesassary Oreo Boot and System. The links on my signature.
By the way for anyone wondering the LG Phoenix 4 can be Rooted this way to.

NonStickAtom785 said:
Compatible Devices:
LG K8+
LG Aristo 2, 2+
LG K9
LG Phoenix 4
Thanks to @AustinGarrick1818 who discovered that this TWRP originally started and developed for the Aristo 2, by @messi2050 and @armandop_, then later updated to the latest version by @tecknight, was able to be flash on the Phoenix 4 leading to the idea that any cv1 device is cable of a ROOT method/TWRP Recovery.
Pre-Requisites:
USB Debugging Enabled
OEM Unlock Enabled
ADB/Fastboot Device Drivers
Your Phone/Brain
Hey guys! Just a heads up, I'm not responsible for any bricked devices or broken devices. So flash at your own risk! This TWRP has the Oreo Kernel from the Aristo 2's Oreo Firmware release.
Downloads
Latest Recovery by @tecknight Here --> https://www.androidfilehost.com/?fid=11410963190603906754
Latest USB Drivers --> http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Instructions:
1. Install the ADB Drivers from above. If you have them don't bother. Just move on. If you don't then make sure to install them somewhere easily accessible, as your gonna want to get to them easily.
2. Place the TWRP image in the ADB Folder for later use and plug your phone into your PC. Then press (Shift+Right Click) and select "Open Command Prompt Here".
3. After that type the next few lines of code:
4. It should boot into fastboot mode. From there type:
5. To prevent fastboot from encrypting cache and data type:
6.Remember the Recovery image? Rename it to rec.img and flash it like this:
7. Now that you've flashed TWRP test it:
NOTE: Anytime you boot up your phone you will get a message saying that the bootloader is locked and you need to lock it. Don't do it. If you do then you phone will soft brick and get stuck in a bootloop. Just let it boot.
8. If you did everything right you should be brought to TWRP.
PLEASE LEAVE A THANKS! THANKS!
Click to expand...
Click to collapse
If fastboot flashing unlock fails try fastboot oem unlock

tdawgg777 said:
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
Click to expand...
Click to collapse
As long as your bootloader is unlocked it won't be a problem at least on the LG Phoenix 4 it can have TWRP with Oreo

hello good night I can not enter bootloader mode I always reboot in normal mode the phone, I do it this way c: adb / adb reboot bootloader but I started normal tengop a lg k9 x210em I do not understand the truth any suggestion excuse my English

hello good night I can not enter bootloader mode I always reboot in normal mode the phone, I do it this way c: adb / adb reboot bootloader but I started normal, a lg k9 x210hm I do not understand the truth any suggestion

tazlooney89 said:
hello good night I can not enter bootloader mode I always reboot in normal mode the phone, I do it this way c: adb / adb reboot bootloader but I started normal, a lg k9 x210hm I do not understand the truth any suggestion
Click to expand...
Click to collapse
on my device is the same

Problem!!!
I do what you write in tutorial but my phone dont run on fastboot mode Please HELP!!!

Do we know anything about unbricking these phones? I've got a US Cellular K8+ (LG-X210ULM) that my wife accidentally bricked a while back while trying to flash TWRP (not this particular build, obviously). I think she said everything seemed fine and then on reboot...well, it just never turned on again. PC doesn't pick it up at all, no Qualcomm mode or anything. Based on that, I had assumed it was a lost cause that would take JTAG to bring back, and it may well be...
...but then I noticed something unusual the other day. For the hell of it, I decided to plug it into a charger and let it sit for a while. I got what I expected, which was nothing at all. Oh well. Anyway, I happened to be working with another X210 at the time but only had one battery handy, so I just popped the one out of the "dead" phone without unplugging it and went about with what I was doing. After about 5-10 minutes, something caught my eye - sure enough, the dead phone's screen was now on, displaying the "?" battery screen. I put the battery back into the phone and got unceremoniously dumped straight back to black nothingness. Oh well.
So yeah, the phone still doesn't seem to respond to anything when connected to the PC with no battery, so it's probably a no-go, but the fact that it still shows the no-battery screen tells me it's not quite *as* bricked as I thought it was at least. Any ideas? Are we lucky enough to do a boot-from-SD trick on this phone?

Lmx210cm twrp
Do you happen to have anything for the lmx210cm?

Ausboz said:
Do you happen to have anything for the lmx210cm?
Click to expand...
Click to collapse
Just created a whole EDL firmware for the Aristo 2 aka Phoenix 4. PM me for the links if you'd like a copy. I also found our prog_emmc_firehose_8917_ddr.mbn to flash with (it works)
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
tdawgg777 said:
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
Click to expand...
Click to collapse
I tested oreo and it works file

AustinGarrick1818 said:
Just created a whole EDL firmware for the Aristo 2 aka Phoenix 4. PM me for the links if you'd like a copy. I also found our prog_emmc_firehose_8917_ddr.mbn to flash with (it works)
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
I tested oreo and it works file
Click to expand...
Click to collapse
Hi would mind telling how to flash that firmware amd whats the prog_+++++++ddr.mbn to flash i have aristo 2 android 8.1 metro and i cant do any flash in fastboot or root it anything you know about it will be appreciated so much...

@NonStickAtom785 Any solution to start fastboot mode, the phone? Whenever I try to start it from CMD the phone restarts normally, there is no way to get into fastboot mode.
I already probe manually, with combination of buttons, and it does not work either, the model is the LX210HM

tazlooney89 said:
@NonStickAtom785 Any solution to start fastboot mode, the phone? Whenever I try to start it from CMD the phone restarts normally, there is no way to get into fastboot mode.
I already probe manually, with combination of buttons, and it does not work either, the model is the LX210HM
Click to expand...
Click to collapse
Have you tried installing the Aristo 2 firmware on your phone? In theory these phones have the same build and processors. Also in theory, but proven to work on some other cv1 devices (LG Phoenix 4), you should be able to flash Aristo 2 firmware and unlock your phone that way. I would also check your system.img to see if anything such as a security patch is in place to keep your phone from rebooting to the bootloader. You can backup the system.img manually and send me the img and I will look for anything that different from the Aristo 2 system.img.
Also by backing up the system.img and sending it to me, I can retrieve any "extra" carrier settings and add them to the cv1 img. I'm working on a full stock cv1 firmware img that will work on all the cv1 devices as a root strategy.

I have Lg K9 ( lmx210em ) and it's IMPOSSIBLE enter in fastboot mode, either with key combinations, either with adb command... The phone always boot in normalk mode !!!
Download mode and recowery mode work properly, but fastboot mode DID NOT !!!

urgent
i need the firmware the phoenix 4 please

NonStickAtom785 said:
Compatible Devices:
LG K8+
LG Aristo 2, 2+
LG K9
LG Phoenix 4
Thanks to @AustinGarrick1818 who discovered that this TWRP originally started and developed for the Aristo 2, by @messi2050 and @armandop_, then later updated to the latest version by @tecknight, was able to be flash on the Phoenix 4 leading to the idea that any cv1 device is cable of a ROOT method/TWRP Recovery.
..............
[/COLOR][/SIZE]
Click to expand...
Click to collapse
I'm assuming this will not work on the LG Aristo 2 Verizon PrePaid LM-X210VPP ? Or am i wrong? I have one here in inventory that just needs a new LCD and Digitizer ($20) and I was thinking about fixing it and modding it but worried about Verizon and the bootloader being locked. Have not found a lot of info on this device just yet so debating whether or not to keep / fix or get rid of it.
---------- Post added at 01:24 AM ---------- Previous post was at 01:22 AM ----------
AustinGarrick1818 said:
Just created a whole EDL firmware for the Aristo 2 aka Phoenix 4. PM me for the links if you'd like a copy. I also found our prog_emmc_firehose_8917_ddr.mbn to flash with (it works)
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
I tested oreo and it works file
Click to expand...
Click to collapse
Did anyone get this guys debrick package? And does it have the xml's already created? Either way I would like a copy. If someone can pm me a link to a download or email me it that would be awesome.

i installed twrp and rooted the lmx210cm however now when i boot i shows a black bar at bottom of screen... top of image is cut off and touch screen is unresponsive.... works fine in twrp... what did i do wrong?

jdthomas4181 said:
i installed twrp and rooted the lmx210cm however now when i boot i shows a black bar at bottom of screen... top of image is cut off and touch screen is unresponsive.... works fine in twrp... what did i do wrong?
Click to expand...
Click to collapse
The issue you describe appears to be caused by kernel incompatibilities between certain partitions of the phone.
The fact that TWRP does not have the screen glitching issue implies that the kernel embedded in the TWRP image you flashed IS compatible, but perhaps the kernel within your boot image is NOT.
My first question would be:
You mention that you rooted your phone from fastboot.
Did you:
1. patch the stock boot image on your phone or
2. flash a pre-rooted boot image to your boot partition or
3. Flash a pre rooted ROM to your phone
If you answered #2 or #3, then my secondary question would be:
Specifically which boot image or ROM did you flash to your phone ?
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
noidodroid said:
I'm assuming this will not work on the LG Aristo 2 Verizon PrePaid LM-X210VPP ? Or am i wrong? I have one here in inventory that just needs a new LCD and Digitizer ($20) and I was thinking about fixing it and modding it but worried about Verizon and the bootloader being locked. Have not found a lot of info on this device just yet so debating whether or not to keep / fix or get rid of it.
---------- Post added at 01:24 AM ---------- Previous post was at 01:22 AM ----------
Did anyone get this guys debrick package? And does it have the xml's already created? Either way I would like a copy. If someone can pm me a link to a download or email me it that would be awesome.
Click to expand...
Click to collapse
I did not get the edl package, but I really want it and of course his account is suspended.
Anybody have it ?
Also this method should be capable of working on your phone, as it is a cv1 device.
You may have to downgrade the firmware to Nougat before proceeding if the device is currently running Oreo.
If the device is currently running Oreo or later, you can downgrade the phone to Nougat using the LGUP utility