Fix for Lenovo A6000/plus stuck on booting Logo - Lenovo A6000/Plus Guides, News, & Discussion

{
"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"
}
Power off the phone .
Press vol down and power button and it will boot into boot loader
Connect the USB cable .
Go to ed300's post and download the twrp recovery for lollipop and KitKat.
If the base ROM on which u have flashed the new ROM was KitKat use the KitKat twrp.
Else use the lollipop twrp.
Extract the required zip file.
After connecting the USB , click on the file named Flash . after its completed click on Boot file .after that's also done again click the Flash file .
After that it will show (waiting for device )
And the phone will boot to the recovery mode and u can flash the ED300's ROM I prefer CM12.1
Good luck.

bro Iam getting waiting for device now itself but Iam not able to move any furthur after that . It is just showing "waiting for device "

bvsbrk said:
bro Iam getting waiting for device now itself but Iam not able to move any furthur after that . It is just showing "waiting for device "
Click to expand...
Click to collapse
Did u follow as I mentioned?
Which was the base rom on which u flashed CM

Its lollipop and I followed steps exactly as you mentioned . I replaced the recovery of adb and fastboot folder with the recovery you suggested . But the thing is fastboot driver which was gone after flashing cm.

bvsbrk said:
Its lollipop and I followed steps exactly as you mentioned . I replaced the recovery of adb and fastboot folder with the recovery you suggested . But the thing is fastboot driver which was gone after flashing cm.
Click to expand...
Click to collapse
Replaced? I didn't get that.
Just download this https://userscloud.com/a25aszfwkn2z
Put the phone to fastboot by pressing vol down and power .
Connect the USB to phone . Unzip the file mentioned above. Open the file.
Double click on flash.bat then after that's done , boot.dat after that's also done then flash.bat and ur phone will boot to recovery.

aravindmj said:
Replaced? I didn't get that.
Just download this https://userscloud.com/a25aszfwkn2z
Put the phone to fastboot by pressing vol down and power .
Connect the USB to phone . Unzip the file mentioned above. Open the file.
Double click on flash.bat then after that's done , boot.dat after that's also done then flash.bat and ur phone will boot to recovery.
Click to expand...
Click to collapse
The link is downloading a file which is invalid. I cant open the zip file that you asked to download from the zip file . Pls send some other link

bvsbrk said:
The link is downloading a file which is invalid. I cant open the zip file that you asked to download from the zip file . Pls send some other link
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk

aravindmj said:
https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk
Click to expand...
Click to collapse
that is not working every command window stopped at "waiting for device" anyway thanks a lot

bvsbrk said:
that is not working every command window stopped at "waiting for device" anyway thanks a lot
Click to expand...
Click to collapse
Try this https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk

aravindmj said:
Try this https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk
Click to expand...
Click to collapse
This I had tried already as you posted it before. Some one said my device data is completely lost while I flashed cm.

bvsbrk said:
This I had tried already as you posted it before. Some one said my device data is completely lost while I flashed cm.
Click to expand...
Click to collapse
Sorry the link was wrong try this it's a different one https://drive.google.com/file/d/0B3yAzE4FH2e7RU5helVWd0dBUGM/view?usp=drivesdk
App data excluding what's app will be lost but the data in the internal storage will.be present.

aravindmj said:
Sorry the link was wrong try this it's a different one https://drive.google.com/file/d/0B3yAzE4FH2e7RU5helVWd0dBUGM/view?usp=drivesdk
App data excluding what's app will be lost but the data in the internal storage will.be present.
Click to expand...
Click to collapse
Same thing bro the problem is something related to fastboot drivers which were gone from my phone

It worked for me . Can you send me a link where i can find CM12.1

Mahesh0001 said:
It worked for me . Can you send me a link where i can find CM12.1
Click to expand...
Click to collapse
https://forum.xda-developers.com/le...t-cm12-1-rom-lenovo-a6000-plus-withe-t3288805

My phone went into bootloop , i was using ResurrectionRemix 5.8.3 , i cant go into recovery mode. but can start bootloader.
I have installed Minimal fastboot , its showing no devices found when used "adb devices"
But shows the devices for command "fastboot devices"
I also tried flashing twrp.img using "fastboot flash recovery twrp.img"
But still phone not starting just stuck on looping the startup..Please helpppp

i get error when i hit flash.bat that device not found but it write the img file
What should i do?

My Lenovo A6000 Kitkat 4.4 struck on logo after phone switched off after hang. Phone when switched lenovo logo comes with display down saying press power button long for fastboot but does not enter fastboot. Whenever i press power button it says the same press power button long for fastboot but does not enter fastboot. nothing works I guess the OS crashed tried to enter into boot menu using volume +- powerbutton nothing works tried different combination nothing works.
i have downloaded kitkat 4.4 stock ROM but dont know how to flash and install using pc. If anyone knows how then let me know.

johnwell4u said:
My Lenovo A6000 Kitkat 4.4 struck on logo after phone switched off after hang. Phone when switched lenovo logo comes with display down saying press power button long for fastboot but does not enter fastboot. Whenever i press power button it says the same press power button long for fastboot but does not enter fastboot. nothing works I guess the OS crashed tried to enter into boot menu using volume +- powerbutton nothing works tried different combination nothing works.
i have downloaded kitkat 4.4 stock ROM but dont know how to flash and install using pc. If anyone knows how then let me know.
Click to expand...
Click to collapse
Flashing via phone is easy.
Just go to recovery wipe entire thing and then flash.

Mahesh0001 said:
i get error when i hit flash.bat that device not found but it write the img file
What should i do?
Click to expand...
Click to collapse
Make sure to use the recovery based on the rom that you where on before this thing happened.
And try executing the boot.bat file also. Do it simultaneously

aravindmj said:
Replaced? I didn't get that.
Just download this https://userscloud.com/a25aszfwkn2z
Put the phone to fastboot by pressing vol down and power .
Connect the USB to phone . Unzip the file mentioned above. Open the file.
Double click on flash.bat then after that's done , boot.dat after that's also done then flash.bat and ur phone will boot to recovery.
Click to expand...
Click to collapse
worked for me to open recovery again.. i am now trying to reflash MIUI8 android 5.1.1.:good::good::good:

Related

[GUIDE][SOLVE]Hard-Brick lenovo a6000/+

HELLO FRIENDS...
Many friend have face this problems i.e no recovery,no splash screen,no system only just a small vibration this is know as Hard-Brick..
This method will 100% works for both Lenovo a6000 and plus...
for this we need the following things....
Firmware-File
QPST Tool
and well working computer or Laptop..
Thing want to know before starting...
We will not use QPST tool for flashing this is optional. After installing QPST tool the error face by most computer will be fixed error like MSVCP100.dll error mostly this problem is face by 64bit OS..If you have installed 64bit try it if it's works then good if not then use your friend's PC which have 32bit OS or install 32bit OS
We will use flash tool which already given in Firmware zip.
Let's Start...:laugh:
After downloading the firmware You'll get firmware folder and Qualcomm Flash Tool and most important drivers folder there will be more files but no use of those file.
STEP 1.First extract this above 3 file in a folder where you want...then click on driver folder and then click on Qualcomm_USB_Driver_Setup.exe......setup will start...select the first option(WWWAN.DHCP........) and then next...further you can do.. while installation if a pop-up comes click on yes(all ways click on yes) after completion of driver installation please reboot or restart you are pc or laptop ..:good:
STEP 2...click on Qualcomm Flash Tool->QcomDLoader.exe if it start then good....and if there is an error like MSVCP100.dll not found or something else
then install QPST tool and run it. After opening it now close it.....Now again click on QcomDLoader.exe this time it will work:good:
then click on Load button(the first icon of the tool) then browse the firmware folder where u have extracted...then click on start(the 3 icon of the flash tool)
STEP 3:..Now remove Your sim card and memory card(if u don't have this then also remove your battery and then put it again)...
Now hold volume+ and volume - button(do not touch power button) and plug in vie usb... the flash will automatically start....
wait till it complete...after finish it will show finish in green color...then unplug the phone and hold power button to start...
This method is same for Lenovo a6000 plus the only different will be....it will show 1GB ram and 8GB internal storage
To fix this install any custom rom..,:good:
This method is tasted by me and it work for me I have Lenovo a6000 plus that's why I am sharing this with you all....
NOTE:-after coming back to KitKat you may face the problem of boot loop for 7.x.x rom or some feature of the rom may not work..to overcome this problem follow this
download this twrp KitKat version(not so important) you can use cwm(not tested) and direct flash the lollipop rom which contain system.img file in it eg. vibe 2.5(tested and works) ,color os 3.1 or any rom which contain system.img and reboot.:good:
do not use any pach file for upgrading to lollipop do direct flash lollipop rom.
I hope this will also work for you...
if this post help's you plz donate me on paytm...no 9763697739
if any problem occurs then please let me know..
Screen Short
This is my phone info after flashing it.....
this is not Lenovo a6000 this SS in of Lenovo a6000 plus
{
"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"
}
This after flashing custom Rom
soan0 said:
HELLO FRIENDS...
Many friend have face this problems i.e no recovery,no splash screen,no system only just a small vibration this is know as Hard-Brick..
This method will 100% works for both Lenovo a6000 and plus...
for this we need the following things....
Firmware-File(this is stock rom is for Lenovo a6000 but can be use for Lenovo a6000+)
QPST Tool
and well working computer or Laptop..
Thing want to know before starting...
We will not use QPST tool for flashing this is optional. After installing QPST tool the error face by most computer will be fixed error like MSVCP100.dll error mostly this problem is face by 64bit OS..If you have installed 64bit try it if it's works then good if not then use your friend's PC which have 32bit OS or install 32bit OS
We will use flash tool which already given in Firmware zip.
Let's Start...:laugh:
After downloading the firmware You'll get firmware folder and Qualcomm Flash Tool and most important drivers folder there will be more files but no use of those file.
STEP 1.First extract this above 3 file in a folder where you want...then click on driver folder and then click on Qualcomm_USB_Driver_Setup.exe......setup will start...select the first option(WWWAN.DHCP........) and then next...further you can do.. while installation if a pop-up comes click on yes(all ways click on yes) after completion of driver installation please reboot or restart you are pc or laptop ..:good:
STEP 2...click on Qualcomm Flash Tool->QcomDLoader.exe if it start then good....and if there is an error like MSVCP100.dll not found or something else
then install QPST tool and run it. After opening it now close it.....Now again click on QcomDLoader.exe this time it will work:good:
then click on Load button(the first icon of the tool) then browse the firmware folder where u have extracted...then click on start(the 3 icon of the flash tool)
STEP 3:..Now remove Your sim card and memory card(if u don't have this then also remove your battery and then put it again)...
Now hold volume+ and volume - button(do not touch power button) and plug in vie usb... the flash will automatically start....
wait till it complete...after finish it will show finish in green color...then unplug the phone and hold power button to start...
This method is same for Lenovo a6000 plus the only different will be....it will show 1GB ram and 8GB internal storage
To fix this install any custom rom..,:good:
This method is tasted by me and it work for me I have Lenovo a6000 plus that's why I am sharing this with you all....
I hope this will also work for you...
if any problem occurs then please let me know..
Click to expand...
Click to collapse
For some people who dont get their phones detected need to open their motherboard and short the two points located beside memory card slot
The Hard Gamer said:
For some people who dont get their phones detected need to open their motherboard and short the two points located beside memory card slot
Click to expand...
Click to collapse
It can be told better with an image, if you can manage :-B
sasukay said:
It can be told better with an image, if you can manage :-B
Click to expand...
Click to collapse
Ok i wil try to find it
nice method thank you for sharing this will help many peoples....
MR.HACKER5476 said:
nice method thank you for sharing this will help many peoples....
Click to expand...
Click to collapse
yes bro i know how it feel when phone get brick...
The phone boots shows logo restarting and it keeps on restarting
chriselanko said:
The phone boots shows logo restarting and it keeps on restarting
Click to expand...
Click to collapse
install any custom rom or do factor reset
if you have done this above but still have the problem then answer my question
u r currently instead rom android version ?
is custom recovery is flashed?
do u have used any patch zip to upgrade or downgrade the android version ?
soan0 said:
install any custom rom or do factor reset
if you have done this above but still have the problem then answer my question
u r currently instead rom android version ?
is custom recovery is flashed?
do u have used any patch zip to upgrade or downgrade the android version ?
Click to expand...
Click to collapse
I am not able to acess recovery mode.
can enter fastboot but not recovery.
I have also attached the screenshot of final status while flashing.
I followed all steps .
bro its taking too much time what to do its tooked about 11 min and still okeep going
soan0 said:
HELLO FRIENDS...
Many friend have face this problems i.e no recovery,no splash screen,no system only just a small vibration this is know as Hard-Brick..
This method will 100% works for both Lenovo a6000 and plus...
for this we need the following things....
Firmware-File(this is stock rom is for Lenovo a6000 but can be use for Lenovo a6000+)
QPST Tool
and well working computer or Laptop..
Thing want to know before starting...
We will not use QPST tool for flashing this is optional. After installing QPST tool the error face by most computer will be fixed error like MSVCP100.dll error mostly this problem is face by 64bit OS..If you have installed 64bit try it if it's works then good if not then use your friend's PC which have 32bit OS or install 32bit OS
We will use flash tool which already given in Firmware zip.
Let's Start...:laugh:
After downloading the firmware You'll get firmware folder and Qualcomm Flash Tool and most important drivers folder there will be more files but no use of those file.
STEP 1.First extract this above 3 file in a folder where you want...then click on driver folder and then click on Qualcomm_USB_Driver_Setup.exe......setup will start...select the first option(WWWAN.DHCP........) and then next...further you can do.. while installation if a pop-up comes click on yes(all ways click on yes) after completion of driver installation please reboot or restart you are pc or laptop ..:good:
STEP 2...click on Qualcomm Flash Tool->QcomDLoader.exe if it start then good....and if there is an error like MSVCP100.dll not found or something else
then install QPST tool and run it. After opening it now close it.....Now again click on QcomDLoader.exe this time it will work:good:
then click on Load button(the first icon of the tool) then browse the firmware folder where u have extracted...then click on start(the 3 icon of the flash tool)
STEP 3:..Now remove Your sim card and memory card(if u don't have this then also remove your battery and then put it again)...
Now hold volume+ and volume - button(do not touch power button) and plug in vie usb... the flash will automatically start....
wait till it complete...after finish it will show finish in green color...then unplug the phone and hold power button to start...
This method is same for Lenovo a6000 plus the only different will be....it will show 1GB ram and 8GB internal storage
To fix this install any custom rom..,:good:
This method is tasted by me and it work for me I have Lenovo a6000 plus that's why I am sharing this with you all....
NOTE:-after coming back to KitKat you may face the problem of boot loop for 7.x.x rom or some feature of the rom may not work..to overcome this problem follow this
download this twrp KitKat version(not so important) you can use cwm(not tested) and direct flash the lollipop rom which contain system.img file in it eg. vibe 2.5(tested and works) ,color os 3.1 or any rom which contain system.img and reboot.:good:
do not use any pach file for upgrading to lollipop do direct flash lollipop rom.
I hope this will also work for you...
if any problem occurs then please let me know..
Click to expand...
Click to collapse
its taking too much time and keep going what to doo
shivanshusuraj said:
its taking too much time and keep going what to doo
Click to expand...
Click to collapse
which buttons u have pressed at the start
bro turn off u r phone then remove u r sim and memory card (not necessary) then press and hold volume + and volume - (don't touch power button )together till u feel a soft vibration then only connect to u r pc
yes i remover all things no sim no memory and i hode both volume key then plug usb
soan0 said:
which buttons u have pressed at the start
bro turn off u r phone then remove u r sim and memory card (not necessary) then press and hold volume + and volume - (don't touch power button )together till u feel a soft vibration then only connect to u r pc
Click to expand...
Click to collapse
yes i remover all things no sim no memory and i hode both volume key then plug usb and then it vibrate and connected but its took 23 min but not done then i remover usb directly
chriselanko said:
I am not able to acess recovery mode.
can enter fastboot but not recovery.
I have also attached the screenshot of final status while flashing.
I followed all steps .
Click to expand...
Click to collapse
bro now u can flash custom recovery i.e TWRP,CWM as par u r android version
i think u know that how to do ..if not then plz check how to flash twrp or cwm in Lenovo a6000
shivanshusuraj said:
yes i remover all things no sim no memory and i hode both volume key then plug usb and then it vibrate and connected but its took 23 min but not done then i remover usb directly
Click to expand...
Click to collapse
u r drivers are install properly plz check which phone do u have
if u have serious problem then whatsapp me 9763697739
shivanshusuraj said:
yes i remover all things no sim no memory and i hode both volume key then plug usb and then it vibrate and connected but its took 23 min but not done then i remover usb directly
Click to expand...
Click to collapse
if it possible to format u r pc then do it and again do all the step if not then try this hole guide in u r friend pc
Still Bootlooping / no recovery
soan0 said:
bro now u can flash custom recovery i.e TWRP,CWM as par u r android version
i think u know that how to do ..if not then plz check how to flash twrp or cwm in Lenovo a6000
Click to expand...
Click to collapse
1) Flashed Sucessfully the given frimware using the tool in the folder.
2) Phone still in boot loop.
3) Tried to flash Twrp image you mentioned in this thread, it flashed sucessfully but cannot able to acess recovery by hardware button combinations or by any means.
4)Tried Flashing Vibe 2.5 Lollipop ROM using fastboot ( using command fastboot update E:\vibe.zip ). It showing errors like
" archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
"
5) Please help me with this and tell me where was I wrong. Am not a PRO, just a beginner So please give detailed instructions if am wrong. Thank you @soan0
chriselanko said:
1) Flashed Sucessfully the given frimware using the tool in the folder.
2) Phone still in boot loop.
3) Tried to flash Twrp image you mentioned in this thread, it flashed sucessfully but cannot able to acess recovery by hardware button combinations or by any means.
4)Tried Flashing Vibe 2.5 Lollipop ROM using fastboot ( using command fastboot update E:\vibe.zip ). It showing errors like
" archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
"
5) Please help me with this and tell me where was I wrong. Am not a PRO, just a beginner So please give detailed instructions if am wrong. Thank you @soan0
Click to expand...
Click to collapse
Bro after flashing wait for few min it take time to boot up
And try to flash vibeui 2.5 by twrp which i have given the link if still have a problem then whatsapp me or call so that i can understand u r problem correctly
9763697739
soan0 said:
Bro after flashing wait for few min it take time to boot up
And try to flash vibeui 2.5 by twrp which i have given the link if still have a problem then whatsapp me or call so that i can understand u r problem correctly
9763697739
Click to expand...
Click to collapse
After flashing , i just power on the device and left it. it just keeps on restarting. (ie what i mentioned as boot loop).
I cannot acess TWRP then how can i flash vibe 2.5 using it.
Sry I didnt get you, I send the video of the phone in your whatsapp number.
even using " fastboot boot twrp.img" command it is showing sucessful in cmd promt but while device keeps restarting
chriselanko said:
I am not able to acess recovery mode.
can enter fastboot but not recovery.
I have also attached the screenshot of final status while flashing.
I followed all steps .
Click to expand...
Click to collapse
If you can't enter recovery your simplest method would be flashing recovery through fastboot mode..

Bootloop on Redmi note 3 SE kate

Hello, I have a redmi note 3 SE (Kate) and its stock.
A few days ago the device randomly restarted and its bootlooping, instead of the recovery mode the device its showing me a picture of the phone and a usb cable. I can only access fastboot mode, what (and how) can I do something about it?
Thank you in advance
Teo128 said:
Hello, I have a redmi note 3 SE (Kate) and its stock.
A few days ago the device randomly restarted and its bootlooping, instead of the recovery mode the device its showing me a picture of the phone and a usb cable. I can only access fastboot mode, what (and how) can I do something about it?
Thank you in advance
Click to expand...
Click to collapse
If u cant boot into miui. Then u need to factory reset in recovery.
Hold power + vol up
and release as soon when mi logo vibrates.u will be in recovery mode.
Choose wipe data and cache. Reboot.
naik2902 said:
If u cant boot into miui. Then u need to factory reset in recovery.
Hold power + vol up
and release as soon when mi logo vibrates.u will be in recovery mode.
Choose wipe data and cache. Reboot.
Click to expand...
Click to collapse
Recovery mode doesn't work, it shows this
{
"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"
}
Teo128 said:
Recovery mode doesn't
work, it shows this
Click to expand...
Click to collapse
If u cant boot into miui then download mi pc suite on computer and install.
Connnect phone to pc in same recovery mode shown by your picture.
And connect internet and download rom and flash. If there is option to factory reset then u use it.
Or
Download fastboot tgz rom .
Put ur device in edl mode.
And flash using miflash tool
Select clean flash all option during flash
Thanks
On windows 10
I downloaded the PC suite and installed the redmi note 3 windows drivers, the computer detect it correctly as "Redmi note 3" and the phone display the USB cable as conneted but the MI pc suite doesn't detect the device :crying:
Teo128 said:
Thanks
On windows 10
I downloaded the PC suite and installed the redmi note 3 windows drivers, the computer detect it correctly as "Redmi note 3" and the phone display the USB cable as conneted but the MI pc suite doesn't detect the device :crying:
Click to expand...
Click to collapse
Use edl mode method.
Mi pc suite already has usb drivers. No need to install drivers twice.
Remove other drivers and check.
Or
Put device in fastboot mode. Vol down +power
Connect to pc
Use this fastboot command in cmd.
fastboot devices
If serial number of device appeaered then ur device is detected.
Ur device is locked. Now put device from fastboot mode to Edl mode. And flash fastboot rom using mi flash. Select " clean all" option.
How to put in edl mode. .? Follow this guide to put in edl mode.
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Download kate rom and mi flash tool. Put in edl mode and flash.
Fastboot kate rom.
http://bigota.d.miui.com/8.11.29/ka...29_20181129.0000.00_6.0_global_b29e9d8bcf.tgz
---------- Post added at 04:27 AM ---------- Previous post was at 03:32 AM ----------
Sorry i gave kenzo rom link..
Use kate rom. Link changed again.
naik2902 said:
Use edl mode method.
Mi pc suite already has usb drivers. No need to install drivers twice.
Remove other drivers and check.
Or
Put device in fastboot mode. Vol down +power
Connect to pc
Use this fastboot command in cmd.
fastboot devices
If serial number of device appeaered then ur device is detected.
Ur device is locked. Now put device from fastboot mode to Edl mode. And flash fastboot rom using mi flash. Select " clean all" option.
Click to expand...
Click to collapse
Hello and thank you for your help.
I actually installed the drivers AFTER MI PC suite failed to detect my device, at that time windows displayed it as just "android device".
Fastboot CMD show me this, it's correctly working?
I don't have time to try the EDL method today, I'll give it a try tomorrow. Will it work on a unlocked(I meant Locked) device?
Teo128 said:
Hello and thank you for your help.
I actually installed the drivers AFTER MI PC suite failed to detect my device, at that time windows displayed it as just "android device".
Fastboot CMD show me this, it's correctly working?
I don't have time to try the EDL method today, I'll give it a try tomorrow. Will it work on a unlocked device?
Click to expand...
Click to collapse
Did u unlocked officially using miunlock tool?
Check ur bootloader status. Using below.command
fastboot oem device-info
If unlocked = true .Then u dont need edl mode..u can flash it in normal fastboot mode.
Just download fastboot rom. I gave link.
Extract it to folder
Put phone in fastboot mode and connect.
Run mi flash tool
Browse and select extracted tgz main folder
Select "clean all" option
And flash.
naik2902 said:
Did u unlocked officially using miunlock tool?
Check ur bootloader status. Using below.command
fastboot oem device-info
If unlocked = true .Then u dont need edl mode..u can flash it in normal fastboot mode.
And flash.
Click to expand...
Click to collapse
The device its unlocked (I meant LOCKED), I didn't tamper with it or tried to flash something, it just bricked on its own.
I'll try your method tomorrowm hoping the problem isn't hardware related.
Teo128 said:
The device its unlocked, I didn't tamper with it or tried to flash something, it just bricked on its own.
I'll try your method tomorrowm hoping the problem isn't hardware related.
Click to expand...
Click to collapse
Wtf dude. Cant u read.
It shows Device unlocked = false
Means Ur device is locked.
U need to flash fastboot rom using edl mode.
naik2902 said:
Wtf dude. Cant u read.
It shows Device unlocked = false
Means Ur device is locked.
U need to flash fastboot rom using edl mode.
Click to expand...
Click to collapse
You are right! I'm sorry, it's my bad, I'm writing "Unlocked" instead of "Locked" so stupid. LOL
I was talking about the EDL Mode method of course, I downloaded everything, just need time to try
Thank you very much for your help
Teo128 said:
You are right! I'm sorry, it's my bad, I'm writing "Unlocked" instead of "Locked" so stupid. LOL
I was talking about the EDL Mode method of course, I downloaded everything, just need time to try
Thank you very much for your help
Click to expand...
Click to collapse
Have u ever unlocked it before? By Officially or unofficiallly?
If u unlocked it before. Then did u try to flash twrp and install custom rom?
naik2902 said:
Have u ever unlocked it before? By Officially or unofficiallly?
If u unlocked it before. Then did u try to flash twrp and install custom rom?
Click to expand...
Click to collapse
Nope, I decided to keep it stock so I didn't attempt anything. It just bricked itself...
naik2902 said:
Have u ever unlocked it before? By Officially or unofficiallly?
Click to expand...
Click to collapse
I putted the phone in EDL mode and I'm tryng to flash it with miflash tool, it gives me this error "cannot receive hello packet, miflash is tryng to reset status!" :silly:
Teo128 said:
I putted the phone in EDL mode and I'm tryng to flash it with miflash tool, it gives me this error "cannot receive hello packet, miflash is tryng to reset status!" :silly:
Click to expand...
Click to collapse
Make sure ur downloaded file is fully downloaded.
Extract tgz zip in folder fully.
Browse and Select main folder in miflash tool.
What option u using during flash ?
Use clean all
naik2902 said:
Make sure ur downloaded file is fully downloaded.
Extract tgz zip in folder fully.
Browse and Select main folder in miflash tool.
What option u using during flash ?
Use clean all
Click to expand...
Click to collapse
I did it but it's not working, the phone is in ELD mode and recognized as QDloader 9008
Teo128 said:
I did it but it's not working, the phone is in ELD mode and recognized as QDloader 9008
Click to expand...
Click to collapse
Check this thread and go through all below comments.and try what users did when they faced this problem.
https://en.miui.com/forum.php?mod=viewthread&tid=354839&extra=page=1&page=2&mobile=2
Could be Many reasons
May be admin privileges to mi flash
May be 32 bit pc u using
May be u need to move rom folder to main c directory
Or many more
Go though comments. They solved it.
naik2902 said:
Check this thread and go through all below comments.and try what users did when they faced this problem.
https://en.miui.com/forum.php?mod=viewthread&tid=354839&extra=page=1&page=2&mobile=2
Could be Many reasons
May be admin privileges to mi flash
May be 32 bit pc u using
May be u need to move rom folder to main c directory
Or many more
Go though comments. They solved it.
Click to expand...
Click to collapse
I already checked that thread...
I have both 64bit windows 7 and 10, tried to move the folder to C: and to run MIflash as administrator, I'll try to start over and download the rom again :crying:
Teo128 said:
I already checked that thread...
I have both 64bit windows 7 and 10, tried to move the folder to C: and to run MIflash as administrator, I'll try to start over and download the rom again :crying:
Click to expand...
Click to collapse
U dont need to download again.
Ur rom zip comes with file name.
Romszip Filename Starts with
kate ....global... ens with something
http://bigota.d.miui.com/8.11.29/ka...29_20181129.0000.00_6.0_global_b29e9d8bcf.tgz
The last number here...b29xxxxxcf is md5sum.
To calculate if u have downloaded file properly .
Just Check md5sum of rom zip using md5 checker.
Install any md5hash checker app from playstore on smarphone.
..Download rom zip on smartphone and check md5sum of downloaded file using the app.
Go through those comments. The link i gave u..
Google search redmi note 3 with those errors. U will find solution somewhere. U dont make use of google thats why u cry.
naik2902 said:
U dont need to download again.
Ur rom zip comes with file name.
Romszip Filename Starts with
kate ....global... ens with something
http://bigota.d.miui.com/8.11.29/ka...29_20181129.0000.00_6.0_global_b29e9d8bcf.tgz
The last number here...b29xxxxxcf is md5sum.
To calculate if u have downloaded file properly .
Just Check md5sum of rom zip using md5 checker.
Install any md5hash checker app from playstore on smarphone.
..Download rom zip on smartphone and check md5sum of downloaded file using the app.
Go through those comments. The link i gave u..
Google search redmi note 3 with those errors. U will find solution somewhere. U dont make use of google thats why u cry.
Click to expand...
Click to collapse
I actually always check google, only problem its that everyone says tons of different things :silly:
So, I started over, redownloaded the ROM (checksum perfect), downloaded the last portable version of MIflash, reinstalled the drivers, rebooted both laptop and phone, started MIflash as administrator...
AND FINALLY!
The device was succesfully unbricked! Many thanks!:good::fingers-crossed:
So, now I have android 6 and MIUI 10 (previously I had MIUI 8), should I upgrade to a better ROM?

Question Redmi Note 10 bricked

My phone is completely messed up right now. All I did was flash spark os (A12) over PPUI (A11) and then my phone didn't boot. I flashed that ROM via fastboot flash tool. I think it was the tool which caused this problem. After so many tries, my phone booted but wifi, sound and many other functions aren't working. Then I tried flashing some other ROM but TWRP/Ofox kept giving some "error 7". Then I tried flashing fastboot ROM with 3 versions of Mi flashtool but it keeps giving some kind of CRC flash error. Please help me I'm too much worried right now.
if you flash through fastboot tool do you see any error (if yes then tell us more about the error )if not and rom starts with some issues try flashing the latest firmware
muneeb rizwan said:
if you flash through fastboot tool do you see any error (if yes then tell us more about the error )if not and rom starts with some issues try flashing the latest firmware
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'm getting this error continously
move it to c:\
muneeb rizwan said:
move it to c:\
Click to expand...
Click to collapse
now my phone screen has gone black and it won't turn on. Computer still detects it as I'm hearing some sound
I was flashing fastboot ROM using mi flashtool and it gave me error. When I tried to turn on the phone, it didn't turn on. However, when I connect it to PC, the PC makes some sound. What do I do now?
boot your phone into fastboot mode and then connect it to pc and install this rom
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv12/xiaomi.eu_multi_HMNote10_V12.0.5.0.RKGMIXM_v12-11-fastboot.zip/download
extract the zip file and you will see a file (install for first time) open it and if all goes well it will flash the rom
muneeb rizwan said:
boot your phone into fastboot mode and then connect it to pc and install this rom
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv12/xiaomi.eu_multi_HMNote10_V12.0.5.0.RKGMIXM_v12-11-fastboot.zip/download
extract the zip file and you will see a file (install for first time) open it and if all goes well it will flash the rom
Click to expand...
Click to collapse
I can't even boot into fastboot mode. Screen stays black no matter what key combo I try
The following steps should put your phone into fastboot.
1) Phone off
2) Connect the USB cable to the computer (not the phone for now)
3) Hold the volume down button only
4) Still hold and connect the USB cable to the phone
Now the telefo should start fastboot mode.
StaryMuz said:
The following steps should put your phone into fastboot.
1) Phone off
2) Connect the USB cable to the computer (not the phone for now)
3) Hold the volume down button only
4) Still hold and connect the USB cable to the phone
Now the telefo should start fastboot mode.
Click to expand...
Click to collapse
Didn't work. I guess EDL mode is my last hope now.
Starting EDL mode can be a problem. At present, perhaps EDL cables no longer work and if the phone does not allow you to enter the EDL by key combinations, the only test points left are on the phone's motherboard. With test points, the question is whether the correct points have already been found. The manufacturer does not inform about them.
What driver is loaded in Windows when the phone is connected?
So the test points are already known:
It works by disconnecting the battery to completely shut down the hardware. Conductively connect the test points (tweezers, scissors) and with the points connected, connect the USB cable plugged into the PC. This activates the EDL mode (sometimes only very briefly). You need to have MiFlash running beforehand and use "refresh" and "Flash" right away. If nothing happens, probably the EDL mode has already been switched off again.
For flash in EDL mode you can normally use MiFlash with ROM for fastboot.
If the Qualcomm HS-USB QDLoader 9008 Windows driver is loaded, this is the EDL mode.
StaryMuz said:
For flash in EDL mode you can normally use MiFlash with ROM for fastboot.
If the Qualcomm HS-USB QDLoader 9008 Windows driver is loaded, this is the EDL mode.
Click to expand...
Click to collapse
I wonder how did my phone boot into edl mode although I never opened its back cover.
And right now the problem is that Mi Flashtool is showing some edl authentication error. How do I resolve that?
First, it is very important to call things by their correct name, otherwise misunderstandings and mistakes in procedure can arise. What do you mean "Mi Flahtool"?
You should have used this:
https://www.xiaomiflash.com/downloads/MiFlash20181115.zip
I think the flashtool version of 2017 works without any problem, coz, recently I unbricked my Poco x2 with this version of flashtool. The latest versions of flashtools are getting errors. And move the flash files to C: partition mandatory
StaryMuz said:
First, it is very important to call things by their correct name, otherwise misunderstandings and mistakes in procedure can arise. What do you mean "Mi Flahtool"?
You should have used this:
https://www.xiaomiflash.com/downloads/MiFlash20181115.zip
Click to expand...
Click to collapse
That's exactly what I used. I even tried the latest version but still no luck.
Shibu Shaji said:
I think the flashtool version of 2017 works without any problem, coz, recently I unbricked my Poco x2 with this version of flashtool. The latest versions of flashtools are getting errors. And move the flash files to C: partition mandatory
Click to expand...
Click to collapse
No matter which version I try, it always gives this error and asks for id and password. And when I enter that, nothing happens.
Bro, connect to a VPN , change the language of auth window and bind your mi account details there. And give it a try on tool version 2017.4.25... If nothing works go for edl.
munimjaffer said:
No matter which version I try, it always gives this error and asks for id and password. And when I enter that, nothing happens.
View attachment 5504363
Click to expand...
Click to collapse
munimjaffer said:
No matter which version I try, it always gives this error and asks for id and password. And when I enter that, nothing happens.
View attachment 5504363
Click to expand...
Click to collapse
Bro, use the same version of flash tool that I mentioned above.. 2017.4.25 with flash all command.

DID I BRICK MY P20 LITE?!

Hi everyone, I'm in need of some help ASAP. I unlocked my ANE-LX1 phone's bootloader so that I could root it, but things went wrong. My phone is stuck on TWRP logo screen (No TWRP menu, only logo) and my PC doesn't recognize it no matter what. I can only access the fastboot screen but it means nothing when you can't use ADB commands. I really don't know what to do, please help!
@-Alf- Hope that you'd help
soslusos said:
@-Alf- Hope that you'd help
Click to expand...
Click to collapse
Hi, try to explain what exactly happened, step by step.
soslusos said:
when you can't use ADB commands
Click to expand...
Click to collapse
For what reason?
-Alf- said:
Hi, try to explain what exactly happened, step by step.
For what reason?
Click to expand...
Click to collapse
Ok so I unlocked the bootloader, then I tried to root with Magisk by using adb but somehow it didn't work so I decided to install TWRP. I was on 9.1 but TWRP version was 9.0. I installed it and phone started to boot into TWRP only. PC recognized the phone but there were a bunch of folders with weird names. So I pressed on Format Data in TWRP but it didn't progress so I had to force-shut down my phone. Now PC doesn't recognize the phone at all. It's stuck on TWRP logo screen. Since my PC can't read the phone, I'm unable to use adb commands.
soslusos said:
Ok so I unlocked the bootloader, then I tried to root with Magisk by using adb but somehow it didn't work so I decided to install TWRP. I was on 9.1 but TWRP version was 9.0. I installed it and phone started to boot into TWRP only. PC recognized the phone but there were a bunch of folders with weird names. So I pressed on Format Data in TWRP but it didn't progress so I had to force-shut down my phone. Now PC doesn't recognize the phone at all. It's stuck on TWRP logo screen. Since my PC can't read the phone, I'm unable to use adb commands.
Click to expand...
Click to collapse
Format Data in incompatible TWRP? Really not good idea...
Okay, try the following:
- install on PC "Minimal ADB and fastboot" , open it, run command
fastboot devices <enter>
You'll get message 'waiting for any device'.
- Turn off the phone, hold Volume Down and connect to PC. Post the result.
What is region? (Cxxx)
-Alf- said:
Format Data in incompatible TWRP? Really not good idea...
Okay, try the following:
- install on PC "Minimal ADB and fastboot" , open it, run command
fastboot devices <enter>
You'll get message 'waiting for any device'.
- Turn off the phone, hold Volume Down and connect to PC. Post the result.
What is region? (Cxxx)
Click to expand...
Click to collapse
First of all, thank you man. It was suggested by someone on XDA, I shouldn't have done it.
I think the regional code is C121, I bought it in Turkey.
The thing is my phone doesn't turn off. Even when I force it by holding the button, it just turns back on. It stays like that until the battery dies.
I can open the fastboot screen by holding the vol down button and it says:
ap_s_abnormal 64
phone unlocked
frp unlocked
Have you tried connect to PC, then press and hold Power + Vol Down for 10-12 sec?
soslusos said:
It was suggested by someone on XDA
Click to expand...
Click to collapse
I bet I know who it was
Yeah I tried that, it just opens fastboot mode after phone restarts.
soslusos said:
Yeah I tried that, it just opens fastboot mode after phone restarts.
Click to expand...
Click to collapse
Game over . Test point method & board SW or DC-Phenix is your friend (maybe...). Unfortunately, I can't help you with this, I've never done it.
Damn. I don't even know what they are Can customer services do anything with this? I guess I'll have to pay.
soslusos said:
Can customer services do anything with this?
Click to expand...
Click to collapse
I guess so. It's all a matter of money .
Haha yeah but some stuff you do on your phone might be irreversible, that's what I'm afraid of.
So do you actually know what caused my device to boot into TWRP menu only? Is it because TWRP is incompatible with Android 9.1? (Or is it?)
soslusos said:
some stuff you do on your phone might be irreversible
Click to expand...
Click to collapse
Yes, e.g. damaged motherboard...
soslusos said:
So do you actually know what caused my device to boot into TWRP menu only? Is it because TWRP is incompatible with Android 9.1? (
Click to expand...
Click to collapse
Of course I cannot say that for sure. But I can say for sure that doing 'data format' (running stock EMUI) on some TWRP 3.4. and above can brick Kirin 659 device.
@-Alf- Hey, my phone is finally fixed. Do you know what's the latest firmware for 9.1 and where to download it? I'll install that one after rooting my phone.
soslusos said:
what's the latest firmware for 9.1
Click to expand...
Click to collapse
Hi, .401 (for C432 region)
soslusos said:
where to download it?
Click to expand...
Click to collapse
via OTA update
soslusos said:
I'll install that one after rooting my phone.
Click to expand...
Click to collapse
I would suggest updating first and then root
OTA says 9.1.0.208 is the latest version but I highly doubt that, something must be wrong with this ROM because the customer service guy installed it. My phone is C121 by the way.
soslusos said:
OTA says 9.1.0.208 is the latest version but I highly doubt that, something must be wrong with this ROM because the customer service guy installed it. My phone is C121 by the way.
Click to expand...
Click to collapse
Try to update via HiSuite or using option "Download latest version etc." in eRecovery. Maybe .208 is really the latest version for regional variant C121, idk...
-Alf- said:
Try to update via HiSuite or using option "Download latest version etc." in eRecovery. Maybe .208 is really the latest version for regional variant C121, idk...
Click to expand...
Click to collapse
So I was gonna roll back to EMUI 8 to unlock the bootloader but this time there's no "Switch to previous versions" option... In phone settings it says LGRP_OVS 9.1.0.208, is that the cause? How am I gonna unlock the bootloader now? So confused, I don't want to mess things up this time
soslusos said:
LGRP_OVS 9.1.0.208, is that the cause?
Click to expand...
Click to collapse
Yes, it is. Incompatible or incomplete FW .
In fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
{
"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"
}

Question Phone stuck in bootloop, unable to boot into fastboot

Hello all, I've been trying to install /e/ os GSI on my Redmi Note 11S. I already unlocked the bootloader.
Whenever i tried flashing system.img, (with boot.img patched manually via fastboot, not via a custom recovery), the phone would only boot fastboot. So I tried installing this custom recovery, and patch boot.img from there, but that still wouldn't work (though the recovery at least worked). So I tried installing the stock ROM, and try something else.
I went with latest fastboot EEA image and ran flash_all.sh (worked last time I tried), but this time I got an error (something about partition preloader not found). So I restarted the phone after which it got stuck in this bootloop. Can't boot into fastboot, nor recovery. Instead, the phone keeps flashing the mi logo on and off every 5 seconds. fastboot on my Linux install can't detect the phone. My Windows 10 install can't find it either, though it plays the "device connected" sound followed by the "device disconnected" sound shortly after. I can't turn the phone off either. Windows 10 USB drivers worked, or at least when I was unlocking the bootloader, so I don't think the issue is there. Any idea how to fix this?
Thank you in advance
Edit: Typos. Also I noticed that it only plays the "device connected" and "disconnected" sounds on Windows 10 only when i hold down the power and vol- buttons.
UPDATE: This tool can at least detect the phone, though I do get this error afterwards:
{
"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"
}
UPDATE: Managed to get FASTBOOT back, thanks to this kind stranger (system is still unbootable).
UPDATE: IT'S ALIVE! Did a quick install_all.sh on the stock ROM, and it's working again! Thank you all for helping me resolve this problem
no idea
Normally you use flashall.bat and not .sh, try using flashall.bat and hopefully you'll get out of the bootloop.
Try following my "how to fix bootloop" guide again, atleast till step 4 when you get the fastboot mode back up again.
warhead1721972 said:
Normally you use flashall.bat and not .sh, try using flashall.bat and hopefully you'll get out of the bootloop.
Try following my "how to fix bootloop" guide again, atleast till step 4 when you get the fastboot mode back up again.
Click to expand...
Click to collapse
Could you send a link to the guide please? The only guide I could find on your profile is the one with the rooting, which is among the first guides I tried and it was the one to get me into this situation. Note that in your guide, it appears that you can at least get to the FASTBOOT screen, which I can't. My phone just stays on the logo for 5 seconds before rebooting, and no matter which buttons I press or hold, I can't get it to go to the FASTBOOT screen.
Also, what's the difference between flash_all.bat, and flash_all.sh, aside of one being for Linux and the other for Windows?
UPDATE: This tool can at least detect the phone, though I do get this error afterwards:
kritomas said:
Could you send a link to the guide please? The only guide I could find on your profile is the one with the rooting, which is among the first guides I tried and it was the one to get me into this situation. Note that in your guide, it appears that you can at least get to the FASTBOOT screen, which I can't. My phone just stays on the logo for 5 seconds before rebooting, and no matter which buttons I press or hold, I can't get it to go to the FASTBOOT screen.
Also, what's the difference between flash_all.bat, and flash_all.sh, aside of one being for Linux and the other for Windows?
Click to expand...
Click to collapse
Press and hold all the 3 buttons, vol +, vol - and power button at the same time, till you see the phone switched off for a few seconds.
Then press the power and vol - button to get to the fastboot mode.
About the flashall.bat, I completely forgot that you were using Linux my bad.
Also sometimes some drivers don't work well in Linux try using windows.
Did you follow the guide which was at the end of this?
warhead1721972 said:
Press and hold all the 3 buttons, vol +, vol - and power button at the same time, till you see the phone switched off for a few seconds.
Then press the power and vol - button to get to the fastboot mode.
About the flashall.bat, I completely forgot that you were using Linux my bad.
Also sometimes some drivers don't work well in Linux try using windows.
Did you follow the guide which was at the end of this?
Click to expand...
Click to collapse
Yes, that's the one, and it won't go into fastboot.
Isn't /e/ Murena GSI just android 10? I am pretty sure it won't work. I had the same problem, but I fixed it by installing stock ROM..​
And that /e/ GSI is not actively developed and not even in beta stage (not usable at most cases)
​
Don't use SP Flash tool for full flash this phone seriously, Sp flash tool will make your phone stuck in recovery miui and show Nvdata Corrupted even you choose download only mode.
for now try to use mtkclient to flash boot.img only to both side A&B.
move your boot.img to mtk client folder
open cmd on that folder
type this command:
Code:
python mtk w boot_a,boot_b boot.img,boot.img
and try turn on your phone.
if still can't boot try to flash one by one img from your firmware
I has your same problem. Just hold the vol- for more than your usually Need and should boot into fastboot and than you flash with flashall.bat
I've sucessfully restore my phone and work as normal.
soutaminori said:
Don't use SP Flash tool for full flash this phone seriously, Sp flash tool will make your phone stuck in recovery miui and show Nvdata Corrupted even you choose download only mode.
for now try to use mtkclient to flash boot.img only to both side A&B.
move your boot.img to mtk client folder
open cmd on that folder
type this command:
Code:
python mtk w boot_a,boot_b boot.img,boot.img
and try turn on your phone.
if still can't boot try to flash one by one img from your firmware
Click to expand...
Click to collapse
Thank you so much, it worked!!!
I think. It's now at least on the FASTBOOT screen, which is progress. And the MIUI recovery is now back as well. While the system is still unbootable, I think I can take it from here. Thank you
Hypeka said:
I has your same problem. Just hold the vol- for more than your usually Need and should boot into fastboot and than you flash with flashall.bat
I've sucessfully restore my phone and work as normal.
Click to expand...
Click to collapse
That's the first thing I tried, and no luck. But I fixed it now (I think).
Very welcome, Glad to hear that
Note for everyone:
Backup this partition it's very important.
nvcfg.img, nvdata.img, nvram.img, persist.img, proinfo.img, protect1.img, protect2.img, md1img.img
Thats all partition about imei, security and network configuration for ur device. CMIW.
mtkclient also can do that,
and it's the clue:
Code:
python mtk r nvcfg,nvdata,nvram,persist,proinfo,protect1,protect2,md1img nvcfg.img,nvdata.img,nvram.img,persist.img,proinfo.img,protect1.img,protect2.img,md1img.img
Check ur mtk client folder, now you got the back up.
u can also use this Partitions Backup & Restore this tool don,t need PC for backup and restore, but i'm not really sure can be work perfectly. i just try for boot partition and its worked.
cheeerrss
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
alzhuks said:
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
Click to expand...
Click to collapse
i can't see mtk client log. but maybe driver problem or try to unlock BL again with THIS TOOL
alzhuks said:
Hi. Could you help me to unbrick my Note 11S 4g? I faced with bootloop after trying rooting phone by twrp. And now i can`t enter to fastboot.
When i try to - python mtk w boot_a,boot_b boot.img,boot.img
Or when I try to disable auth brom i have another one issue.
Click to expand...
Click to collapse
I myself did it with the terminal and on Linux. I didn't use the GUI, so I can't help with that. Could you send a higher res picture of the terminal please? We can't really see anything.
If you're doing this on Windows, then my guess is a driver issue (I did have to install a special driver for Windows to work with Fastboot, could be that mtk needs it too).
Hi All,
I unbricked my phone by using fresh release of mtkclient (https://github.com/bkerler/mtkclient).

Categories

Resources