Database Develop

MI3 Completely bricked!!!

Guys i have bricked MY mi3 16gb.
I was using Bitti opticancro build with extended partitiion.
as i want to go to miui v6. i flashed stock partition zip
Then i flashed miui stock recovery and tried to flash the miui latest rom
i forgot to rename the rom zip to update .zip so i couldnt insatll the miui rom.
the i tried to flash using fast fastboot mode but it is showing error as remote size too large.
now i am stuck with miui recovery and fastboot error.
pls help me to get back my phone.

If you can enter fastboot mode, then you can flash miui rom manually.
First unzip miui fastboot rom, place adb and fastboot files into the folder you just extracted. (ex. located in cancro_global_images_V6.4.3.0.KXDMICB_4.4_global\images)
And then press shift while in this folder to open terminal, type these one by one.
Code:
fastboot devices
fastboot flash tz tz.mbn
fastboot flash dbi sdi.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot erase boot
fastboot flash misc misc.img
fastboot flash modem NON-HLOS.bin
fastboot flash modem1 NON-HLOS.bin
fastboot flash system system.img
fastboot flash system1 system.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash boot1 boot.img
fastboot flash userdata userdata.img[B] (optional, need backup first, but I recommended to flash this if you want to use gapps)[/B]
fastboot reboot
You're done!
Android ADB Fastboot files is given if you don't have one.https://www.dropbox.com/s/ndud98a4ek3fvxg/Android_ADB_FASTBOOT.zip?dl=0

Or you can just fastboot flash TWRP recovery and then flash whatever you want from USB or something...

1)Install CWM recovery
2) Download restore-stock partition zip file from here http://www.htcmania.com/showpost.php?p=17750021&postcount=144
3) Flash it.
4) Now get in fastboot mode.
5) Get fasboot images from MIUI Forums
6) Flash it via MiFlash or use command line given by 2nd comment
7) Grab a coffee and you will be on miui in no time
8) use miui

Edit: http://xiaomi.eu/community/threads/5-5-8.27542/page-8#post-246332
There is modified flash_all.bat for Mi2, i beleive same works for cancro.
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash partition" && exit /B 1
Add this line after getvar and before flash lines in flash_all.bat and then MiFlash it like usually.

Flash cwm via fastboot, use "fastboot flash recovery recoveryname.img" and don't use this title, its not completely bricked.

Never run stock recovery until u manage to flash a stockrom.. Better remember that.. Save twrp or cwm.. In my case, on last monday, on twrp, i've accidentally wipe internal storage.. Luckily got 6 type of rom in usb-otg..

[Untested][Linux/ Mac] Fastboot package for Oreo January update

Hi all,
this one is for the brave, as it is still untested.
Nevertheless, please find here some information what I did:
Got the latest full OTA package here from xda
Extracted payload.bin into the fastboot compatible .img files
Adapted the "flash_all_except_storage script" in order to automate the flashing and included it
As I have right now (just my luck) an issue with fastboot not detecting my phone, I cannot test right now. Will try again myself in the evening though, at least that is the plan.
In the meantime any brave (no guarantees, no warranties) are welcome to test it. Apart from the above mentioned changes, it is the update as it was distributed by Xiaomi/ Google including the January security patch:
Android 8.0.0 [OPR1.170623.026.8.1.10]
link removed as official version is now available here
I am looking forward to your feedback.
P.S.: For more information how to use it, please have a look here
UPDATE: system.img seems to be not flashable right now and I have no more ideas right now what I could do about it. So sorry guys, back to waiting for Xiaomi again.

downloading...
will report the result later.
EDIT: Sorry, I just saw that it only includes a "flash_all_except_storage.sh" for Linux/Mac.. Could I use the *.bat script from an official fastboot image on this one?

i dont have a Mac, windows 10. how do i flash it ?

soeschelz said:
downloading...
will report the result later.
EDIT: Sorry, I just saw that it only includes a "flash_all_except_storage.sh" for Linux/Mac.. Could I use the *.bat script from an official fastboot image on this one?
Click to expand...
Click to collapse
Rawwr said:
i dont have a Mac, windows 10. how do i flash it ?
Click to expand...
Click to collapse
@ all dear Windows users: The scripts from the official fastboot package require some slight changes, due to some different namings. So far I have done this only for Linux/ Mac and included the appropriate script, but you could still flash the *.img files via the following fastboot commands:
Code:
fastboot oem unlock
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash abootbak aboot.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot set_active a
fastboot reboot

majamee said:
@ all dear Windows users: The scripts from the official fastboot package require some slight changes, due to some different namings. So far I have done this only for Linux/ Mac and included the appropriate script, but you could still either flash the *.img files via the following fastboot commands:
Code:
fastboot oem unlock
fastboot flash modem_a modem.img
Click to expand...
Click to collapse
cant you make a script ? it is hard to enter every code at once

@majamee
I tried to flash manually but no luck. It seem all OK until I flash system.img.
After I enter
Code:
fastboot flash system_a system.img
I got the following error:
Code:
invalid sparse file format at header magi
then it flashes system_a. Same with system_b. All other commands run without any error. After a reboot I'm stuck on bootsplash.
I used fastboot and adb linked in the thread mentioned in first post and had no problem with flashing the first Oreo.
I hope you understand me, I'm very tired and not a native speaker

soeschelz said:
@majamee
I tried to flash manually but no luck. It seem all OK until I flash system.img.
After I enter
I got the following error:
then it flashes system_a. Same with system_b. All other commands run without any error. After a reboot I'm stuck on bootsplash.
I used fastboot and adb linked in the thread mentioned in first post and had no problem with flashing the first Oreo.
I hope you understand me, I'm very tired and not a native speaker
Click to expand...
Click to collapse
Thank you for your helpful feedback. I will see if I can do something about it, except waiting for xiaomi to finally release the fastboot image themselves or I get my ota without reading play services data.

Can you explain me how you extracted payload.bin to .img files

ramesh1686 said:
Can you explain me how you extracted payload.bin to .img files
Click to expand...
Click to collapse
I can tell you the basic instructions, but for the details I have to ask you to please have a look yourself how to do it for your Operating System.
So,
You download both python scripts from here: https://gist.github.com/ius/42bd02a5df2226633a342ab7a9c60f15
You make sure you have installed python and google-protobuf binding for python
You open a terminal/ shell/ cmd and navigate via the "cd" command to the directory the payload.bin and the both .py scripts are
run the following command "payload_dumper.py payload.bin"
I personally did these parts on a Linux system as it was at least for me the easiest way to have python and protobuf set up in no time.
----
Btw. I had another look, if I can do something about the system.img not being flashable at the moment. Nevertheless no luck so far, I begin to wonder if the OTA package is really a full OTA, due to that or just a very big update as it is intended to update Android N to O...
Sorry, for the failed attempt, at least it was worth a try.

I had issue with "invalid sparse file format at header magi" before (also extracted image from OTA), but it flashed successfully. Flashing just took longer than usual. However I had issues with failed video recording and the only fix for me was to use full flash of stock fastboot ROM. There might be something missing in extracted images from OTA package.

I have unpacked the latest payload.bin file from Android 8.0.0 [OPR1.170623.026.8.1.10] and the size of the system.img is 3.2 GB . This is too much?
The system partition has a size of 3072 MB. It's some error of unpacking?

Fastboot ROM is available http://bigota.d.miui.com/8.1.10/tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b.tgz
Source: http://en.miui.com/thread-1596182-1-1.html

exit from fastboot mode

starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/open?id=16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase system
fastboot erase modem
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash dsp dspso.bin
fastboot flash parameter parameter.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img (if you failed, don't worry, try this step again and again.)
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.

emmegitony said:
Download download necessary files https://drive.google.com/drive/folde...Ym?usp=sharing
good luck.
Click to expand...
Click to collapse
404. That’s an error.
The requested URL was not found on this server. That’s all we know.

nabbed said:
404. That’s an error.
The requested URL was not found on this server. That’s all we know.
Click to expand...
Click to collapse
modified link: https://drive.google.com/open?id=16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm

Question Flashing TWRP doesn't work (Xiaomi Redmi 9t)

Hello,
After unlock his bootloader, I try to install TWRP recovery on my smartphone with :
Bash:
fastboot flash recovery twrp.img
Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
But he reboot always on the fastboot mode when I push simultaneously on power and volume + and when I don't push on any button.
I use these file :
twrp.img
vbmeta.img
Thanks for your help .

TWRP by brigudav- i flashed only twrp renamed to recovery.img and patched os via that stock recovery will not back.

Rename the file change nothing to me.
As information, when I try in try
Bash:
fastboot boot recovery.img
i get :
Bash:
FAILED (remote: unknown command)
in fastboot
and
Bash:
FAILED (remote: Unrecognized command boot)
in fastbootd
I've test lineage recovery and that's the same : impossible to boot on other recovery except the stock MI-Recovery 3.0 .

I get the exactly same errorwhile try booting twrp.img is there no custom recovery for lime that works?

GrandTouque said:
Hello,
After unlock his bootloader, I try to install TWRP recovery on my smartphone with :
Bash:
fastboot flash recovery twrp.img
Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
But he reboot always on the fastboot mode when I push simultaneously on power and volume + and when I don't push on any button.
I use these file :
twrp.img
vbmeta.img
Thanks for your help .
Click to expand...
Click to collapse
The twrp image is just for another device, for davinci and not for lime. But i got the same problem with correct twrp image

ex-it said:
The twrp image is just for another device, for davinci and not for lime. But i got the same problem with correct twrp image
Click to expand...
Click to collapse
You are right, I try to flash a unofficial TWRP that I found at this thread and now I've just a black screen when I boot on it but I can now boot on the OS with this "recovery".

Finally, I've found this one on this thread who works .

How To Guide Method to get Stock realme UI dialer and contact apk by changing firmware from India To philipines in Realme 8 Pro Device.

Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Don't Lock your device bootloader.
1.) First of all you need
laptop,
Usb data cable,
Minimal adb & fastboot setup,
firmware.
MCT ofp extractor tool.
and Your device.
Download below files.
Firmware link:
https://rms01.realme.net/sw/RMX3081export_11_C.19_2022072820470000.zip
MCT OFP extractor tool:
https://drive.google.com/file/d/1-MgGdT9fxi2LtJ1DIOxLVSM67thj9EpG/view?usp=drivesdk
Minimal adb & fastboot setup:
https://ava4.androidfilehost.com/dl/OqBAMk5-7QCuTzL-IhX9ZA/1661345244/10763459528675595887/ADB+&+FASTBOOT.rar
2.) Extract the ofp file package by mct ofp extract tool.
3.) Request to unlock your device bootloader by in-deapth test apk, once approved then you can start deep testing and unlock bootloader.
4.) connect your device with laptop.
5.) Open minimal adb & fastboot terminal.
and flash this images files by below cmd.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash metadata metadata.img
fastboot flash opporeserve2 opporeserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
Note: Flash this only 3 super images
fastboot flash super super.0.c5548a43.img
fastboot flash super super.1.bbada0de.img
fastboot flash super super.2.1400563f.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash userdata userdata.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot reboot
Your device will reboot to system.