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.
Related
(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
Hi,
i have a problem with ADB drivers for the phone. i have downloaded it from Sony (Link:https://developer.sonymobile.com/downloads/drivers/xperia-x-driver/) and install it like they said (by going in to device manager and manually installing it). after booting it to Fastboot, Flashtool says i have to install them from the drivers folder, which however, does not contain the Xperia X driver. Also, when selecting the Flashboot and Flashmode drivers, one installs but the other doesn't which is "Google, Inc, (WinUSB) Android UsbDeviceClass".
While in Fastboot, i tired to delete it, then update it using the download driver from Sony which failed to install. Also, in device manager it say something like S1 fastboot driver with a Waring symbol (it's not recognised), and upon checking in flashtool while in Fastboot, it says there is no ADB drivers installed, just Fastboot.
i have tried booting the phone with USB debugging and it does recognise it, but still doesn't work when booting to Fastboot.
BTW i am on Windows 10
any information would be useful.
Force install adb driver over device manager
max26292 said:
Force install adb driver over device manager
Click to expand...
Click to collapse
thanks, just to confirm, by force install do you mean to download from sony and install within device manager, by 'adding legacy software' ?
if so, i have done that and the driver appears, and shows the following error:
This device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
Also, still and unrecognised 'S1 fastboot ' driver appeared when in Fastboot.
thank you again.
remar786 said:
thanks, just to confirm, by force install do you mean to download from sony and install within device manager, by 'adding legacy software' ?
if so, i have done that and the driver appears, and shows the following error:
This device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
Also, still and unrecognised 'S1 fastboot ' driver appeared when in Fastboot.
thank you again.
Click to expand...
Click to collapse
If you install Jdk you already have driver, you just right click choose update driver> choice option 2 ( I choose driver from my computer > choose from list device > android > adb. Next, it will show a alert message bla bla > yes :3 use flash tools again to see the magic
max26292 said:
If you install Jdk you already have driver, you just right click choose update driver> choice option 2 ( I choose driver from my computer > choose from list device > android > adb. Next, it will show a alert message bla bla > yes :3 use flash tools again to see the magic
Click to expand...
Click to collapse
quick question, what is JDK?
hopefully i will try when i hear back, thanks again .
How to install ADB Xperia x
finally!!!
it's worked. Thanks for your help max26292 (although would have been nice to hear back but a huge thank you!)!
Here's what i did (not in the exact order though)
i used the instruction from Sony - http://support.sonymobile.com/global-en/xperiae3dual/kb/0231018805656b91c0145c620eeaf004cb9/(Not for the Xperia X though but usable) on how to install the Xperia driver, and after restarting the PC, Flashtool still didn't recognise while in Fastboot. Also, in device manage there, was a Waring sign next to it, and gave the error as mentioned previously. image is below of the sign.
{
"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 then installed the 15 seconds ADB from https://forum.xda-developers.com/showthread.php?t=2588979 ( i keptpressing Y) after a reboot and putting the phone in Fastboot, still Flashtool had the same messages about drivers, like i said in the first post.
i then tired out max26292's method, which there are images below to show the process. i put the phone in Fastboot, and where the warning sign was, NOT THE SAME PLACE AS THE IMAGE SHOWN ABOVE, rather where it said "S1Boot Fastboot" . using the steps you mentioned (THANKS ALOT BTW!) :
i right clicked on the s1 fastboot> clicked update driver> chose the second option - browse my computer>
the clicked on "let me pick from a list of device drivers on my computer"> then browsed for the driver i'd already installed from Sony - the "Sony sa0114> kept clicking next, and yes to a warning message> restarted computer and BANG! it worked!
i however should mention that i did try to install the flashmode and fastboot driver from flashtool, but one of them failed to install - i have mentioned n my previous post, please refer back. so, you may want to do that, but i think the 15 seconds ADB will do it for you. also, i have not done commands so i can't test it out fully, bu when i do, i will let you know.
again i would like to thank everyone for your help, really appreciate it!
P.S. Please put a F U C K ING updated guide up Sony, T W A T s.
remar786 said:
finally!!!
it's worked. Thanks for your help max26292 (although would have been nice to hear back but a huge thank you!)!
Here's what i did (not in the exact order though)
i used the instruction from Sony - http://support.sonymobile.com/global-en/xperiae3dual/kb/0231018805656b91c0145c620eeaf004cb9/(Not for the Xperia X though but usable) on how to install the Xperia driver, and after restarting the PC, Flashtool still didn't recognise while in Fastboot. Also, in device manage there, was a Waring sign next to it, and gave the error as mentioned previously. image is below of the sign.
I then installed the 15 seconds ADB from https://forum.xda-developers.com/showthread.php?t=2588979 ( i keptpressing Y) after a reboot and putting the phone in Fastboot, still Flashtool had the same messages about drivers, like i said in the first post.
i then tired out max26292's method, which there are images below to show the process. i put the phone in Fastboot, and where the warning sign was, NOT THE SAME PLACE AS THE IMAGE SHOWN ABOVE, rather where it said "S1Boot Fastboot" . using the steps you mentioned (THANKS ALOT BTW!) :
i right clicked on the s1 fastboot> clicked update driver> chose the second option - browse my computer>
the clicked on "let me pick from a list of device drivers on my computer"> then browsed for the driver i'd already installed from Sony - the "Sony sa0114> kept clicking next, and yes to a warning message> restarted computer and BANG! it worked!
i however should mention that i did try to install the flashmode and fastboot driver from flashtool, but one of them failed to install - i have mentioned n my previous post, please refer back. so, you may want to do that, but i think the 15 seconds ADB will do it for you. also, i have not done commands so i can't test it out fully, bu when i do, i will let you know.
again i would like to thank everyone for your help, really appreciate it!
P.S. Please put a F U C K ING updated guide up Sony, T W A T s.
Click to expand...
Click to collapse
Please read carefully =-= I told Android driver not sony =-=
max26292 said:
Please read carefully =-= I told Android driver not sony =-=
Click to expand...
Click to collapse
thank you, but i don't have them. i only have the Sony ones and ADB by Samsung, which the 15 seconds ADB program installed.
when i connected to Fastboot, Flashtool does recognise it, so it should work right?
thanks again
pm me on facebook when you onl I think we should do a private mess and teamview
max26292 said:
pm me on facebook when you onl I think we should do a private mess and teamview
Click to expand...
Click to collapse
Thank you but it's working fine with the way I installed it (by installing the Sony driver from the list)
remar786 said:
Thank you but it's working fine with the way I installed it (by installing the Sony driver from the list)
Click to expand...
Click to collapse
you also use driver pack in flashtool because it include android driver
max26292 said:
you also use driver pack in flashtool because it include android driver
Click to expand...
Click to collapse
yes i did use it, but only one installed. i did before i installed both drives, (Fastboot and ADB) but one installed and one didn't ( i think the ADB driver failed and the other one installed).
remar786 said:
Hi,
i have a problem with ADB drivers for the phone. i have downloaded it from Sony (Link:https://developer.sonymobile.com/downloads/drivers/xperia-x-driver/) and install it like they said (by going in to device manager and manually installing it). after booting it to Fastboot, Flashtool says i have to install them from the drivers folder, which however, does not contain the Xperia X driver. Also, when selecting the Flashboot and Flashmode drivers, one installs but the other doesn't which is "Google, Inc, (WinUSB) Android UsbDeviceClass".
While in Fastboot, i tired to delete it, then update it using the download driver from Sony which failed to install. Also, in device manager it say something like S1 fastboot driver with a Waring symbol (it's not recognised), and upon checking in flashtool while in Fastboot, it says there is no ADB drivers installed, just Fastboot.
i have tried booting the phone with USB debugging and it does recognise it, but still doesn't work when booting to Fastboot.
BTW i am on Windows 10
any information would be useful.
Click to expand...
Click to collapse
1. install XPERIA COMPANION
2. INSTALL FLASHTOOL (www.flashtool.net)
3. after installing flastool goto C:\Flashtool\drivers and you will find "Flashtool-drivers.exe" / run it and install from list "common fastboot drivers", "common flashmod drivers" and xperia z series with Xperia X series motherboard drivers.
windows 10 gives digital signature verification errors so you have to
Use the following steps to disable driver signature enforcement.
Click the Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
Click to expand...
Click to collapse
then repeat point "3"
you should be ok
frp locked huawei honor 20 wont connect to laptop
hi mate im trying to connect my huawei honor 20 to my laptop but it doesnt even come up with anything in device manager. its frp locked and i need to access fastboot mode to enter the frp key. can anyone please help me.
Updated my phone to Android 7.1.2 today, using the built in updater.
Now when I restart, I get the following on the bootloader: "Your device is corrupt. It can't be trusted and may not work properly"
It still boots normally. But Android Pay doesn't work.
Any suggestions for fixing this?
I can't help, but I can confirm that the same has happened to me so you're not alone...
I had the same problem. I couldn't even start twrp anymore. I fixed it by flashing the full tos118c rom from fastboot. After that I let the ota install. I then reinstalled twrp and flashed magisk to root the phone. Now it boots without dm verity or corrupt message. Even the play store is now certified, so I can install Netflix without problem.
Also you can hide root so you can use Android pay.
WileyFox customer support?
I have the exact same issue.
My device started off by saying:
The dm-verity is not started in enforcing mode and may not work properly
Now after the update, I get the error message saying that the phone is corrupt and will power off if I dont press power within 30 seconds.
I contacted WileyFox when the first issue occurred and was told that I needed to send the phone back. I sent on my details and never heard back.
Ideally I would like to get the phone sorted without flashing a custom rom or recovery.
Has anyone else had issues with their support? Is it just my case they are managing badly, or is it an ongoing thing?
jamesmcd05 said:
I have the exact same issue.
My device started off by saying:
The dm-verity is not started in enforcing mode and may not work properly
Now after the update, I get the error message saying that the phone is corrupt and will power off if I dont press power within 30 seconds.
I contacted WileyFox when the first issue occurred and was told that I needed to send the phone back. I sent on my details and never heard back.
Ideally I would like to get the phone sorted without flashing a custom rom or recovery.
Has anyone else had issues with their support? Is it just my case they are managing badly, or is it an ongoing thing?
Click to expand...
Click to collapse
You can try reflashing using fastboot. That fixed it for me.
Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/showthread.php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!
RedNas74 said:
You can try reflashing using fastboot. That fixed it for me.
Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/showthread.php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!
Click to expand...
Click to collapse
Brilliant, thanks.
Didn't realise there were offical wileyFox builds available.
Much appreciated. I will give that a try
:fingers-crossed:
EDIT:
I got an error saying that:
target reported max download size of 535822336 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
Also my phone was OEM locked.
I unlocked the device and tried again, but got the same error.
So I unzipped the contents and manually flashed each img,. which seems to have worked fine
I re-enabled OEM lock and now the phone boots without errors.
Thanks a million
Just wanted to say thank you very much for the thread info.
I also got the error messages, but realised that I was just being a bit hasty. Waiting a further 20 seconds gives a couple of other messages about other .sig files missing, but then the update continues and the flash is completed. The 'corrupted' and 'dm-verity' messages have now gone and the phone appears to be functioning properly.
Hopefully it will now update OTA to the next version and do so without corruption.
Thanks again
David
Wait a minute.
I'm a almost complete newbie but perhaps you guys can help me out.
Like davids-h I also got the errors and after over seven (!) minutes I get:
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished.
What can I do or should I do?
Thanks in advance!
I have the same issue as Razorblattor above - please could someone chime in with any suggestions. Would be appreciated. Thanks
rjl_12345 said:
I have the same issue as Razorblattor above - please could someone chime in with any suggestions. Would be appreciated. Thanks
Click to expand...
Click to collapse
Update: I managed to get the ROM flashed by removing the SD card and SIM. I have no idea why this would have been an issue but it was. I could then flash the ROM. Thanks
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
The steps documented by asg1977 have also worked for me.
I had the issue on a Swift2X that was delivered factory standard with a Nougat image. It occured while taking the phone out of its cover, pressing the power button in the process. After that the phone rebooted consistently with the corrupted warning. (Even tough the phone worked fine once past that screen.)
asg1977 said:
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
Click to expand...
Click to collapse
Thanks for this, but when I open a command prompt, and type in adb devices, I get a message saying that
'adb' is not recognized as an internal or external command,
operable program or batch file. I have developer options activated and usb mode is switched on and set to mtp devices. I have downloaded the 2 sets of files (USB drivers and ADB, and unzipped them to the desktop. Where am I going wrong?
EDIT - SOLVED IT! The command prompt needs to be opened inside the platform tools folder, whereupon it will find the phone, and the adb reboot "dm-verity enforcing" command will work. Prior to this, I had to revoke usb debugging authorisation between the phone and computer, then reconnect the phone the computer, so the phone could be seen by the computer. Command prompts can be very finicky about how they work, but I got there in the end.
RedNas74 said:
You can try reflashing using fastboot. That fixed it for me.
Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/showthread.php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!
Click to expand...
Click to collapse
Hi sorry I have the same problem but I am new to all this, could someone send me a link to/write out a step by step instructions on how to do this?
Thanks in advance!
Louise
---------- Post added at 02:33 PM ---------- Previous post was at 02:06 PM ----------
louisew92 said:
Hi sorry I have the same problem but I am new to all this, could someone send me a link to/write out a step by step instructions on how to do this?
Thanks in advance!
Louise
Click to expand...
Click to collapse
Sorted now thanks!
I had the same issue and WF support fixed it for me
I had this issue previously when Wileyfox support was still active and they gave me this PDF file as a solution
{
"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"
}
3LzW said:
I had this issue previously when Wileyfox support was still active and they gave me this PDF file as a solution
Click to expand...
Click to collapse
FTFY:
Something weird about posting links makes me fail posting the correct link: https:// imgur.com/a/NHjGV
asg1977 said:
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
Click to expand...
Click to collapse
Thanks from Poland, genius! It works
My phone has developed this problem after I flashed TWRP, I've tried to follow instructions so I can enforce the DM verity reboot in a command line interface but if I select fastboot my phone stays on a load up screen and doesn't change. The only other thing I can access is TWRP, will I be able to use the terminal in that to solve this problem?
asg1977 said:
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
Click to expand...
Click to collapse
I know this is old.. but just wanted to say I wasn't able to do this from my laptop via adb - but used the terminal via TWRP and it worked.
Thanks a lot from Wales
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.
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).