Hi,
I downloaded the latest firmware miui8 from miui .com for my Redmi 2 prime to update because VOLTE was not enable.
After flashing using this command , it doesn't power on .
I use this command
Code:
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 system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
It doesn't detect on device manager , no recovery mode, no fastboot mode.
Completely dead, No led while charging also.
Help!
Here's the file that i use
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try this.. http://en.miui.com/thread-382180-1-1.html
Thanks i have done it after sorting the two test points and it detect as Qualcomm.
Does this thing will happen in miui 8 lollipop firmware or only in kitkat firmwire
Broo Why u try tiz method...!! Mi flash Tool is easy method so If u r flashing redmi2 flashing tiz method.. Dont try othr methods ??
While Downgrading i bricked my redmi 2 1gb.... No response...screen dead ...but i removed the battery and pressed volume down and power button and it just vibrated then i connected to pc( thank god it was showing device id in cmd) just fresh flashed everything and it restarted and my phone was back to live.. I hope ur device gets to fastboot mode.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I finally managed to install this goddamn lollipop. I had a custom recovery and I could not find the stock version. Finally I found it here (http://forum.xda-developers.com/showthread.php?p=54872143#post54872143).
So, fastboot everything!
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
This is my OTA copied from /cache.
Name: Blur_Version.210.12.40.falcon_umts.O2SL.en.GB
SHA-1: 2d7cd57a59986f80c185fc6ab87b848e773f9ca0
Mega link: https://mega.co.nz/#!EsYFTIqL!0pBkt3m61QH2QhHzZWYe4JJDo5RXqclMegQmb4GD_Mk
Enjoy
iBART said:
edit. I'm an idiot. I copied the wrong file (Version.210.12.40). Please delete this post -.-
Click to expand...
Click to collapse
The file name of an OTA update matches the currently installed firmware. So it's probably the right file
It's the right file !!!!!!!!!!! just upload it ! I will make a mirror for google drive.
Ok. Uploading it again...
k-kuchen said:
The file name of an OTA update matches the currently installed firmware. So it's probably the right file
Click to expand...
Click to collapse
Eurofighter_ty said:
It's the right file !!!!!!!!!!! just upload it ! I will make a mirror for google drive.
Click to expand...
Click to collapse
I don't understand. I tried to update and it says "Installation aborted" due to fingerprint... it says i have the 4.3 but i have 4.4.4 installed
I think it is because i'm trying to update my phone using a custom recovery and i need the stock one.
No way. I suck. Sorry ^_^
You need to flash stock recovery from the development section.
By the way, I take it that it isn't retail but o2 filmware?
ignore this.
eemgee said:
You need to flash stock recovery from the development section.
By the way, I take it that it isn't retail but o2 filmware?
Click to expand...
Click to collapse
O2 ... inside develop section the link of stock firmawares is 404.
cra1g321 said:
Available here - http://forum.xda-developers.com/moto-g/general/xt1032-ota-5-0-2-en-gb-captured-t3050342/post59324115
Click to expand...
Click to collapse
Not really. You captured the Retail version!
iBART said:
Not really. You captured the Retail version!
Click to expand...
Click to collapse
oops my bad, thought they were the same .
Ok. Uploaded. Have fun.
hi everyone, sorry for the google translator
by a test point, I managed to phone has connectivity to the notebook.
when start phone in Download Mode, appears fastboot
[490] FASTBOOT MODE STARTED
[570] UDC_START()
[610] ---PORTCHANGE----
[620] ---RESET---
[630] ---PORTCHANGE---
[690] FASTBOOT: PROCESSING COMMANDS
with adb commands always comes failure
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot boot.bin
fastboot flash aboot aboot.bin
fastboot flash recovery recovery.bin
fastboot flash laf laf.bin
fastboot reboot
message phone
[548290] error 4: failure sending erase group start command to the card (RCA:2)
notebook
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please , I need your help
thanks
Cristian
Maybe this tool will help u to fix ur problem.
http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
[490] FASTBOOT MODE STARTED
[570] UDC_START()
[610] ---PORTCHANGE----
[620] ---RESET---
[630] ---PORTCHANGE---
Click to expand...
Click to collapse
this looks like u will enter the Recovery mode with PowerButton -Volume, but with no recovery u end in fastboot.
U tried PowerButton +Volume? (DownloadMode)
u got the correct LG Driver on ur PC? http://oceanhost.eu/ed0bnrnghgef/LGUnitedMobileDriver_S51MAN312AP22_ML_WHQL_Ver_3.12.3.exe.htm
After i got a real brick (bootloader crash) with my D802 i fixed it like this:
1. LG G2 Stock Firmware (Go Back to Stock)
- follow the kdz instruction
- Important, get the LG Driver new for ur PC!
http://forum.xda-developers.com/showthread.php?t=2432476
2.[TOOLS] One Click ROOT+TWRP Recovery for Lollipop Stock Firmware
- read and follow and u will have root+TWRP Recovery bumped after that
http://forum.xda-developers.com/lg-...ols-how-to-install-twrp-bump-d80230a-t3072186
3. get the JB Bootloader for D802
- install via recovery
https://www.androidfilehost.com/?fid=95916177934533199
- reboot ur phone, get Custom Rom (D802) u want on ur SD and install via Recovery (Wipe Cache etc.)
looks like ur Bootloader is wrong/crashed and/or u dont got correct DRIVER (Fingerprint)
hi BFruchtfliege, thanks for your help.
- Drivers is OK
- when press POWER +VOLUME UP = enter fastboot
[490] FASTBOOT MODE STARTED
[570] UDC_START()
- LG FLASHTOOL
-TOT METHOD impossible, only this driver found in device manager
- One Click ROOT+TWRP Recovery for Lollipop Stock Firmware
- FASTBOOT JB-D802-BOOT-LOADER.zip
That looks really crazy with the "??????" thats not normal, What DesktopSystem u use?
If u cant handle point 1. from me u dont need 2. and 3. because u need point 1. ready.
Look in Forum for "brick D802" or like that.
U will find much, may there are other methods, that will help u and i dont know!
But i think, Driver isnt okay... or u got branded mobile... or u got no D802... or ur PC-OS occurs the prob.
Hope u can handle ur Phone. :fingers-crossed:
My english is pig bad, i think i spider
ls 980 bricked . fastboot only but not able to write command
hi everyone,
by a test point, I managed to phone has connectivity to the pc
when start phone in Download Mode, appears fastboot
[490] FASTBOOT MODE STARTED
[570] UDC_START()
[610] ---PORTCHANGE----
[620] ---RESET---
[630] ---PORTCHANGE---
[690] FASTBOOT: PROCESSING COMMANDS
with adb commands always comes failure
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot boot.bin
fastboot flash aboot aboot.bin
fastboot flash recovery recovery.bin
fastboot flash laf laf.bin
fastboot reboot
message phone
[548290] error 4: failure sending erase group start command to the card (RCA:2)
Also find error 2
Hi
I installed latest 20s for lepro 3 x727 and i want to install cm.
The problem is that i cannot unlock the bootloader
It said remote unlock failed.
Maybe this update came with a security patch for stop unlock bootloaders.
chemicalboyxda said:
Hi
I installed latest 20s for lepro 3 x727 and i want to install cm.
The problem is that i cannot unlock the bootloader
It said remote unlock failed.
Maybe this update came with a security patch for stop unlock bootloaders.
Click to expand...
Click to collapse
Go to the persistent bootloader unlock thread, download the bootloader files, unzip and run these commands
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
Then reboot and do the bootloader unlock command.
I've been searching for an answer to this to avoid a new thread but I will ask here. Can you confirm that taking the 20s OTA after being on stock 19s that the same unlock methods and files do still work? Thanks in advance!
I did an ota update fully stock no root.
I can confirm that unlocking the method works multiple ways:
1: LeEco aio toolkit latest version
2: Both methods in the thread of persistant bootloader unlock 19's
suhridkhan said:
Go to the persistent bootloader unlock thread, download the bootloader files, unzip and run these commands
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
Then reboot and do the bootloader unlock command.
Click to expand...
Click to collapse
That worked!!! Thanks man
xerythul said:
I've been searching for an answer to this to avoid a new thread but I will ask here. Can you confirm that taking the 20s OTA after being on stock 19s that the same unlock methods and files do still work? Thanks in advance!
Click to expand...
Click to collapse
yes...
suhridkhan said:
Go to the persistent bootloader unlock thread, download the bootloader files, unzip and run these commands
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
Then reboot and do the bootloader unlock command.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
. I can't get to flash the elf file
Sent from my SM-P600 using XDA-Developers Legacy app
how check which bootloader i have?
have new phone out of box with rom from 2016
So I'm trying to root my huawei p9 lite vns-l31 but had no luck
I did ulock bootloader and i do get the message when i reboot
but why i try to boot into the twrp from fastboot i get FAILED (remote: Command not allowed)
also the thing when you press the power button and vol up it will jsut reboot it
I tried many TWRP files none woked also I have android 7.0 and emui 5.0
P.S. sorry for bad english
Unlock bootloader again with ADB command:
"Fastboot oem unlock YOUR_CODE"
Reboot and flash a good version of TWRP for you.
Done!
Therand said:
Unlock bootloader again with ADB command:
"Fastboot oem unlock YOUR_CODE"
Reboot and flash a good version of TWRP for you.
Done!
Click to expand...
Click to collapse
Not working for me aswell
chakalovski2 said:
Not working for me aswell
Click to expand...
Click to collapse
What's not work?
ADB command?
Or fastboot?
What's return of command?
Error text?
What did you make on your phone?
How do you want help without explaining your problem?..
Hello,
When I try to send a command as flashing through fastboot it's telling me command not allowed it's kind of impossible to write or send data like a flash to my phone. Though the drivers are installed and adb too.
help me pls Command Not Allowed
I have bootloader code but when I write the command fastboot oem unlock ******* I get the command not allowed error 210 stock rom is not loaded with the three key method I want to install a twrp in vendor, system, product invalid argument error how to fixed pls help me (sorry my bad english) i can not open the oem lock because i do not know how to use the usb debug mode
Elite Rom 5.1 (Hassan Mirza) came to me after I uploaded it and I could not fix it again
TEL: P9 LİTE VNS-L31
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help me
did you fixed that error
Failed (Remote: Command not allowed)
If yes How?
Because i am also in same problem...:crying::crying::crying:
Revert to stock OS, then go to Developer settings and enable OEM unlock.
Then repeat hte process.
How can I get the stock OS without TWRP? I tryed dload method, but theres is allways a problem when eRecovery tries to install the update.zip... Idon't know what to do.. My bluetooth is not working, that my problem
Hi ,as the tiltle said,every time that i reboot mi cellphone It eraise the efs partition (IMEI and base band), i have to restore it vía TWRP and works normally ,but when i reboot It gets eraised ,is It posible to repair ? I have root with magisk.(last versión 16) and android 8 oreo instaled(january)
hi , alemarprieto .
i did not teach you the whole steps as reported by others users .
you need to flash back to 7.8.23 and restore your qcn ,
before that , you need to erase whole partition to flush out the corrupted EPS .
use this file to erase and flash ( copy the flash_factory.bat into the 7.8.23 directory /folder)
NOTE : THIS FILE ONLY FOR THOSE WHO HAVE EFS PROBLEM
https://drive.google.com/open?id=1FbXlc56R4UHE2wiT4F1nTgr-QmR5jpjj
after that :
you have to use twrp backup :
advance > Terminal
type :
dd if=/dev/block/mmcblk0p14 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p15 of=/sdcard/modemst2.img
after that , move the modemst1 and 2 img to your desktop and flash into your phone via fastboot
fastboot flash modemst1.img
fastboot flash modemst2img
you may update to latest oreo .
feedback .
@JoKeRLeE
When I flash in fastboot, this appears:
cannot determine image filename for 'modemst1.img'
You have to type fastboot flash modemst1 (drag the modemst1.IMG to cmd then flash it ....
JoKeRLeE said:
You have to type fastboot flash modemst1 (drag the modemst1.IMG to cmd then flash it ....
Click to expand...
Click to collapse
Can you explain me better? I've tried everything and it does not work, please help me.
danswat said:
Can you explain me better? I've tried everything and it does not work, please help me.
Click to expand...
Click to collapse
Maybe you can dm me and don't spam the thread
JoKeRLeE said:
You have to type fastboot flash modemst1 (drag the modemst1.IMG to cmd then flash it ....
Click to expand...
Click to collapse
My cell phone is in fastboot mode.
The modemst1 and modemst2 files are in the cmd folder.
But when I'm going to flash, he gives this error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
danswat said:
My cell phone is in fastboot mode.
The modemst1 and modemst2 files are in the cmd folder.
But when I'm going to flash, he gives this error.
Click to expand...
Click to collapse
You are missing partition name in the command.
Code:
fastboot flash modemst1 modemst1.img
Permanent Repair IMEI Oreo
I downgrade to 7.8.23 build and bootloader unlock
1.Enter fastboot mode.
2.Type fastboot command (fastboot format modemst1 and fastboot format modemst2) and reboot.
3.Repair IMEI through RBSoft_V1.5 crack version and QPST Configuration Tool.,IMEI and baseband corrected.
Mobile signal back,All back to normal phone.
4.After complete above steps,enter into fastboot
and boot into twrp 3.1.1 moded.
5.In Twrp,Backup section-> Backup efs only and reboot.
6.Again Boot into fastboot and type command (fastboot format modemst1 and fastboot format modemst2) and reboot.
7. Boot into twrp 3.1.1 moded version and enter restore section.
8.Restore your previous backuped efs and reboot.
9.Download Mi a1 Oreo January fastboot ROM and flash with Clean All mode.
10.Boom,you have ur original IMEI and not fail on every reboot.You can apply magisk and what ever u want.
THAT MY ANSWER FOR IMEI FAIL ON EVRY REBOOT.
ASK ur problem.
Report ur condition.
Recommended To this post.Do all step in this post and apply my above steps->https://forum.xda-developers.com/mi-a1/help/repair-imei-mi-a1-links-updated-t3756891