Question Redmi Note 10 bricked - Redmi Note 10

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.

Related

{HELP}only fastboot is accessible

(used unofficial way to unlock) .please anyone help only fastboot screen is accessible not edl and nothing other,bricked by flashing 7.2.3 recovery rom through twrp-cofface recovery.
please help as soon as possible not able to access device
when i try to switch on the phone then mi logo blinks fro two times then gets off.
when tried miflash it says device is locked .
in device manager this shows when connected in fastboot modeView attachment 3736364
this shows when connected for chargingView attachment 3736365
and when try to flash with miflash tool this error comes
{
"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"
}
shubham tech said:
please anyone help only fastboot screen is accessible not edl and nothing other,bricked by flashing 7.2.3 recovery rom through twrp-cofface recovery.
please help as soon as possible not able to access device
when i try to switch on the phone then mi logo blinks fro two times then gets off.
when tried miflash it says device is locked .
in device manager this shows when connected in fastboot modeView attachment 3736364
this shows when connected for chargingView attachment 3736365
Click to expand...
Click to collapse
Are you able to access recovery (Power + Vol Up)?
If not:
Marshall London Bootloader Interface gave me some problems before. Try this:
1. Right-click "Marshall London Bootloader Interface" in your Device Manager and click "Update Driver Software..."
2. Select "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. In the list you should be able to find "Android" (or something like that) and in the sub-menu "ADB" (again, something like that), provided you have adb drivers installed on your computer.
5. Select "ADB" drivers to replace "Marshall London Bootloader Interface"
You should be able to use ADB in a command window to reapply Cofface's TWRP recovery and access it. If it's in Chinese see my comment here.
Hope this helps solve at least some of the problem.
Does your bootloader officially unlocked? If yes, just download a miui fastboot rom, and flash it through miflash
Edit: oops I didn't read the whole post. sorry
shubham tech said:
please anyone help only fastboot screen is accessible not edl and nothing other,bricked by flashing 7.2.3 recovery rom through twrp-cofface recovery.
please help as soon as possible not able to access device
when i try to switch on the phone then mi logo blinks fro two times then gets off.
when tried miflash it says device is locked .
in device manager this shows when connected in fastboot modeView attachment 3736364
this shows when connected for chargingView attachment 3736365
Click to expand...
Click to collapse
Hello..
I too faced such situation...
I tried to root my redmi note 3 pro..(SD)
I followed the unofficial method which I found here in XDA.. Don't know ,where I missed any step...
My phone gets in same situation as yours..
It can boot into fastboot mode ( volume - and power ),
If I turn on it flashes mi logo two times and .. Gets into diagnostic mode ...
Searched a lot.. But.. Can't find my exact situation in any thread..
Somewhere in some forum I found that.. Let the battery be fully drain.. And.. Without turning on.. Charge the phone to at least 30% .. And den enter edl mode by pressing and holding two volume buttons...( + & -).
My mobile is at 97 % of charge when it got bricked .
Which means... A few days to drain it fully..
Omg... I can't wait..
So.. I decided to open the back cover..
Gently opened it.. And.. Removed battery strip.. And.. Placed it again ...
Den..
While connecting to PC through USB cable..
I pressed and hold the two volume buttons..
Connected cable..and.. Pressed both volume buttons as fast as I can after connecting cable.. And holded for two secs..
There. U can enter edl mode...
So that u can flash.. Global stable ROM..via mi flash tool...
If u failed...
Remove the battery connector . and.. Put it again..
Close mi flash.. Open it again.. Try to put the phone in edl again...
I don't know .this can be done in another easy way..
But.. I have done this way...
Tell me if u succeed..
can you execute "adb devices" and "adb reboot edl" in command window when connecting your phone to PC? if so, you might use latest MiFlash (20160330 or 20160401) to flash rom.
MIUI forum has a guide to rescue bricked redmi note 3, you should have a look at it.
The posts are http://en.miui.com/thread-274589-1-1.html and http://en.miui.com/thread-235865-1-1.html
If the vol + and - trick does not work, I was in the same situation and I ended up doing this: http://forum.xda-developers.com/redmi-note-3/how-to/redmi-note-3-pro-snapdragon-650-edition-t3367774
if you unlock official way, just run the unlock tools again
Immortal68 said:
Are you able to access recovery (Power + Vol Up)?
If not:
Marshall London Bootloader Interface gave me some problems before. Try this:
1. Right-click "Marshall London Bootloader Interface" in your Device Manager and click "Update Driver Software..."
2. Select "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. In the list you should be able to find "Android" (or something like that) and in the sub-menu "ADB" (again, something like that), provided you have adb drivers installed on your computer.
5. Select "ADB" drivers to replace "Marshall London Bootloader Interface"
You should be able to use ADB in a command window to reapply Cofface's TWRP recovery and access it. If it's in Chinese see my comment here.
can you tell about this in some brief from where to select which driver please help?
Hope this helps solve at least some of the problem.
Click to expand...
Click to collapse
can you tell about this in some brief from where to select which driver please help?
shubham tech said:
can you tell about this in some brief from where to select which driver please help?
Click to expand...
Click to collapse
Created a short slide show. Hope this helps.
If you don't see "Android ADB Interface you have to install ADB/fastboot first. Minimal ADB and fastboot drivers
Best of luck. Let me know if anything else is still unclear to you.
Abhi45 said:
Hello..
I too faced such situation...
I tried to root my redmi note 3 pro..(SD)
I followed the unofficial method which I found here in XDA.. Don't know ,where I missed any step...
My phone gets in same situation as yours..
It can boot into fastboot mode ( volume - and power ),
If I turn on it flashes mi logo two times and .. Gets into diagnostic mode ...
Searched a lot.. But.. Can't find my exact situation in any thread..
Somewhere in some forum I found that.. Let the battery be fully drain.. And.. Without turning on.. Charge the phone to at least 30% .. And den enter edl mode by pressing and holding two volume buttons...( + & -).
My mobile is at 97 % of charge when it got bricked .
Which means... A few days to drain it fully..
Omg... I can't wait..
So.. I decided to open the back cover..
Gently opened it.. And.. Removed battery strip.. And.. Placed it again ...
Den..
While connecting to PC through USB cable..
I pressed and hold the two volume buttons..
Connected cable..and.. Pressed both volume buttons as fast as I can after connecting cable.. And holded for two secs..
There. U can enter edl mode...
So that u can flash.. Global stable ROM..via mi flash tool...
If u failed...
Remove the battery connector . and.. Put it again..
Close mi flash.. Open it again.. Try to put the phone in edl again...
I don't know .this can be done in another easy way..
But.. I have done this way...
Tell me if u succeed..
Click to expand...
Click to collapse
thanks for help but didnt succeed.
Immortal68 said:
Created a short slide show. Hope this helps.
If you don't see "Android ADB Interface you have to install ADB/fastboot first. Minimal ADB and fastboot drivers
Best of luck. Let me know if anything else is still unclear to you.
Click to expand...
Click to collapse
thanks for help but none of above worked for me.
adb things will not work if phone just got to fastboot.
you must look on 'ports' section on device manager.
it will detect qcom hs-usb qloader 9008 if you're on edl mode (you can use miflash on this situation).
but on bricked phone it will show qcom hs-usb diagnostic 900e if you try to enter edl. here you can't do anything.
the only working solution known is by disassembling the phone and use test-point method.
but luckily I don't have to do it. mine works just by re-unlock using unlock tool.
just apply the unlock code with your last entered mi account on phone. when you got the sms, go unlock it
aabenroi said:
adb things will not work if phone just got to fastboot.
you must look on 'ports' section on device manager.
it will detect qcom hs-usb qloader 9008 if you're on edl mode (you can use miflash on this situation).
but on bricked phone it will show qcom hs-usb diagnostic 900e if you try to enter edl. here you can't do anything.
the only working solution known is by disassembling the phone and use test-point method.
but luckily I don't have to do it. mine works just by re-unlock using unlock tool.
just apply the unlock code with your last entered mi account on phone. when you got the sms, go unlock it
Click to expand...
Click to collapse
even unlock tool says cant verify device, this is really a xiaomi,dont expect anything better from xiaomi.
shubham tech said:
even unlock tool says cant verify device, this is really a xiaomi,dont expect anything better from xiaomi.
Click to expand...
Click to collapse
If u had not opened ur phone and tried test point method , take it to service center ASAP.
sanjib734 said:
If u had not opened ur phone and tried test point method , take it to service center ASAP.
Click to expand...
Click to collapse
yes i am going to service center on tomorrow .
shubham tech said:
yes i am going to service center on tomorrow .
Click to expand...
Click to collapse
best of luck.
sanjib734 said:
best of luck.
Click to expand...
Click to collapse
got my phone repaired from mi service center.
Immortal68 said:
Are you able to access recovery (Power + Vol Up)?
If not:
Marshall London Bootloader Interface gave me some problems before. Try this:
1. Right-click "Marshall London Bootloader Interface" in your Device Manager and click "Update Driver Software..."
2. Select "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. In the list you should be able to find "Android" (or something like that) and in the sub-menu "ADB" (again, something like that), provided you have adb drivers installed on your computer.
5. Select "ADB" drivers to replace "Marshall London Bootloader Interface"
You should be able to use ADB in a command window to reapply Cofface's TWRP recovery and access it. If it's in Chinese see my comment here.
Hope this helps solve at least some of the problem.
Click to expand...
Click to collapse
Sorry to chime in (and open up this discussion) months later, but: I have marshall london bootloader interface Here's the thread with my issue http://en.miui.com/thread-362628-1-1.html (if you don't mind). My phone has finally powered off after bootlooping for hours (was able to switch between fastboot mode and mi logo bootloop). Waiting to recharge and try and enter recovery or try this (http://xiaomitips.com/guide/how-to-put-redmi-note-3-into-edl-mode/). Maybe you have some other pointers for me? Please? :laugh: I'm nearing my wits end
Hope this isn't rude and all and hope you have some ideas. Thanks in advance!
shubham tech said:
got my phone repaired from mi service center.
Click to expand...
Click to collapse
how much time they take to repair it
devsc said:
how much time they take to repair it
Click to expand...
Click to collapse
½ an hour
Sent from my Redmi Note 3 using Tapatalk

[GUIDE][A2017G] Reinstall TWRP and Root after update to Nougat

Get TWRP and root after updating to Nougat​
This method worked for me, but be aware, it might not work for your specific device. in a worst-case scenario, you'll brick your device - proceed at your own risk!
For devices with UNLOCKED BOOTLOADER! This guide does not show you how to unlock the bootloader
BIG thanks to @tamahouse02, @bkores, @S0wL and @tron1 for the help they gave me when trying to do this on my own device. This post is just a compilation of everything we tested over the old questions/answers post.​
How To:
Set up axon7tool and download TWRP
Download axon7tool from here. Thanks tennear for the awesome tool
Download TWRP for ailsa_ii, newest one available. I used 3.1.0.0
Download Zadig and throw the exe somewhere
I asume that you already have adb installed, if not install it with 15 seconds installer
Put axon7tool on your adb folder, rename it to axon7tool.exe
Put TWRP image on the same folder, rename it to recovery.img (you NEED TO BE ABLE TO SEE THE FILE EXTENSION! Google how to enable that)
Duplicate the recovery.img, rename it recovery.bin, keep it in the same place
Connect your phone, enable USB debugging, open CMD and run adb reboot edl
Open Device Manager once your phone looks like it's off. You should see a Qualcomm HS-USB QDLoader 9008 under Ports - COM & LPT, uninstall it AND TICK DELETE DRIVER SOFTWARE TOO and hold the three buttons of your phone (vol buttons and power) for quite a lot of time, until you see that the device manager list refreshes. If Windows attempts to install the driver cancel it at once, repeat the process if it did install it (it appears as a Qualcomm thing again). After holding the 3 buttons you should see an unidentified device named QUSB_BULK
After you have the QUSB_BULK device fire up Zadig and Install the driver.
Flash TWRP using axon7tool
Hold the 3 buttons of your phone again until device manager refreshes
Open CMD on your adb folder (go to the folder, SHIFT+right click anywhere, open command window here)
run axon7tool -r recovery gpt boot
Leave CMD open. Go to the folder where the tool is and make a folder named backups or whatever, put all the backups there (recovery_backup.bin for example)
You should have made a recovery.img and recovery.bin there before. Check that you left them there, just to be sure
Finally, on the CMD window, run axon7tool -w recovery. If it fails try holding the three buttons, opening cmd again and trying this step again. otherwise post your error here
If it succeeds disconnect your usb cable from the phone BEFORE THE COUNTDOWN ENDS, then hold the power button for like an eternity until the phone reboots. If you don't do this your TWRP will be replaced by the stock recovery. you only have to do the previous step again in that case, don't worry.
Either while the phone is booting or with adb after it gets to system, get to the recovery and test if it boots. Congrats if it does!
Install SuperSU
You probably know how to do this if you came this far. If you don't:
Download SuperSU 2.79 from somewhere on the internet
Get to TWRP
Flash SuperSU
Avoid the inherent nervous breakdown that the initial bootloop causes (in layman's terms, don't freak out, let it do its thing)
Done
Get Fastboot
Download this ZIP (thanks @sToRm1nG) and put it in the root of your phone's storage
Go to TWRP and flash the ZIP
Boot system and adb reboot edl
Now we need to replace the Zadig driver, sorry you'll find QUSB_BULK under USB devices (bottom of the list in English), uninstall and check Delete driver software too
Hold the 3 keys
Windows might attempt to install the driver. Leave it, hopefully it will. You need to get Qualcomm HS-USB QDLoader 9008. If it appears as an unknown device google for the driver (just google Qualcomm HS-USB QDLoader 9008 driver and you'll get it) and install it, then hold the 3 buttons and check if the QDLoader 9008 appears under Ports COM&LPT
Download MiFlash from here, and the fastboot package from here
Unpack the fastboot package somewhere, be careful not to unpack it like a folder with another one inside, but rather one folder directly with all the stuff inside
Open MiFlash and select the folder that you unpacked
Select Refresh, then your device should appear. if it doesn't then you didn't reload EDL or you didn't install the Qualcomm drivers, simply do that again. If it appears go ahead and choose Flash
Reboot and try if it worked, by selecting Fastboot from the 5 sec menu or using adb once you're booted
All done. I'm not a developer of any kind, so I'm afraid i won't be able to help with specific errors. But most simple errors you could have are described here, so you should have little trouble doing the procedure.
Hope the best of luck to y'all while doing this
I just tested unfortunately with the much less easy to read original problem thread that described process works fine! Thanks!
Thanks for the Guide!
My Axon 7 (G-Modell - Nougat 7.1.1) is located in the EDL and is under Device Manager as
"Qualcomm HS-USB QDLoader 9008" detected, but MiFlash does not recognize it. The latest drivers from Qualcomm are installed and I use the original cable from ZTE, but it does not want to be recognized ;-(
Thank you man!I'm already Rooted in Nougat 7.0 in my A2017G..... But AdAway can't write the host file, do you have the same issue?
No idea, I never use AdAway. BTW can you cut down the quote a little bit? A lot of people complain about the huge quotes
jorgex said:
Thank you man!I'm already Rooted in Nougat 7.0 in my A2017G..... But AdAway can't write the host file, do you have the same issue?
Click to expand...
Click to collapse
Download any terminal emulator app and execute:
Code:
su
then
Code:
reboot disemmcwp
it seems that i soft bricked my device.. after i flashed TWRP my A2017G only shows me the Bootscreen.. what to do now?
4ert said:
it seems that i soft bricked my device.. after i flashed TWRP my A2017G only shows me the Bootscreen.. what to do now?
Click to expand...
Click to collapse
Did you try to get to TWRP? Does it show the BL unlocked screen, or just the boot logo?
Otherwise try to get to fastboot however you can, then flash TWRP again, or you can try getting to EDL and restoring the backups that you hopefully made. I have no idea how the DFU mode thing is, but I would do some research on that. I'm no dev
Thanks for this guide saved my day.
do i need an unlocked bootloader for this to work?
DarkShadowSwE said:
do i need an unlocked bootloader for this to work?
Click to expand...
Click to collapse
I assume you do. Try the method in here. I have no idea if that will work for Android 7.1.1 though, so I hope you still have android 6
Please help, I have the same problem as logimowl:
My Axon 7 (G-Modell - Nougat 7.1.1) is located in the EDL and is under Device Manager as
"Qualcomm HS-USB QDLoader 9008" detected, but MiFlash does not recognize it. The latest drivers from Qualcomm are installed and I use the original cable from ZTE, but it does not want to be recognized
@icaros1530 Huh I've just installed 7.1.1 official today, so I have to do the process again. I've just opened MiFlash and it detects stuff nicely. The device appears as COM5 on MiFlash and the driver is under Ports (COM & LPT) with the name Qualcomm HS-USB QDLoader 9008 (COM5)
Choose an username... said:
@icaros1530 Huh I've just installed 7.1.1 official today, so I have to do the process again. I've just opened MiFlash and it detects stuff nicely. Look
{
"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"
}
Click to expand...
Click to collapse
Thanks for checking and posting the screenie. I've been on the issue since yesterday now and found a suggestion to try on a different computer, so I tried again and it worked on my win10 notebook. So issue is insofar solved as my smartphone is now running 7.1.1 and rooted and all. Why miflash just can't connect on my win10 pc.. I have no clue. I've rebooted device and pc tons of time with different drivers, even trying the old root methods, used zadig whatever. Everything looks the way it should - but some minor thing hiding somewhere just won't let it work.
td;dr: if miflash can't connect try different computer..
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
bkores said:
Download any terminal emulator app and execute:
Code:
su
then
Code:
reboot disemmcwp
Click to expand...
Click to collapse
That doesn't work for me. The command reboots the device, but Adaway keeps saying host files couldn't be copied.
SOLVED: for 7.1.1. we seem to need the systemless version of adaway. I picked up version 3.2 from here and it works perfectly: https://forum.xda-developers.com/showthread.php?t=2190753
@icaros1530 lol I'm gonna add that to the OP (try different computers if it doesn't work)
All these programs are extremely nitpicky it seems!
And I uploaded 2 pictures, but only one showed up, so I just deleted them and added some text. That's why i edited, i just wanted to make that clear
Thanks dude! Clear and simple instructions, got TWRP and root running on my A2017G 7.1.1
Anyone get the 'can't receive hello packet' when flashing?
lesterp said:
Anyone get the 'can't receive hello packet' when flashing?
Click to expand...
Click to collapse
flashing what? with miflash?
Choose an username... said:
flashing what? with miflash?
Click to expand...
Click to collapse
Yes using Miflash
A few reboots of phone and laptop and it flashed.

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?

Hard brick any solution

1.unlock bootloader
2.flashed magsik boot.img
3.lock bootloader
4. infinity bootloop cant enter fastboot mode
ankitnaik16 said:
1.unlock bootloader
2.flashed magsik boot.img
3.lock bootloader
4. infinity bootloop cant enter fastboot mode
Click to expand...
Click to collapse
Having the same problem. Is there a firmware available online for flashing?
Cedric Miraflor said:
Having the same problem. Is there a firmware available online for flashing?
Click to expand...
Click to collapse
it is possible to flash with sp tool but it require scatter file can someone provide scatter file of realme 6
ankitnaik16 said:
it is possible to flash with sp tool but it require scatter file can someone provide scatter file of realme 6
Click to expand...
Click to collapse
By using sp tool is it required for the device to go to fast boot mode? because currently we cant access fastboot using power down with power button
Cedric Miraflor said:
By using sp tool is it required for the device to go to fast boot mode? because currently we cant access fastboot using power down with power button
Click to expand...
Click to collapse
SP Tool work in Download Mode it can be access by pressing volume up + volume down key while phone is off
I see. Im just waiting for somebody with the scatter file for this device
ankitnaik16 said:
1.unlock bootloader
2.flashed magsik boot.img
3.lock bootloader
4. infinity bootloop cant enter fastboot mode
Click to expand...
Click to collapse
You can't flash it through SP flash or any flash tool. Realme Doesn’t allow user to flash it by their own though Xaomi Samsung Allow user to flash their own Android. I also tried but after downloaded 12 GB file its need authenticating id provided by Realme. Just take it to care and let them fix it. Never buy Realme ?
RantiHasan said:
You can't flash it through SP flash or any flash tool. Realme Doesn’t allow user to flash it by their own though Xaomi Samsung Allow user to flash their own Android. I also tried but after downloaded 12 GB file its need authenticating id provided by Realme. Just take it to care and let them fix it. Never buy Realme
Click to expand...
Click to collapse
You Are right Never Buy Realme
I finally went to service center process is too slow and tedious
Going to sell this phone and buy oneplus nord
ankitnaik16 said:
1.unlock bootloader
2.flashed magsik boot.img
3.lock bootloader
4. infinity bootloop cant enter fastboot mode
Click to expand...
Click to collapse
i think realme dont allow you install patched boot when bootloader locked, you should leave bootloader unlocked and never locked it again if you want modified your device.
Same
just like me bro After I can't enter the system (bootloop) now I can't enter recovery mode, and again I want to flash Realme 6 but can't, I can't even enter EDL mode,(power & button plus + minus) on my PC was only detected for a moment,
Letinamazuki said:
just like me bro After I can't enter the system (bootloop) now I can't enter recovery mode, and again I want to flash Realme 6 but can't, I can't even enter EDL mode,(power & button plus + minus) on my PC was only detected for a moment,
Click to expand...
Click to collapse
You find solutions
I have same issue. I went to sc and they said they couldn't detect the phone on pc, then they provide one only solution which to replace the whole circuit board
did anyone found any solution?
2021, Please, i want any solution
solution is in the link below
[GUIDE] UNBRICK/DOWNGRADE YOUR REALME 6/6I(INDIA)/6S USING SPFLASH TOOL FOR FREE!
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY...
forum.xda-developers.com
mercan01 said:
solution is in the link below
[GUIDE] UNBRICK/DOWNGRADE YOUR REALME 6/6I(INDIA)/6S USING SPFLASH TOOL FOR FREE!
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY...
forum.xda-developers.com
Click to expand...
Click to collapse
I can't even enter EDL mode,(power & button plus + minus) on my PC was only detected for a moment, the phone in eternal black screen
erickdiazw said:
I can't even enter EDL mode,(power & button plus + minus) on my PC was only detected for a moment, the phone in eternal black screen
Click to expand...
Click to collapse
I have the same issue. Did you find any solution?
The solution is easy, just need follow de guide,
1 install python and LibUSB Win
2 the phone is black screen, just press power putton and volume + for 10 seconds (The Phone will reboot, stop pressing buttons)
3 (You need be fastt) instantly press power button and volume -, connect the phone to pc and next press volume +, dont stop pressing (Lib USB Win already installed and open on your PC)
4 Select Mediatek On LibUSB Win, install, and all its ready,
{
"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"
}
5 The phone automatically reboots, you need to do step 2 and 3 again, but instead of LIbUSB WIn it will be brom.bat
6 If you followed all this steps good, your phone be ready to unbrick
erickdiazw said:
The solution is easy, just need follow de guide,
1 install python and LibUSB Win
2 the phone is black screen, just press power putton and volume + for 10 seconds (The Phone will reboot, stop pressing buttons)
3 (You need be fastt) instantly press power button and volume -, connect the phone to pc and next press volume +, dont stop pressing (Lib USB Win already installed and open on your PC)
4 Select Mediatek On LibUSB Win, install, and all its ready,
5 The phone automatically reboots, you need to do step 2 and 3 again, but instead of LIbUSB WIn it will be brom.bat
6 If you followed all this steps good, your phone be ready to unbrick
Click to expand...
Click to collapse
Hi @erickdiazw
This is for MediaTek chipset , any solution for Qualcomm Chipset?
I have a hardbricked Realme 6 Pro device because of re-lock bootloader
gaduaxe said:
Hi @erickdiazw
This is for MediaTek chipset , any solution for Qualcomm Chipset?
I have a hardbricked Realme 6 Pro device because of re-lock bootloader
Click to expand...
Click to collapse
I'm sorry bro, i have Realme 6 with MediaTek, idk for Qualcomm :c

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