Related
Hi my friends.
this is my story :
my phone is Redmi note 3 pro (qualqomm)
I got permissions for unlocking a week ago.
then i tried xiaomi website unlock method but it stopped at 50% and gave me couldn't verify device (different account) error.
my rom is global (MIUI 8) . then i tried to flash dev rom with updater app but it gave me couldn't verify update package error. i cleared updater data and tried again but same error.
in next step i tried mi pc suite to flash but no success.
then i used fastboot mode and mi flash and i got locked bootloader error.
then i used EDL mode to flash but in mi flash i got hello package error. (object reference not set to an instance of an object)
i completely confused . i tried all methods and read many fix like login in i.mi.com and other method that people fixed their problem but all of them not fix mine.
i read some threads about flashing twrp and root without unlocking bootloader but all of them need flashing dev rom and i can't flash.
can anyone help me?
x23are said:
Hi my friends.
this is my story :
my phone is Redmi note 3 pro (qualqomm)
I got permissions for unlocking a week ago.
then i tried xiaomi website unlock method but it stopped at 50% and gave me couldn't verify device (different account) error.
my rom is global (MIUI 8) . then i tried to flash dev rom with updater app but it gave me couldn't verify update package error. i cleared updater data and tried again but same error.
in next step i tried mi pc suite to flash but no success.
then i used fastboot mode and mi flash and i got locked bootloader error.
then i used EDL mode to flash but in mi flash i got hello package error. (object reference not set to an instance of an object)
i completely confused . i tried all methods and read many fix like login in i.mi.com and other method that people fixed their problem but all of them not fix mine.
i read some threads about flashing twrp and root without unlocking bootloader but all of them need flashing dev rom and i can't flash.
can anyone help me?
Click to expand...
Click to collapse
I just recently went through most of what you have gone through... Be patient though... It seems that the unlocking of bootloader even after you getting permission, takes atleast 2-3 weeks more.
- You can flash the miui global dev rom, you may download it from the miui forums... Here is the link for the fastboot rom http://en.miui.com/a-234.html.
- To flash the dev rom, you need to ensure you put your phone into fastboot, ensure all the fastboot drivers are installed on your computer
- Also, you need to ensure that you download the GLOBAL/DEV FASTBOOT ROM(this is different than the regular zip package) that you download.
- Then you can follow the instructions to install the ROM using miflash tool
- If the ROM installation is a success, then you just need to wait patiently atleast for 15-20 days from the time you got unlock permission sms from MI
- Then try running the flash unlock tool, it should get unlocked.
- Now flashing TWRP might be tricky, I was able to flash the official TWRP, but had issues where the internal memory wasn't getting mounted, because you keep getting asked for decryption password in TWRP to mount the data, no matter what you enter, it might not work
- After trying many TWRP types, the one that worked was "zcx twrp"
- Once you flash that, you should be able to flash any custom or miui roms you need :good:
GENiU5 said:
I just recently went through most of what you have gone through... Be patient though... It seems that the unlocking of bootloader even after you getting permission, takes atleast 2-3 weeks more.
- You can flash the miui global dev rom, you may download it from the miui forums... Here is the link for the fastboot rom http://en.miui.com/a-234.html.
- To flash the dev rom, you need to ensure you put your phone into fastboot, ensure all the fastboot drivers are installed on your computer
- Also, you need to ensure that you download the GLOBAL/DEV FASTBOOT ROM(this is different than the regular zip package) that you download.
- Then you can follow the instructions to install the ROM using miflash tool
- If the ROM installation is a success, then you just need to wait patiently atleast for 15-20 days from the time you got unlock permission sms from MI
- Then try running the flash unlock tool, it should get unlocked.
- Now flashing TWRP might be tricky, I was able to flash the official TWRP, but had issues where the internal memory wasn't getting mounted, because you keep getting asked for decryption password in TWRP to mount the data, no matter what you enter, it might not work
- After trying many TWRP types, the one that worked was "zcx twrp"
- Once you flash that, you should be able to flash any custom or miui roms you need :good:
Click to expand...
Click to collapse
tnx for reply but my problem is i cant flash.
my bootloader is locked and i cant flash fastboot rom.
therefor i must use edl mode or updater app but both of them don't work as a said in first post.
You don't need an unlocked BL to flash official fast boot miui ROMs
GENiU5 said:
You don't need an unlocked BL to flash official fast boot miui ROMs
Click to expand...
Click to collapse
mi flash show me : bootloader unlock in flashing process
x23are said:
mi flash show me : bootloader unlock in flashing process
Click to expand...
Click to collapse
You may try the steps on this link http://en.miui.com/thread-235865-1-1.html
Skip the EDL thing and go directly to the part where they explain how to use the miflash tool to flash a fastboot ROM
I should have asked this first... what's the state of your phone right now? Does it boot, stuck on boot loop, or are you able to boot into some ROM.
maybe u have a vendors rom, flash the fastboot rom using edl
finally a downloaded adb 1.4.3 and installed it and i flashed dev rom in EDL mode.
but now i have some questions:
can i change kernel with locked bootloader?
if i change kernel does fingerprint work?
You just dont have proper drivers installed im 100% sure, else it would go via edl
Hehe was right������
And why dont you ask for official unlock approval? Its approved in less than a day, anyone saying otherwise have old news
Or you can always use a method in this forum...
Hi Friends i flashed miui firmware by stinx when i was on lineage rom to update the rom without any error.Then after flashed no mi logo no recovery no fastboot tooo Anyone pls tell solution for this to recover my device back
The Game 370 said:
Hi Friends i flashed miui firmware by stinx when i was on lineage rom to update the rom without any error.Then after flashed no mi logo no recovery no fastboot tooo Anyone pls tell solution for this to recover my device back
Click to expand...
Click to collapse
Are you able to see led blinking as red when you connect it to PC?
gulshanstrider said:
Are you able to see led blinking as red when you connect it to PC?
Click to expand...
Click to collapse
Yes but pc is not recognising
The Game 370 said:
Yes but pc is not recognising
Click to expand...
Click to collapse
Go to device manager and tell which Port it Is connected on ?
900E or 9008
gulshanstrider said:
Go to device manager and tell which Port it Is connected on ?
900E or 9008
Click to expand...
Click to collapse
Hi its not showing anything sorry if i am wrong
Do you have MiFlash tool ?
gulshanstrider said:
Do you have MiFlash tool ?
Click to expand...
Click to collapse
YES
The Game 370 said:
YES
Click to expand...
Click to collapse
Check if it is getting listed there.
If not try test point method
gulshanstrider said:
Check if it is getting listed there.
If not try test point method
Click to expand...
Click to collapse
No its not showing my device
The Game 370 said:
No its not showing my device
Click to expand...
Click to collapse
what is the current state of yr phone?
tell in details.
is it charging?
is mi logo appears when power button is pressed?
did u try pressing "vol down+power button"?
and what exactly did u do before the phone was dead?
any error occured during flashing?
Same with me
Try accessing fastboot, then reunlock your bootloader
Simoom Sadik said:
what is the current state of yr phone?
tell in details.
is it charging?
is mi logo appears when power button is pressed?
did u try pressing "vol down+power button"?
and what exactly did u do before the phone was dead?
any error occured during flashing?
Click to expand...
Click to collapse
No mi logo,no fastboot,no recovewry nd not charging too
Only red light blinking when connected to usb
I was on lineage rom nd tried to update that rom nd flashed miui 7.5.4 firmware by the stinx to get rid of error while flashing newer build of lineage rom
auliamaster74 said:
Same with me
Try accessing fastboot, then reunlock your bootloader
Click to expand...
Click to collapse
I am unable to access fastboot
The Game 370 said:
I am unable to access fastboot
Click to expand...
Click to collapse
try pressing power + vol down untill it boots into fastboot
at first, I thought I can't access fastboot, turns out I could
try it
auliamaster74 said:
try pressing power + vol down untill it boots into fastboot
at first, I thought I can't access fastboot, turns out I could
try it
Click to expand...
Click to collapse
Thanks i tried deep flash cable method but it didnt worked nd tried test point method Finally it worked
Also Fixed,but FW Flash is a problem
HI,
I just wanted to comment on this, in the hope that some more experienced member, or even TheStrix would see it.
I've had the exact same problem over the last few days, but have been able to fix it each time by reflashing recovery from miFlash in edl mode;
Flashing the firmware from TheStrix (Latest, kenzo) without fail, bricks the Redmi Note 3, only being able to get to FastBoot. I'm able to switch to EDL on the PC with that batch file that's floating about, and flash recovery through miflash. I've been on LineageOS14 for the past few weeks, but my phones been barely usable with lag. Switched to AOSPX the other day by first flashing the FW;
1. Reboot to recovery
2. Backups
3. Wipe everything except for sd
4. Flash FW
5. Flash AOSPEx
6. Flash Gapps
7. Clear Cache
8. Reboot
That was the first time, and brick... as described above, back to recovery- tried missing out GAPPS- same result..
I went through a few different combinaitons, so have gotten quite used to the EDL mode miFlash...
Back through EDL.. flash recovery.. JUST AOSPEx, booted fine. Setup, etc, back to recovery, GAPPS, reboot, setups, etc.All working good- Except no power button
So I once again went back to recovery and flashed just the FW (Fully expecting it might fail)- Sure enough.. BRICK... So just, I've gone back through the miFlash, installed recovery, but then just decided to try rebooting from recovery into my existing AOSPEx- All works fine- Even the power button now- Was that fixed by the FW? And the bigger thing I'm wondering, since everytime I've flashed the FW it's resulted in a brick-does that mean the FW's not working? When I re flash the recovery, am I back to original FW?
Am I now on the new FW?
Only other thing is I don't have root... I'll see if I can find a supersu to flash, I guess.
So tl;dr- I'm all up and working- but flashing the latest FW form TheStrix appears to brick the Note 3 every time. I can only get a rom to install by NOT first flashing the FW. Flashing the FW after a rom still bricks. And I don't know if it is actually flashed with the new fw after re-installing recovery.
Edd.
Edmundajw said:
HI,
I just wanted to comment on this, in the hope that some more experienced member, or even TheStrix would see it.
I've had the exact same problem over the last few days, but have been able to fix it each time by reflashing recovery from miFlash in edl mode;
Flashing the firmware from TheStrix (Latest, kenzo) without fail, bricks the Redmi Note 3, only being able to get to FastBoot. I'm able to switch to EDL on the PC with that batch file that's floating about, and flash recovery through miflash. I've been on LineageOS14 for the past few weeks, but my phones been barely usable with lag. Switched to AOSPX the other day by first flashing the FW;
1. Reboot to recovery
2. Backups
3. Wipe everything except for sd
4. Flash FW
5. Flash AOSPEx
6. Flash Gapps
7. Clear Cache
8. Reboot
That was the first time, and brick... as described above, back to recovery- tried missing out GAPPS- same result..
I went through a few different combinaitons, so have gotten quite used to the EDL mode miFlash...
Back through EDL.. flash recovery.. JUST AOSPEx, booted fine. Setup, etc, back to recovery, GAPPS, reboot, setups, etc.All working good- Except no power button
So I once again went back to recovery and flashed just the FW (Fully expecting it might fail)- Sure enough.. BRICK... So just, I've gone back through the miFlash, installed recovery, but then just decided to try rebooting from recovery into my existing AOSPEx- All works fine- Even the power button now- Was that fixed by the FW? And the bigger thing I'm wondering, since everytime I've flashed the FW it's resulted in a brick-does that mean the FW's not working? When I re flash the recovery, am I back to original FW?
Am I now on the new FW?
Only other thing is I don't have root... I'll see if I can find a supersu to flash, I guess.
So tl;dr- I'm all up and working- but flashing the latest FW form TheStrix appears to brick the Note 3 every time. I can only get a rom to install by NOT first flashing the FW. Flashing the FW after a rom still bricks. And I don't know if it is actually flashed with the new fw after re-installing recovery.
Edd.
Click to expand...
Click to collapse
It's because you haven't unlocked officially. TheStrix's firmware contains MM bootloader which relocks your bootloader if you're in LP bootloader(which is your bootloader if you've unlocked unofficially). If you've already unlocked officially then flash the latest MIUI dev ROM(which relocks your bootloader) then unlock again, TheStrix's firmware will now work.
Or you can just unzip the Firmware then remove emmc_appsboot.mbn(MM bootloader) then rezip it again. You'd still get problems flashing the latest LineageOS Roms if you don't update your bootloader though. So my advice is unlock officially.
Try This guide http://en.miui.com/thread-235865-1-1.html and this guide make a deep flash cable and download the latest fastboot rom and follow the first link http://en.miui.com/thread-380827-1-1.html
Hi.
I flash this recovery from this thread --> https://forum.xda-developers.com/re...-development/unofficial-twrp-3-1-1-1-t3709034
I wipe every thing in the recovery.
Mark all cheks and select wipe.
I flash the latest slim stable 2.0 whit gapps and reboot the phone normal.
The phone boot first freeze and then reboot.
And then the nightmare has begin.
No matter what rom i flash its the same on all ROMS.
ALL !
Offical MIUI 9 whit MiFlash.
LoS 14,1 LoS 15.
AOSP.
I flash different recovery:
Redwolf, Official TWRP, TWRP for project treble for the new LOS 15.1
I remove the sd card.
Format all partition to different file system :ext4 , f2fs all the same.
Flash a different Firmware.
Boot freeze and the phone reboot.
When the phone enter in any custom recovery it dose`n reboot after 50 sec.
It only happened buy it booting the system.
I dont have any idea what to do.
This recovery from this man brick my phone.
Problem solve thanks to the @ArK96.
Solution 1:
Enter in EDL mode if you bootloader is unlocked --> https://forum.xda-developers.com/re...ool-redmi-note-4-edl-mode-o-removing-t3684024
Solution 2
Open the phone and enter in test point if your bootloader is locked --> https://www.youtube.com/watch?v=d0vjrA9S0p0
Use V8.1.10.0.MCFMIDI (http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz and unziped to qualqom hub bin where the program exe is.
Fallow his thread whit qualcom flasher. --> https://forum.xda-developers.com/redmi-note-4/how-to/how-to-fix-totally-dead-redmi-note-4-t3746465
One more time big thanks to @ArK96 and his assist in Skype to solve this software problem.
If was not him i will be whit no phone right now.
I got it when you flashed recovery the boot.img file is courupted that's why whenever you flash ROM it stuck at boot and again go to twrp you have to flash stock I'm going or twrp may be courupted try to flash it again
DhackerD said:
I got it when you flashed recovery the boot.img file is courupted that's why whenever you flash ROM it stuck at boot and again go to twrp you have to flash stock I'm going or twrp may be courupted try to flash it again
Click to expand...
Click to collapse
Nope is not that.
Like i say i flash different recovery.
And the system boot.
But freeze after 50 sec and reboot.
Its happened on any rom.
I really don`t know what to doo.
Bro! Flash Red Wolf TWRP. Check System, Data and Cache and swipe to wipe them. Flash the latest firmware. Then flash ROM & GApps package then reboot. You don't need to wipe every partition.
LordArcadius said:
Bro! Flash Red Wolf TWRP. Check System, Data and Cache and swipe to wipe them. Flash the latest firmware. Then flash ROM & GApps package then reboot. You don't need to wipe every partition.
Click to expand...
Click to collapse
Nope.
Dint work.
I erase the boot and recovery from fastboot.
Flash redwolf recovery.
Enter the recovery.
Try to wipe the partitions but it write cant mount the data and the cache.
So i manual wipe data to exfat and the to ext4.
I do the same whit the cache and finaly it mount the partitions.
So i normaly flash the latest stable firmware (i try whit old one) Los 14.1 whit gapps and reboot.
The phone boot to the boot animation freeze and reboot.
Then start loading again this time boot the Los 14.1 but a few seconds later the phone freeze and reboot.
I happened again and again.
I can`t even take a logicat to get some info why is this happened.
I am 100% sure this problem come from this gay recovery.
Why i flash this old recovery.
What i was think it.
Sectorian said:
Nope.
Dint work.
I erase the boot and recovery from fastboot.
Flash redwolf recovery.
Enter the recovery.
Try to wipe the partitions but it write cant mount the data and the cache.
So i manual wipe data to exfat and the to ext4.
I do the same whit the cache and finaly it mount the partitions.
So i normaly flash the latest stable firmware (i try whit old one) Los 14.1 whit gapps and reboot.
The phone boot to the boot animation freeze and reboot.
Then start loading again this time boot the Los 14.1 but a few seconds later the phone freeze and reboot.
I happened again and again.
I can`t even take a logicat to get some info why is this happened.
I am 100% sure this problem come from this gay recovery.
Why i flash this old recovery.
What i was think it.
Click to expand...
Click to collapse
You seriously messed up everything Lol! Now flash stock fastboot ROM and then try my method.
LordArcadius said:
You seriously messed up everything Lol! Now flash stock fastboot ROM and then try my method.
Click to expand...
Click to collapse
I already try this.
Its the same. Boot freeze and reboot.
And now i completly fu ck up the phone.
I lock the bootloader and i can`t unlock it.
Even the Miflash don`t want to flash a official rom.
I dont know how this recovery mess my phone but it destroy it completly.
A have to found a way to flash stock official Miui and send it whit lock bootloader to the buyers and use the warranty.
If some one have ideas to help.
I am open for suggestions.
Sectorian said:
I already try this.
Its the same. Boot freeze and reboot.
And now i completly fu ck up the phone.
I lock the bootloader and i can`t unlock it.
Even the Miflash don`t want to flash a official rom.
I dont know how this recovery mess my phone but it destroy it completly.
A have to found a way to flash stock official Miui and send it whit lock bootloader to the buyers and use the warranty.
If some one have ideas to help.
I am open for suggestions.
Click to expand...
Click to collapse
Bruh! I don't know whether this will work but it is worth a try.
Boot into EDL mode and then use MiFlash to flash Official MIUI. You can visit this thread HERE, to know how to boot into EDL.
No guarantees but worth a try, since your bootloader is locked it's the only way I suppose.
ArK96 said:
Bruh! I don't know whether this will work but it is worth a try.
Boot into EDL mode and then use MiFlash to flash Official MIUI. You can visit this thread HERE, to know how to boot into EDL.
No guarantees but worth a try, since your bootloader is locked it's the only way I suppose.
Click to expand...
Click to collapse
Thanks for the assist.
But before i lock the bootloader i delete the recovery.
So now i cant flash stock Miui it write succeses but it dont flash the rom.
And i dont have EDL its black screen.
MiuiUnlock tool dont want to unlock the phone bacause it dosen`t see the Miui accaunt loging in the ROM .
I play now whit the Miui Flash tool to flash stock Miui
Sectorian said:
Thanks for the assist.
But before i lock the bootloader i delete the recovery.
So now i cant flash stock Miui it write succeses but it dont flash the rom.
And i dont have EDL its black screen.
MiuiUnlock tool dont want to unlock the phone bacause it dosen`t see the Miui accaunt loging in the ROM .
I play now whit the Miui Flash tool to flash stock Miui
Click to expand...
Click to collapse
Hmm. I don't think you quite understood what I said. If fastboot is working on your use it enter EDL mode using the tool I mentioned before and then use MiFlash to flash MIUI. Using MiFlash on EDL mode doesn't require bootloader unlocking.
ArK96 said:
Hmm. I don't think you quite understood what I said. If fastboot is working on your use it enter EDL mode using the tool I mentioned before and then use MiFlash to flash MIUI. Using MiFlash on EDL mode doesn't require bootloader unlocking.
Click to expand...
Click to collapse
My computer port discover qualqom diganostic port.
The phone enter automaticly in qualqom diganostic.
But the MiuiFlash Tool dont detect the EDL and i cant flash the whit Miflaash tool.
The problem is that when i flash official MIUI 9 it flash for 1 sec and it write succses.
But it dint flash anything.
So the only solution for me is same how to flash stock Miui or atleast stock recovery some how.
Sectorian said:
Hi.
I flash this recovery from this thread --> https://forum.xda-developers.com/re...-development/unofficial-twrp-3-1-1-1-t3709034
I wipe every thing in the recovery.
Mark all cheks and select wipe.
I flash the latest slim stable 2.0 whit gapps and reboot the phone normal.
The phone boot first freeze and then reboot.
And then the nightmare has begin.
No matter what rom i flash its the same on all ROMS.
ALL !
Offical MIUI 9 whit MiFlash.
LoS 14,1 LoS 15.
AOSP.
I flash different recovery:
Redwolf, Official TWRP, TWRP for project treble for the new LOS 15.1
I remove the sd card.
Format all partition to different file system :ext4 , f2fs all the same.
Flash a different Firmware.
Boot freeze and the phone reboot.
When the phone enter in any custom recovery it dose`n reboot after 50 sec.
It only happened buy it booting the system.
I dont have any idea what to do.
This recovery from this man brick my phone.
I am desperate.
I am really hope some one here to help me.
Click to expand...
Click to collapse
Hey there! Don't worry I faced exactly same issue! If you go to service center those idiots will tell you to replace motherboard which is 80% of cost of phone itself. Well they are idiot! I fixed my phone myself! Its not hardware issue! You just messed up your system partitions! Believe me I Know your case! Phone would just boot up successfully then reboot after freezing! Right? Here is the solution: https://forum.xda-developers.com/redmi-note-4/how-to/how-to-fix-totally-dead-redmi-note-4-t3746465
This guide is written by me only! If you face any problem then feel free to ask! Best of luck!
addymishra said:
Hey there! Don't worry I faced exactly same issue! If you go to service center those idiots will tell you to replace motherboard which is 80% of cost of phone itself. Well they are idiot! I fixed my phone myself! Its not hardware issue! You just messed up your system partitions! Believe me I Know your case! Phone would just boot up successfully then reboot after freezing! Right? Here is the solution: https://forum.xda-developers.com/redmi-note-4/how-to/how-to-fix-totally-dead-redmi-note-4-t3746465
This guide is written by me only! If you face any problem then feel free to ask! Best of luck!
Click to expand...
Click to collapse
Thanks god.
But the problem is that my bootloader is locked.
That`s me first problem for now.
If i can flash stock miui i will unlock the bootloader.
Sectorian said:
Hi.
I flash this recovery from this thread --> https://forum.xda-developers.com/re...-development/unofficial-twrp-3-1-1-1-t3709034
I wipe every thing in the recovery.
Mark all cheks and select wipe.
I flash the latest slim stable 2.0 whit gapps and reboot the phone normal.
The phone boot first freeze and then reboot.
And then the nightmare has begin.
No matter what rom i flash its the same on all ROMS.
ALL !
Offical MIUI 9 whit MiFlash.
LoS 14,1 LoS 15.
AOSP.
I flash different recovery:
Redwolf, Official TWRP, TWRP for project treble for the new LOS 15.1
I remove the sd card.
Format all partition to different file system :ext4 , f2fs all the same.
Flash a different Firmware.
Boot freeze and the phone reboot.
When the phone enter in any custom recovery it dose`n reboot after 50 sec.
It only happened buy it booting the system.
I dont have any idea what to do.
This recovery from this man brick my phone.
I am desperate.
I am really hope some one here to help me.
Click to expand...
Click to collapse
Sectorian said:
Thanks god.
But the problem is that my bootloader is locked.
That`s me first problem for now.
If i can flash stock miui i will unlock the bootloader.
Click to expand...
Click to collapse
Do you have unlocking permissions from Xiaomi? If yes then thats very good news for you! Actually you don't need miui in order to unlock bootloader if you are not logged into device using mi account which im pretty sure of as you are not on miui. I would recommend you to download latest mi unlock tool and unlock your device! I think it will be unlocked successfully if your mi account has unlocking permissions!
Let me tell you, you need to add account in developers options only when you are on miui and you mi account is logged in on the device! In your case you are neither on miui not logged in with mi account on device so it will unlock! Trust me I was in same place as you! Just breathe in and out and follow this:
* Download mi unlock tool
* Start mi unlock tool and login with you mi account which had permissions
* Connect your phone in fastboot mode
* Click on unlock and it will unlock successfully then you are good to go!
addymishra said:
Do you have unlocking permissions from Xiaomi? If yes then thats very good news for you! Actually you don't need miui in order to unlock bootloader if you are not logged into device using mi account which im pretty sure of as you are not on miui. I would recommend you to download latest mi unlock tool and unlock your device! I think it will be unlocked successfully if your mi account has unlocking permissions!
Let me tell you, you need to add account in developers options only when you are on miui and you mi account is logged in on the device! In your case you are neither on miui not logged in with mi account on device so it will unlock! Trust me I was in same place as you! Just breathe in and out and follow this:
* Download mi unlock tool
* Start mi unlock tool and login with you mi account which had permissions
* Connect your phone in fastboot mode
* Click on unlock and it will unlock successfully then you are good to go!
Click to expand...
Click to collapse
Yes but the stuped Miui Unlock Tool Requaret to be sing in to the Miui.
I cant sing in to the phone MIUI OS.
Because my phone is bricked whitout recovery.
Sectorian said:
Yes but the stuped Miui Unlock Tool Requaret to be sing in to the Miui.
I cant sing in to the phone MIUI OS.
Because my phone is bricked whitout recovery.
Click to expand...
Click to collapse
You are quite not getting what I am trying to say! Just strictly follow the steps:
1) Download Mi unlock tool
2) Run the tool and login with you mi account ( it doesn't matter if you are logged into miui or not)
3) Connect your phone to PC in fastboot mode (power+ volume down button)
4) Your phone will be detected as Mi device in unlock tool
5) Click on unlock and it will be completed
First of all do this then proceed with anything else! Its late so I'm going to sleep! Will check back on you in the morning! If you face any problem then keep me posted along with screenshots! Hope it helps!
addymishra said:
You are quite not getting what I am trying to say! Just strictly follow the steps:
1) Download Mi unlock tool
2) Run the tool and login with you mi account ( it doesn't matter if you are logged into miui or not)
3) Connect your phone to PC in fastboot mode (power+ volume down button)
4) Your phone will be detected as Mi device in unlock tool
5) Click on unlock and it will be completed
First of all do this then proceed with anything else! Its late so I'm going to sleep! Will check back on you in the morning! If you face any problem then keep me posted along with screenshots! Hope it helps!
Click to expand...
Click to collapse
Dude i understand you.
But the leatest Miui Unlock Tool Requer my account to be login in to the MIUI 9 for example.
I use Miui twice.
The Miui Unlock Tool say that my acount need to be bound.
Sectorian said:
Dude i understand you.
But the leatest Miui Unlock Tool Requer my account to be login in to the MIUI 9 for example.
I use Miui twice.
The Miui Unlock Tool say that my acount need to be bound.
Click to expand...
Click to collapse
Which recovery you have right now?
same problem on my redmi note 4.
i flash stock rom in many time in edl methode but the same problem after 50 second phone will restart.
sanalsanal4646 said:
same problem on my redmi note 4.
i flash stock rom in many time in edl methode but the same problem after 50 second phone will restart.
Click to expand...
Click to collapse
The problem is solve.
Lock the page 1 !
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Completely Bricked
Me too need a stock rom of ta 1056. Please help if you could manage to provide a helping hand... ?
I had the same issue like yours, looping in twrp. then i tried to flash it with a so called stock rom from net, guess what it went completely bricked and I donnow what to do. ??
mrabudi said:
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Click to expand...
Click to collapse
It's simple. just get the stock recovery (and boot, optional) to flash it with fastboot and go to recovery and wipe it and you'll be ok.
and also using the twrp on this phone is not a great idea to wipe.
if you wanna wipe. please use "fastboot -w" to wipe the phone while bootloader is unlocked. or stock recovery to wipe.
Because twrp built this recovery with only formatting option was ext4 to /data and /cache. So the phone cannot operate properly. Which leads to fake failed decryption notification.
Data partition must need to be formatted under f2fs format.
And finding rom for this phone is pretty easy. Just find some nb0 file for this phone (any variant of this phone should work) and extract it with "nb0 extractor" and then flash it with SP Flash tool by mediatek.
That's my way. I don't know how will you do. But normally you only need the nb0 file and then flash it with OST LA (Nokia's flash tool based off Intel's SUT L1/L3 tool).
My Nokia 1 TA-1047 stuck at Nokia logo screen
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
cuantonhonhoi said:
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
Click to expand...
Click to collapse
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047. Since it's a universal ROM so any variant of the phone can also work) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to look at line with partition "metadata" and then edit "boundary_check" to false.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
kutiz21 said:
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to hide/delete line with partition "metadata" in scatter.txt and you can flash it perfectly.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
Click to expand...
Click to collapse
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
pabloluih said:
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
Click to expand...
Click to collapse
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
kutiz21 said:
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
Click to expand...
Click to collapse
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
That's weird. If you unlocked the bootloader and install adb/fastboot (must be latest version. Older version will not recognize the phone, download platform-tools from google dev site, don't download adb tools off XDA) + Nokia's driver from emulated CD drive (every time you plug the phone to computer with official rom, you'll see it) properly then it should be able to work.
You need to check the fastboot device driver Device Manager (devmgmt.msc) and see if the driver is properly installed yet.
You can only use "fastboot -w" once the bootloader is unlocked. And booting up the phone. It will say the bootloader is in Orange state.
You need to unlock oem bootloader from developer settings when the stock rom is there. And in fastboot too
Here is how you unlock it:
Enable oem unlock from dev settings
Then reboot to fastboot mode (bootloader)
Do this:
"fastboot oem key "serial number string converted to md5, not imei strings" "
"fastboot oem unlock"
Volume up
Then you are actually unlocked the bootloader.
Unlock from developer settings only will not do the trick. It only allows you to have ability unlock the bootloader in fastboot.
If you stuck on the Encryption unsuccessful screen. Try wipe it with stock recovery or "fastboot -w" (if you properly unlocked the bootloader)
If you think you can't do anything anymore. Just flash the ROM provided you above.
If you need the extracted ROM for SP flash tool and the fastboot driver. I can link it to you.
Most of all drivers will automatically install off Windows Update if you're on Windows 10 (except the fastboot driver, and yes. SP flash tool drivers are also provided by Windows 10 too)
Also. You should update the phone to the latest software update when flashing stock rom too. Because newer builds for this phone is compatible-friendly with GSI rom (Treble ROMs like AOSP Android 9 or 8.1 by phhusson)
Updates on Android 9/10
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
Nokia might harden the security of the device so you can't use Magisk on stock rom.
Hi,
My favourite phone is the Xiaomi Redmi note 3 Pro SE with Lineage OS 13 (Yes marshmallow).
I got a new one that was in endless bootloop and I planned to get it working.
I don't know if the bootloader has been unlocked and how (last time I checked it was written locked), if a custom ROM as been flashed or anything that could been done on it before I get it.
After many tries I first succeed to install LineageOs 13 on it, what I remember:
I go to fastboot mode
I go to edl mode
I flashed it with an old MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_global_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. (This is the way to get a recovery with no need to unlock bootloader)
I started it directly to TWRP recovery mode (to be sure TWRP will stay it I guess?) changed the language and checked OTA checkbox in parameters
I started this old official ROM once (to get the full storage capacity)
I discovered it was a 16GB ROM / 2GB RAM version instead a 32GBROM / 3GB RAM I previously knowed
I restarted to TWRP recovery mode
I wiped david/cache
I flashed the last knowed LineageOS 13 for this phone: https://forum.xda-developers.com/re...ageos-13-0-t3533744/post83687823#post83687823
I wiped david/cache
I flashed the last radeon kerned on it
I wiped david/cache
I restarted it to LineageOS 13
I restarted to TWRP recovery mode, changed the language and checked OTA checkbox in parameters
I flashed magisk (sytemless)
I wiped david/cache
I restarted it to LineageOS 13
I could use it install a lot of things, was happy with it
Before succeeding I tried a lot of combinations of official ROM/TWRP/MiFlash versions and this couple was the only one working.
Other MiFlash versions don't detect the phone in edl mode
But 2 weeks later, just after installing a new app, the phone sudently reboots and I got stuck in bootloop again...
I could go to recovery one time, I selected reboot system, now I can't go to recovery anymore
I still can go to fastboot mode and edl mode, and I can flash a ROM, but whatever I flash I can't go away from bootloop.
What could the new bootloop come from?
Is my installation sequence good?
Why only this combination of official ROM/TWRP/MiFlash versions was working?
Why can't I start a ROM anymore after a new flash?
Why can't I go to the recovery anymore after a new flash?
How to check if the emmc memory is defective (I got no error while flashing)?
Thanks for reading, hope someone still cares on this old great phone
Sorry for my bad English
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
JD. A said:
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
Click to expand...
Click to collapse
Thanks for your answer.
The last app before bootloop was a sms/mms backup app on google store I get through Aurora.
I tried to flash the stock ROM (old one) kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 but it doesn't start, always bootloop.
I have no option to wipe on the only miflash version that detect my phone in edl : the 2016.04.01.0 64 bit version. so I choose flash all data/storage include, but still bootloop.
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
JD. A said:
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
Click to expand...
Click to collapse
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
ROUGE13 said:
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
Click to expand...
Click to collapse
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
JD. A said:
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
Click to expand...
Click to collapse
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
ROUGE13 said:
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
Click to expand...
Click to collapse
I'm not home this weekend so I can't say for sure. gismoZ recommends using the 8.0.2 firmware or something like that can't remember, but the latest works just fine on my kate. The latest miflash is from 20200314 and just get the latest global rom and try to flash it.
I tried with an other windows computer, I successfully used last MiFlash version
But now, whatever I flash, ROM version or recovery version, it stay in bootloop when I power it.
I expect the eMMC memory to be faulty but why doesn't I have any error while flashing?
How to be sure this comes from the eMMC chip?
Some people have successfully changed it on the mediatek version of the phone:
https://fr-fr.facebook.com/16816505...c-kmvtu-done/1821360108117225/?_fb_noscript=1
https://translate.google.com/transl.../03/service-hp-xiaomi-redmi-mi-note-mati.html
If I go on this solution I have some questions before:
Must the eMMC chip be programmed before soldering it?
If not, can I program it with MiFlash once soldered?
If not, have I to use some special touch/contact on the mainboard to program it?
How to be sure of the chip model to buy?
Will the chip come already balled? Or have I to ball it before soldering it on mainboard?
Could I buy a 32GB chip instead 16GB original one?
Something else to test before going on this crazy last chance solution?
I bought a EDL flash cable, but I think I don't need it on this phone, I alway success to go to EDL mode from fastboot mode with a small batch script.
Hello ,
Any chance I could get an answer anymore or is my problem too specific maybe?