nokia 6 ta1000 full brick. - Nokia 6 Questions & Answers

In my nokia 6 ta1000 , i flashed mena rom and used oreo for 3days. Now,today i wanted to roll back to my old ta1000 rom. So i flashed it .it was successful. But when the device booted it stuck in nokia ... Thn no progress. I think it bricked ... Thn i flashed again but no result... Now the device don't recognized by ost app also... Help me as soon as possibe,,as it is my daily driver .???
Note: it doesn't go to fastboot either. It just shows ,no command. And turned off instantly...my battery chrg is 75% though...

Ta-1000 rom mdl: D1C-331A-0-00CN-A01.7.1.nb0
MENA ROM MODEL: PLE-3320-0-00WW-A02.nb0

When it shows "no command" press power button and volume up, then immediately release volume up button. There is a chance you'll get into recovery and from there you can put your phone into "download" mode, so OST LA will detect it.
P.S. A bit dumb idea to do risky experiments with a daily driver.

ziaur786 said:
In my nokia 6 ta1000 , i flashed mena rom and used oreo for 3days. Now,today i wanted to roll back to my old ta1000 rom. So i flashed it .it was successful. But when the device booted it stuck in nokia ... Thn no progress. I think it bricked ... Thn i flashed again but no result... Now the device don't recognized by ost app also... Help me as soon as possibe,,as it is my daily driver .
Note: it doesn't go to fastboot either. It just shows ,no command. And turned off instantly...my battery chrg is 75% though...
Click to expand...
Click to collapse
Dear brother, i would like to suggest you one thing, I not 100% sure but it might help you, follow these steps
Please read the instructions very carefully
also make sure you have all driver and framework properly installed
1. Download the TA-1000 Firmware from here
2. Then open your OST tool.
3. When you select the firmware on OST tool, after that it will prompt you to connect your device
4. Just do not do anything, keep patience, turn off your device properly and then connect to the computer. It will directly boot into download mode.
done, rest of the steps are same as you flashed your device before.
Enjoy
hit the thanks button if you find this useful
happy flashing

Related

[GUIDE]ROOT/TWRP/MULTIROM/Cm13/RR on Locked Bootloader + Hardbrick Recovery

DO NOT FLASH HYDROGEN ROMS ON HELIUM, OR YOU GONNA HAVE A HARDBRICK.
IN CASE YOU HAVE ONE, HERE IS THE SOLUTION.
This was tested with Xiaomi Mi Max 128GB helium and localized rom from xiaomi eu.
I am not responsible for bricked devices or anything else. So at your own risk:
1. Install official MiPhone drivers
2. Download and install MiFash beta.
3. Download and unpack TWRP for miflash: 32gb or 64-128gb thanks @Abdess76.
4. Download ROM for your device, I recommend to try this one. You can install RR/CM Rom as well.
5. Run MiFlash with admin rights.
6. Turn off the phone, plug the cable to PC and halfway to the phone.
7. At the same time press Volume + and Volume - and plug in the cable.
8. Refresh MiFlash phone should show up. (If it didn't then make sure you did it right and u got drivers)
9. Navigate to your unpacked TWRP and flash it.
10. Now, boot ur phone with volume up. It's a bit slow. If it's stuck on miui logo, just release button and wait.
From here start to pay more attention:
11. TWRP can ask for password, press cancel and allow modifications by moving slider.
If you just need ROOT and your current rom, skip to the step 16. Also there is a recovery from boot in system folder. If you won't remove it, recovery may be replaced with stock one after reboot. Keep it that way if you want OTAs.
12. Format data.
13. Enable MTP and put modified zip in your phone.
14. Go to mounts and unmount system **
15. Flash your rom.
16. Flash latest supersu.
17. Reboot the phone.
In case u got NO OS message, then it means that u probably ignored step 15.
Also first boot may take like 15-20 minutes, since eu rom is deodexed.
Just to be sure, after installation mount system partition and navigate to the /system folder using TWRP's file manager and make sure it's not empty.
* In my case system didn't install because script could mount system partition since it was already mounted.
P.S. In order to update, you need to install OTA for offical rom via TWRP. Then without rebooting flash SuperSU, and finally using TWRP's file manager navigate to system folder and delete file named recovery from boot. Doing so will keep root and recovery.
Thank you so much for the guide! I will try it tonite
Waiting for boot loader is just too long..
WOW!!!! Just, wow..... I can not believe it but it worked like a charm. It took me forever to figure out my issue with the drivers, but after solving that I followed you step-by-step. And, lo and behold, it WORKED! Note for other users, Twrp took about a minute or two to finally boot up and it took me personally about 15-20 minutes before MIUI 8 finally booted. Just wait it out and you should have the amazing results that Doom Slayer has so graciously provided you
THANK YOU!!!!
I just done following your guide and it works!!
For rooting, I tried 2 times before it works. I believe you missed out a step to mount back system before flashing supersu.
So in the future, how do we dirty flash? Start from step 13?
How about clean flash? Start from step 12?
Thank you once again for this great guide!!
You saved me a lot of time waiting for Bootloader approval.
flywithme said:
I just done following your guide and it works!!
For rooting, I tried 2 times before it works. I believe you missed out a step to mount back system before flashing supersu.
So in the future, how do we dirty flash? Start from step 13?
How about clean flash? Start from step 12?
Thank you once again for this great guide!!
You saved me a lot of time waiting for Bootloader approval.
Click to expand...
Click to collapse
Yeah, dirty flash is you keep your data and format system and caches .
Clean flash is u format data as well.
The thing is that u have root, and ur phone is also secured. It's linked to ur Mi account, while it's locked. It's better to keep that way
Theoretically If you will ignore steps from 12 to 16. (Maybe u can ignore data formatting too)
Then you can get a ROOT and TWRP on your current rom.
And also theoretically while on miui 8 rom ,u can try to unlock bootloader without waiting.
Try this manual.
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
agreusar said:
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
Click to expand...
Click to collapse
Open it up and remove battery for a few minutes, then try again from step 6...
agreusar said:
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
Click to expand...
Click to collapse
Which rom did u flash, give the link please.
Are u sure it's for your version? It can be a broken file as well.
Does the device connects when u hold both volume buttons?
It's called emergency download mode, u can istall rom with miflasher.
There is a testpoint method also.
All u need is a pic from this post on http://4pda.ru/forum/index.php?showtopic=749580&st=700#entry51154086
U need to disconect battery, connect testpoint to battery and flash ur device with miflash.
After that let it charge, since this in your state phone consumes battery.
thanks for you answer, I flashed the MiMAXPRO EU ROM xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0.zip (sorry as a new user not allowed to post a link yet)
When I hold both volume buttons the screen is still black but MI Flasher works with COM10, after flashing a ROM or TWRP again MIFlash says "success" but the phone is still dead and won't start up even after holding power button for a long time.
I'm happy to open the phone and try the method on the russian forum, I will try tomorrow hope it will start up
agreusar said:
thanks for you answer, I flashed the MiMAXPRO EU ROM xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0.zip (sorry as a new user not allowed to post a link yet)
When I hold both volume buttons the screen is still black but MI Flasher works with COM10, after flashing a ROM or TWRP again MIFlash says "success" but the phone is still dead and won't start up even after holding power button for a long time.
I'm happy to open the phone and try the method on the russian forum, I will try tomorrow hope it will start up
Click to expand...
Click to collapse
Don't worry about your phone, the testpoint method will work for sure.
But in order to prevent this kind of situations ,we need to determine the reason how did it happen and you need to help me with that one by answering following questions:
1) You have mentioned that you had an error 1st time.
I also had error which was cache related, and it's OK because that partition was just formatted. You tried to flash again... but did you unmount your system partition for second time?
2) What's the capacity of your internal storage?
3) Did you use internal or external storage? If external then I need the model and the file system that have been used on that storage.
Doom Slayer said:
Don't worry about your phone, the testpoint method will work for sure.
But in order to prevent this kind of situations ,we need to determine the reason how did it happen and you need to help me with that one by answering following questions:
1) You have mentioned that you had an error 1st time.
I also had error which was cache related, and it's OK because that partition was just formatted. You tried to flash again... but did you unmount your system partition for second time?
2) What's the capacity of your internal storage?
3) Did you use internal or external storage? If external then I need the model and the file system that have been used on that storage.
Click to expand...
Click to collapse
Hello,
I managed to recover the phone, I installed a fresh windows 7 on another PC with only MI Flash Beta installed, device appeared as "Qualcomm HS-USB QDLoader 9008" as usual and I flashed the china ROM. Not sure why it wouldn't start previously after flashing, maybe issue with drivers.
1) unfortunately I don;t remember the syntax of the error, it was after a few seconds of flashing but the process seemed interrupted, I even googled it but my browser history has been purged.
2) 64GB (Helium)
3)I used internal storage, copied the zip on the phone using MTP.
Might try to go through the process again this weekend.
agreusar said:
Hello,
I managed to recover the phone, I installed a fresh windows 7 on another PC with only MI Flash Beta installed, device appeared as "Qualcomm HS-USB QDLoader 9008" as usual and I flashed the china ROM. Not sure why it wouldn't start previously after flashing, maybe issue with drivers.
1) unfortunately I don;t remember the syntax of the error, it was after a few seconds of flashing but the process seemed interrupted, I even googled it but my browser history has been purged.
2) 64GB (Helium)
3)I used internal storage, copied the zip on the phone using MTP.
Might try to go through the process again this weekend.
Click to expand...
Click to collapse
Well, I guess system was mounted and it gived u the error,but formatted it.
hi to all of you. I am very interested by this thread. Here is the story. I received my brand new mi max helium this week but it was the chinese rom. I am in France and my country did not appear in the settings. So I wanted to flash a global rom. I plugged it to my pc in recovery mode and a window appeared said that there is an update. I clicked ok and after a while I got stuck in the mi logo bootloop.
Then from then I tried everything possible from several solutions here, but nothing worked. What I got is the mi logo without bootloop, but nothing more.
I get the message that the bootloader is locked, but I can't get it unlock if it is in this state.
What I can reach is the recovery mode and the fastboot mode. But nothing else worked, flash or anything.
That is why I am interested to flash a recovery, in order to flash a clean rom, etc..
I did what you, Doom Slayer, explains, but I could not get a twrp flash. It ends with "receiving hello packet" in mi flash, and every thing stopped.
If I cannnot install any recovery, I cannot flash a rom.
So please if you have any suggestion, it would be helpful. Thanks a lot.
alain belay said:
hi to all of you. I am very interested by this thread. Here is the story. I received my brand new mi max helium this week but it was the chinese rom. I am in France and my country did not appear in the settings. So I wanted to flash a global rom. I plugged it to my pc in recovery mode and a window appeared said that there is an update. I clicked ok and after a while I got stuck in the mi logo bootloop.
Then from then I tried everything possible from several solutions here, but nothing worked. What I got is the mi logo without bootloop, but nothing more.
I get the message that the bootloader is locked, but I can't get it unlock if it is in this state.
What I can reach is the recovery mode and the fastboot mode. But nothing else worked, flash or anything.
That is why I am interested to flash a recovery, in order to flash a clean rom, etc..
I did what you, Doom Slayer, explains, but I could not get a twrp flash. It ends with "receiving hello packet" in mi flash, and every thing stopped.
If I cannnot install any recovery, I cannot flash a rom.
So please if you have any suggestion, it would be helpful. Thanks a lot.
Click to expand...
Click to collapse
Did you disable drivers signature?
Also some people have a better luck on windows 7, u can try a virtual machine.
If you can enter EDL mode, then you should be fine.
Unless Chinese already disabled it in a new update.
I would blame drivers. Make sure u got them correctly.
Updated tutorial.
Uploaded TWRP for helium, so you don't need to edit updater script anymore, since script will get correct model.
Now you can try to get root on your current rom and unlock bootloader without Xiaomi's confirmation.
People having helium with unlocked bootloader may also have problems installing roms from xiaomi eu, if they have TWRP from hydrogen.
You may update using my recovery.img from archive using fastboot, or TWRP(will also work for locked bootloader).
Doom Slayer said:
Did you disable drivers signature?
Also some people have a better luck on windows 7, u can try a virtual machine.
If you can enter EDL mode, then you should be fine.
Unless Chinese already disabled it in a new update.
I would blame drivers. Make sure u got them correctly.
Click to expand...
Click to collapse
hi Doom. Thank you for reply. But what do you mean by " disable drivers signature". I did not do anything but install the drivers and when I am on what I think is EDL mode(screen isi black) the driver is recognized as Qualcomm HS-USB QDLoader 9008(COM20).
Anyway, I will give another try and let you know. Thank you again.
---------- Post added at 09:14 AM ---------- Previous post was at 08:22 AM ----------
I followed your guide and I could get the twrp installed. So I tried to install rom(following your link). It said rebooting in 5 seconds, and then nothing. The screen is black, no power anymore, no logo, no vibes, and no life at all.
I cannot get any more reaction from it. I plugged it to my pc, but nothing is connected. I was so happy with twrp working... Any idea?...
one more information I don't know if it can help, when I flashed first, I tried the "xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0" and a message said "failed. This rom is for helium and this is hydrogen phone". Which is strange because mine is helium(4GB/128GB).
Then I tried with the "xiaomi.eu_multi_MIMAX_V7.5.6.0.MBCCNDE_v7-6.0" rom, and everything got ok, last message "success. The phone will reboot in 5 seconds", and from then, dead all over...
alain belay said:
one more information I don't know if it can help, when I flashed first, I tried the "xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0" and a message said "failed. This rom is for helium and this is hydrogen phone". Which is strange because mine is helium(4GB/128GB).
Then I tried with the "xiaomi.eu_multi_MIMAX_V7.5.6.0.MBCCNDE_v7-6.0" rom, and everything got ok, last message "success. The phone will reboot in 5 seconds", and from then, dead all over...
Click to expand...
Click to collapse
Looks like you installed hydrogen TWRP and that caused all your problems.
I've been very careful to install the helium twrp from this thread...

Strange brick on Axon 7 A2017G after rollback to MM

Dear Friends,
I had this problem...
Buy this phone with MM6.0.1 and after a week decide to update to N 7 with OTA. Process was clear and fast...
after another week and affording a lot of issues with clock, bluetooth, etc.. i decide to rollback to MM6.0.1
There's the problem... phone boots and do the presentation of images like it wants to enter, but stucks in the image of AXON...
Only can enter in a strange recovery, without shelters... only START, Restart Bootloader, Recovery mode(that does nothing), Power OFF, and Boot to FFBM
Anyone has a minimal idea that was happen? Don't want to wait an eternity to send back to china and wait to reapir, if anyone have a solution.
Images are an example of issue, you can see but no can do anything in the screens.
Thanks for your kindly cooperation folks!!!
tanoobx said:
Dear Friends,
I had this problem...
Buy this phone with MM6.0.1 and after a week decide to update to N 7 with OTA. Process was clear and fast...
after another week and affording a lot of issues with clock, bluetooth, etc.. i decide to rollback to MM6.0.1
There's the problem... phone boots and do the presentation of images like it wants to enter, but stucks in the image of AXON...
Only can enter in a strange recovery, without shelters... only START, Restart Bootloader, Recovery mode(that does nothing), Power OFF, and Boot to FFBM
Anyone has a minimal idea that was happen? Don't want to wait an eternity to send back to china and wait to reapir, if anyone have a solution.
Images are an example of issue, you can see but no can do anything in the screens.
Thanks for your kindly cooperation folks!!!
Click to expand...
Click to collapse
Version of MM is important! Was it on V1.0.0B10 or V1.0.0B11? If older, it was too old to go N and ZTE say do updates via SD card, not OTA. There are tools to recover it but I'm not up on them as mine is stock and carefully updated to B09 N so I will leave it to others well informed to explain recovery methods.
That's fastboot mode. No idea why it is booting to that screen. I assume you are locked so miflash is probably the easiest way to fix.
lafester said:
That's fastboot mode. No idea why it is booting to that screen. I assume you are locked so miflash is probably the easiest way to fix.
Click to expand...
Click to collapse
I try Miflash, but phone isn't recognized by PC or Miflash. I only see android with a yellow triangle. i'm searching for one idea or driver to make recognize my phone to PC and reflash all... do you have an idea?
RobboW said:
Version of MM is important! Was it on V1.0.0B10 or V1.0.0B11? If older, it was too old to go N and ZTE say do updates via SD card, not OTA. There are tools to recover it but I'm not up on them as mine is stock and carefully updated to B09 N so I will leave it to others well informed to explain recovery methods.
Click to expand...
Click to collapse
Mine was in V1.0.0B09
Find a way to unlock bootloader... connect phone to pc, and if not recognized open cmd and write: "fastboot oem unlock" this unlocks the twrp i had installed... thanks a lot to gandou63 from france... now i proceed to flash a rom, and after i told you how is going... thanks for the advices!!!
tanoobx said:
I try Miflash, but phone isn't recognized by PC or Miflash. I only see android with a yellow triangle. i'm searching for one idea or driver to make recognize my phone to PC and reflash all... do you have an idea?
Click to expand...
Click to collapse
Lol no, you have to put your phone in EDL mode. But maybe you can get to the recovery and flash another version first.
If you have an SD card, do this:
Turn the phone off, wait around 5 seconds and hold Volume Up and Power. It should boot into the recovery. You need to have the SD card inserted, with the B11 rollback package. select Install through sd card and install it.
If you don't have one, you need to get in EDL mode.
Connect the USB to the PC but not the phone.
Turn the phone off, wait around 5 seconds, then hold Volume Up and Volume Down (NOT power) and insert the USB cable on the phone. After that go to Device Manager and check that the phone appears (as Qualcomm HS-USB QDLoader 9008, in 'Ports (COM & LPT)'). Download an A2017G B11 FULL EDL package and flash it with miflash.
P.S. Is it an A2017G? If it is not, just use the packages from the model you have. I just read that 'send back to china' bit.
tanoobx said:
Mine was in V1.0.0B09
Click to expand...
Click to collapse
Here's the support page on the ZTE Australia website, I read this before doing any updates and have had a trouble free run to B09 N. Mine was on older firmware than B10MM when I purchased too.
http://www.ztemobiles.com.au/feature_AXON7.htm
The information will apply to any A2017G on older firmware. The latest shipments are now coming with B11 MM so they can go straight to B09 N.
I unboxed mine, turned on with B10MM update on an SD and updated it, then updated to B04. Didn't use it before it was on Nougat.
Choose an username... said:
Lol no, you have to put your phone in EDL mode. But maybe you can get to the recovery and flash another version first.
If you have an SD card, do this:
Turn the phone off, wait around 5 seconds and hold Volume Up and Power. It should boot into the recovery. You need to have the SD card inserted, with the B11 rollback package. select Install through sd card and install it.
If you don't have one, you need to get in EDL mode.
Connect the USB to the PC but not the phone.
Turn the phone off, wait around 5 seconds, then hold Volume Up and Volume Down (NOT power) and insert the USB cable on the phone. After that go to Device Manager and check that the phone appears (as Qualcomm HS-USB QDLoader 9008, in 'Ports (COM & LPT)'). Download an A2017G B11 FULL EDL package and flash it with miflash.
P.S. Is it an A2017G? If it is not, just use the packages from the model you have. I just read that 'send back to china' bit.
Click to expand...
Click to collapse
Thanks a lot for your kindly advice. I'll try...
Had to thanks all you guys for your advices... i unbricked my phone and all goes very well... Hugs for alls Guys!!!

Lenovo K8 Note (XT1902-3) - Fix Dead/Hard Bricked Phone,Downgrade to Nougat from Oreo

Revive Dead/Hard Bricked/Dead after Flash/LED doesn't light up the phone - K8 Note (XT1902-3)​
If you tried to downgrade from Oreo to Nougat and your device is hard-bricked. Don't worry, follow the procedure below...
1. If your device is fully hard bricked and doesn't boot up by pressing the power button, and also the white LED light doesn't light up while u connect the charger/power on the USB to the PC. Try pressing all the 3 buttons, Volume Up+Volume Down+Power Button for about 25-30 seconds and connect your phone through USB to SP Flash Tool (install all drivers before as said in step 3) and see whether it detects your phone (If it detects, go to step 3). If this also didn't work, don't get panic - follow step 2 (Dismantling your device - the only way to recover. But be cautious while doing it, use proper tools).
2. Remove your phone back cover carefully and disconnect the battery connector as shown in the video
. Use proper tools and a screwdriver. Connect the charger and see now, the LED light will blink surely (If it doesn't blink now also, then it's a hardware problem, you should go to the service centre only).
3. If the LED light blinks properly, then go to SP Flash Tool (download the latest version here - https://androidmtk.com/smart-phone-flash-tool), and in Options->Option go to Download and check USB Checksum and Storage Checksum. Then choose the option Download Only in the drop-down list. (Dont Forget to install all Drivers before - MTK Drivers and Lenovo USB Driver, links below)
MTK (USB DA COM,Preloader USB VCOM,USB Port,USB VCOM) Drivers : https://spflashtool.com/download/Driver_Auto_Installer_v1.1236.00.zip
Lenovo USB Driver : https://lenovousbdriver.com/download/lenovo-driver-v1-1-33
(CAUTION : Don't select Format all+Download because if you mistakenly chose Format All+Download option it will delete all your IMEI no, Device Serial no, WIFI MAC address, and Bluetooth Address. But don't worry you can retrieve it through this method : https://forum.hovatek.com/thread-12328.html or
. Make sure you know all your IMEI no, and device serial no {You can get that from your device box, there will be a label in it}.
4. In the Scatter-Loading file click Choose and load MT6797_Android_scatter.txt under the extracted Oreo Rom (whichever version you prefer)
COUNTRY: GLOBAL​
Oreo Stock Rom OMB 27.43-20 -> https://drive.google.com/file/d/18iZb3sumLUEBNNAYDfRVa3t8fJZVCXgg/view (MANNING OMB 27.43-20.7z ~ 1.40 GB)
Oreo Updated Rom OMB 27.43-45 -> https://drive.google.com/file/d/10QRAgh9Nap30zFSKVkANNkQkifWYrkwC/view (MANNING OMB-27-43-45.7z ~ 1.50 GB)
COUNTRY: USA​
Oreo Updated Rom OMB 27.43-67 -> https://mirrors.lolinet.com/firmwar..._OMB27.43-67_subsidy-UNLOCKED_CFC_SVC.xml.zip (MANNING_RETAIL_OMB27.43-67_subsidy-UNLOCKED_CFC_SVC.xml.zip ~ 1.79 GB)
Oreo Updated Rom OMB 27.43-70 -> https://mirrors.lolinet.com/firmwar..._OMB27.43-70_subsidy-UNLOCKED_CFC_SVC.xml.zip (MANNING_RETAIL_OMB27.43-70_subsidy-UNLOCKED_CFC_SVC.xml.zip ~ 1.79 GB)
Wait for some time until it loads........
5. Now click on Download Button. Then switch off your phone and keep pressing the Volume UP button while connecting your phone to the PC through USB.
6. Now your phone will be flashed successfully and you will get a message Download OK. Close that and remove your USB and Power On your phone. Your phone will boot in Oreo, and you have unbricked your phone!!! Enjoy!!!
Downgrade to Nougat from Oreo - K8 Note​
1. First Unlock your bootloader through the following steps:
(Before this take a backup of all your files, apps, and data because it will factory reset your mobile)
{Unroot your phone if you're rooted, also Uninstall any modules or Xposed or rooted apps if installed}
i) Go to Settings->About Phone and Tap on Build number for about 7 times, this will enable the Developer Options. Now go to Settings->Developer Options, switch ON it, and enable OEM unlocking & USB debugging.
ii) Next, Go to Fastboot mode manually. Switch off your phone. Press Volume UP+Power Button at the same time. While the phone vibrates release the power key and hold the Volume up button. You will see three options. Select fastboot option using the Volume UP key (for scrolling) and select it using Volume Down Key (for selecting).
iii) Extract minimal_adb_fastboot zip file on your PC -> https://androidfilehost.com/?fid=457095661767103465, and press Shift+Right Click inside the extracted folder and give open the command window here. Then Connect the mobile to your PC using a USB.
iv) Then type : fastboot oem unlock {Note: This will wipe all your phone data & make it as new, so take a backup of all before doing it} (Then press the Volume Up key in your mobile after it prompts)
vi) Type : fastboot reboot (It will boot up your phone normally)
vii) That's it now you have unlocked your bootloader successfully
2. Download Nougat Rom : (whichever version you prefer)
Updated Final Version Nougat ROM NMB26.54-94 ->
https://mega.nz/#!lIYSAaSb!q1S24g11wHxH3j0Zjl9FD8jO7s4jPFwInseORqYg9Xs (MANNING-54_94 .7z ~ 1.61 GB) COUNTRY : GLOBAL
https://mirrors.lolinet.com/firmwar...MB26.54-94_105_release-keys_retail_US_SVC.zip (manning_retail_user_7.1.1_NMB26.54-94_105_release-keys_retail_US_SVC.zip ~ 1.69 GB) COUNTRY : USA
Updated Nougat ROM NMB26.54-74 ->
https://androidfilehost.com/?fid=962021903579496260 (Lenovo_K8_Note_XT1902-3_(NMB26.54-74_75)_by_(FirmwareOS.com).zip ~ 2.09 GB) COUNTRY: GLOBAL
Nougat Stock Rom NMB26.54-35 -> (whichever link you prefer)
http://www.mediafire.com/file/7l8n312jhec1hmy/Lenovo_K8_Note_XT1902-3_MT6797_26092017_7.1.1.zip (Lenovo_K8_Note_XT1902-3_MT6797_26092017_7.1.1.zip ~ 2.10 GB) COUNTRY: GLOBAL
https://mega.nz/#F!EXphwJLb!Us6WQxEOAonVCrmLomxjHw (fastboot_manning_retail_user_7.1.1_NMB26.54-35-2_2_release-keys_retail_US.zip ~ 2.06 GB) COUNTRY: USA
https://mirrors.lolinet.com/firmwar...NMB26.54-35_35_release-keys_retail_US_SVC.zip (manning_retail_user_7.1.1_NMB26.54-35_35_release-keys_retail_US_SVC.zip ~ 2.01 GB) COUNTRY : USA
3. Extract the downloaded zip file and Go to Fastboot mode manually as mentioned before. (Switch off, Press Volume UP+Power button at same time. Release Power button while phone vibrates. Then Choose Fastboot option using Volume Up Key and select it using Volume Down Key)
4. Connect the USB Cable from phone to PC and Double click the flashall.bat file inside the downloaded zip. {Rename flashall.txt in the attachment to flashall.bat, if you didn't find it from the downloaded zip}. This will flash the Nougat Rom fully on your device. Sit Back for some time, and relax.
5. It will boot automatically and go to Nougat Rom. If you got some error on it or force stop apps or bootloop don't worry.
Switch off your phone by long pressing power key
6. Go to Recovery Mode manually (Switch off, Press Volume UP+Power button at same time. Release Power button while phone vibrates. Then Choose Recovery option using Volume Up Key and select it using Volume Down Key. Now you will get a Android dead kinda symbol. Press Volume UP + Volume Down +Power button, you will see Recovery Mode). Choose Wipe Data/Factory Reset and Yes--delete all user data. See this video if you have doubts how to factory reset using recovery mode :
7. Then select Restart System now in Recovery Mode (Volume Up and Volume Down to Select between options and Power Button to OK). Viola...!!! Your system will reboot and your'e on Nougat Rom...!!!
{Note : After downgraded to Nougat, you won't get OTA update to Oreo. But you can get all the OTA updates of Nougat. Main thing: Don't use "fastboot oem lock" in downgraded Nougat Rom it may brick your device. Because while you lock the oem in downgraded version, the system updates will look for Oreo Rom so it wont boot as you already downgraded. If it's bricked try flashing Oreo Stock Rom using spflash tool. So try keep the "device unlocked. Orange Status......" text that comes while you boot up, always in downgraded Nougat Rom}
Follow the procedure correctly so you can retrieve your K8 Note, don't blame me if you totally damaged/bricked your device.
Hit Like and Press Thanks...!!!!
If you have any doubts you can mail me at [email protected]
Bro... thanks a lot. I was able to downgrade my lenovo k8 note to Nougat from Oreo. Oreo update sucked lot of battery, had heating issues and sometimes hung during power off/restart. I decided to downgrade and this post was very helpful.
Flashing succeeded but still phone dead after several failed attempts, flashed nougat back, still no use... again flashed oreo and boom....... phone booted into oreo. thanks for the great help.
ROM links are not working
Stock Nougat Rom links are not working.. can you please check
Feel Awesome that you Downgraded K8 Note from Oreo to Nougat
sudhans said:
Bro... thanks a lot. I was able to downgrade my lenovo k8 note to Nougat from Oreo. Oreo update sucked lot of battery, had heating issues and sometimes hung during power off/restart. I decided to downgrade and this post was very helpful.
Click to expand...
Click to collapse
I am glad that my blog helped u in downgrading...
Felt Awesome that you Downgraded K8 Note from Oreo to Nougat
sudhans said:
Bro... thanks a lot. I was able to downgrade my lenovo k8 note to Nougat from Oreo. Oreo update sucked lot of battery, had heating issues and sometimes hung during power off/restart. I decided to downgrade and this post was very helpful.
Click to expand...
Click to collapse
I am glad that my blog helped u in downgrading...
Updated, check it.... Try Mediafire Link
bhellsun said:
Stock Nougat Rom links are not working.. can you please check
Click to expand...
Click to collapse
Nougat Stock Rom (NMB26.54-35) -> http://www.mediafire.com/file/7l8n312jhec1hmy/Lenovo_K8_Note_XT1902-3_MT6797_26092017_7.1.1.zip
Oreo Stock Rom (OMB 27.43-20) -> https://drive.google.com/file/d/18iZb3sumLUEBNNAYDfRVa3t8fJZVCXgg/view
Try the procedure properly so that you can downgrade...
Manivel2007 said:
Flashing succeeded but still phone dead after several failed attempts, flashed nougat back, still no use... again flashed oreo and boom....... phone booted into oreo. thanks for the great help.
Click to expand...
Click to collapse
If u have installed twrp in oreo get rid of that and go for stock oreo recovery, if u have rooted already on oreo means unroot your mob, uninstall xposed/magisk manager if it's there. Then start the process with unlocked bootloader, go to fastboot mode and run flashall.bat inside the Stock Nougat Rom zip. After the process finished successfully the device will boot automatically. You may get some errors or not, no probs about it, go to recovery mode manually and factory reset your mobile. Restart the mob. This will surely work. Go for it...
Anyways, I feel good that you retrieved your phone back through Oreo Rom. :good:
Thanks, man Much appreciate. I have followed your instruction and I succeeded. XDA always rocks.
100 percent working
working to kmay k8 note thank you so much for helpng each other
After flashing, Have tried to install the Nougat ROM, But getting below error
Flashing Options:
- flash userdata: 0
- erase userdata: 0
- erase cache: 0
Waiting for fastboot enumeration...
Not found any devices connected. Please check and try again.
i need 8.0 43-45 any upload in eat
please gavi a ink on lenovo k8 note latest update
appreciated your work
hey, I recently read your thread on the same topic of lenovo k8 note.
I downgraded my phone from oreo update to naugat directly through flash tool.
it got dead and after multiple flashings it didn't work.
finally your thread help me out to revive my phone, but it is just showing me the logo.
it has stucked on boot loop.
what to do?
help me out.
I feel good that you flashed your K8 Note successfully
Dj ps said:
Thanks, man Much appreciate. I have followed your instruction and I succeeded. XDA always rocks.
Click to expand...
Click to collapse
I Feel Good that you Succeeded following my steps
Don't downgrade from Oreo to Nougat of K8 Note through spflash tool
akki8800 said:
hey, I recently read your thread on the same topic of lenovo k8 note.
I downgraded my phone from oreo update to naugat directly through flash tool.
it got dead and after multiple flashings it didn't work.
finally your thread help me out to revive my phone, but it is just showing me the logo.
it has stucked on boot loop.
what to do?
help me out.
Click to expand...
Click to collapse
Try factory resetting using Recovery mode, if u can go through it. Else flash Oreo Rom through latest version of spflash tool. Only Downgrade using fastboot mode....
Given Oreo Updated ROM for K8 Note links, check it...
kulerman123 said:
please gavi a ink on lenovo k8 note latest update
Click to expand...
Click to collapse
OMB 27.43-45 links updated, check it...
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
See whether your phone is properly connected to PC and the device is showing or not
mymilu2018 said:
After flashing, Have tried to install the Nougat ROM, But getting below error
Flashing Options:
- flash userdata: 0
- erase userdata: 0
- erase cache: 0
Waiting for fastboot enumeration...
Not found any devices connected. Please check and try again.
Click to expand...
Click to collapse
Check up your drivers and the ROM file whether its corrupted....
Thanks for your positive review....
kulerman123 said:
working to kmay k8 note thank you so much for helpng each other
Click to expand...
Click to collapse
Thanks and I am always glad to help peoples.... :highfive:
I tried many things... i tried to use recovery but after showing lenovo logo for about a minute... it either gets off or restart. I m using latest sp flash tool.
Drivers are updated and.
What should i do....
I have given it to service center as well even they cant help it out..
Saying motherboard has issues...
:crying::crying:
Can Lenovo k8 note Android p unofficial ROM.
Hi, xda developers is there any way that Lenovo k8 note can get Android p ROM. If yes please reply?

Stuck in rescue mode after tried flashing stock firmware

Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.

Might have bricked my Mi9T (non-pro) - Bootloop, XiaoMiTool V2

**EDIT**: Had to send the phone back as the bootloader was locked and nothing was flashing. I believe they EDL flashed it and all is good now. Unlocked the bootloader on the new one just in case this happens again, I will be able to fix
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BACKSTORY:
Okay, so I recently updated to MiUI 12 and it wasn't great. My apps were crashing all the time and the general stability was not good. (this was around a week ago)
Then earlier today, my device just went into the boot screen (the colourful MiUI one) and stayed there for over 30 mins.
I forcefully restarted my phone using the volume buttons and it would go into the first "Mi powered by android" screen and then back into the colourful MiUI screen.
Then it would stay in the MiUI screen for a minute or so, and then restart itself, continually repeating the process.
At this stage, I had no custom recovery, had not tried to tinker with the phone (other than disabling some default apps through FastbootTools), and everything was fine until MiUI 12 came.
WHAT I DID:
I was able to access the default XiaoMi recovery (3.0?) and tried to wipe the data and restart, but nothing would change.
I tried to use the MiPC Suite after selecting in recovery, but it would recognise my device, even after updating to latest version.
I tried to use FastBootTools, but that would also not recognise my device.
I tried to use XiaoMiTool V2 (by Francesco Tescari), and that did recognise my device. I selected "my device is bricked" option and it did its thing, downloading and trying to sideload something. And then on the device, it got stuck at 4.99% with a message "You won't be able to turn on your device if you try to reboot it", and on the XiaoMiTool, the progress was at around 400% and said -70 seconds remaining, and around 40000MB / 3000 MB or something along those lines. Basically, **** was ****ed.
So I just let it sit there for a bit and then the XiaoMiTool V2 gave and error, "miui sideload failed adb execution exception adb sideload exited with status 1"
I had 3 options,
"Retry step"
"Go back to previous step"
"Cancel and abort"
I tried to search what the error was, but all of the results came from years ago, for different devices. So I clicked "Cancel and abort", only for the device to remain unchanged (4.99%, You won't be able to turn on your device if you try to reboot it), while the XiaoMiTool V2 went back to the start screen.
So I tried it again, the "my device is bricked option", and went through the same steps, and now it is stuck at "Pushing file to the device via ADB, ..., Starting MIUI sideload procedure".
Now I am stuck. My phone screen just says
"4.99%, You won't be able to turn on your device if you try to reboot it"
and my XiaoMiTool is stuck on the beginning sideload procedure.
Closing
If you managed to read this far, thanks, even if you don't have a solution. I appreciate anything that could help with this situation.
U could use the official tool by xiaomi and install your stock miui 12 rom, it's called miflash
Idk about downgrade if u wanted to flash miui 11 i heard there is some problems related to that so, always try official xiaomi tools first before trying other stuff
Ps : if it doesn't detect ur device in miflash there is a button called update or install driver I don't remember exactly press it and u should be fine
Badis st said:
U could use the official tool by xiaomi and install your stock miui 12 rom, it's called miflash
Idk about downgrade if u wanted to flash miui 11 i heard there is some problems related to that so, always try official xiaomi tools first before trying other stuff
Ps : if it doesn't detect ur device in miflash there is a button called update or install driver I don't remember exactly press it and u should be fine
Click to expand...
Click to collapse
I tried to install the drivers, and it says it was successful, but it still does not recognise my device in fastboot mode. However, it does seem to recognise my device in the default recovery, when selecting the "Connect with MiAssistant", which prompts to use the Mi PC Suite.
Any other ways to help it recognise in fastboot mode?
coolboy328509 said:
I tried to install the drivers, and it says it was successful, but it still does not recognise my device in fastboot mode. However, it does seem to recognise my device in the default recovery, when selecting the "Connect with MiAssistant", which prompts to use the Mi PC Suite.
Any other ways to help it recognise in fastboot mode?
Click to expand...
Click to collapse
Try another computer and another USB port...
The solution will benunder fastboot. You have to unclock your bootloader and flash a custom twrp or flash a stock rom using miflash
Hi, can you give any updates? I think i'm on the same boat. I have a Xiaomi Redmi Note 9 pro
EdoDT99 said:
Hi, can you give any updates? I think i'm on the same boat. I have a Xiaomi Redmi Note 9 pro
Click to expand...
Click to collapse
this is totally the wrong thread for ur device

Categories

Resources