Redmi Note 3 - Special Edition (Kate) stuck on booting screen. - Xiaomi Redmi Note 3 Questions & Answers

Hi Folks
I just bought my girlfriend a Redmi Note 3 SE (Kate) quick back story, she received it turned it on added a pin to it got called away, when she got back to it she couldn't remember the pin, bad news is she hadn't yet turned on Developer Mode or USB Debugging.
Original SW - MIUI 7.5 android 6.0.1, at least that's what the Ali product page says (Sorry it seems I can't post a link to the actual product)
This began last Friday, since then she has tried the following:-
Installed MI Suite and registered a gmail account - so far "device not recognised"
Applied for an Unlock code.
Unlocked the boot loader which seems to have been successful.
Flashed two different (stock) ROM's which completed successfully but both stuck while booting the phone.
One was:-
"kate_global_images_6.12.29_20161228.0000.00_6.0_global" not sure what the other was.
On trying a different ROM today she's now getting the following error:-
"Can't Flash in miflash. Not enough storage is available to process this command"
Tried different versions of the Flash tool including the Beta version but still getting the same error on each of them.
Ticked the "Clear Data" box in the Mi Flash tool but that doesn't help.
A bit stuck on what to try from here and any help would be greatly appreciated if you need any more info please let me know.

I had the same bootloop problem with the stock firmware and miflash and driver was a pain to get sorted out.
What versions of miflash have you tried and which firmware did you download from xiaomi?

theoneofgod said:
I had the same bootloop problem with the stock firmware and miflash and driver was a pain to get sorted out.
What versions of miflash have you tried and which firmware did you download from xiaomi?
Click to expand...
Click to collapse
Hi thanks for the reply, unfortunately I need to wait for an answer on that as she's not around at the moment, but from what I can gather she has tried miuiflash 1, 2 and beta and i know she tried this which I'm assuming is a firmware - kate_global_images_6.12.29_20161228.0000.00_6.0_global (if it's not please let me know what we should be using) *edit, mind you that's one of the files that got stuck showing the out of space error.
I also forgot to mention the PC is a win 10 64bit..
Soon as I can get you a better answer on the above I'll post it.

I would have them try this version http://bigota.d.miui.com/V8.1.1.0.M...DI_20161202.0000.00_6.0_global_ac46ea44bd.tgz it's the latest fastboot ROM.
Make sure when you install miflash you are running in test mode so the drivers install properly and accept any prompts about driver signatures. That is important. I believe MiFLash_v20160401 worked for me. Also you know when you're in EDL when the front LED flashes red now and then.

theoneofgod said:
I would have them try this version http://bigota.d.miui.com/V8.1.1.0.M...DI_20161202.0000.00_6.0_global_ac46ea44bd.tgz it's the latest fastboot ROM.
Make sure when you install miflash you are running in test mode so the drivers install properly and accept any prompts about driver signatures. That is important. I believe MiFLash_v20160401 worked for me. Also you know when you're in EDL when the front LED flashes red now and then.
Click to expand...
Click to collapse
Ah so it wasn't a firmware, alright I've passed this on as soon as I hear back I'll post here, many thanks.

I just checked the link for the 8.1.1.0 Firmware but it gives a 404 error on the page, I'll look on their site for an alternative, but if you do know of an alternative please let me know.
**edit Never mind a right click and copy link location got it.

So the issue looks to be solved, so firstly many thanks "theoneofgod" for your input.
Unfortunately due to a rather dodgy internet connection I haven't managed to get further into it, but here is what I received:-
"I used the same Kate and used miflash beta version.. i did the same as i did on first attempt.. after succesfully flashing it, i turned it on (result:same stuck on booting)
i switch it back to fastboot mode.
flash it.
result error.
i then press power on for about 5 seconds or till the mi logo appeared.
unplugged the USB cable and plugged it in again.
then phone booted.
and
When miflash beta version recognized my phone as just a device not com port. i flashed it. (it was just flashing endlessly)
So i tried to refresh the page, it then showed my device with an id as com10 (I have a feeling this might be the important part)
i flashed that too, and then it worked didn't get that error " no storage" anymore.
I'm not sure though if that helped
Basically I'm saying that i was flashing 1 device with two different id.
So I'm thinking simply the device refresh actually did the trick, anyway it looks to be solved, that was 3 days of no fun, and that whole thing about hey submit an application for a bootloader unlock and then wait 2 or 3 weeks and we might even refuse it lol.
Thanks again for your help "theoneofgod" thanks meter pressed.

Related

P780 Bricked and not recognized in PC

Hello,
I bought a Lenovo P780 some days ago from china.
The phone came with many pre-installed Chinese apps that simply annoyed me, moreover I kept getting email has stopped, settings has stopped error messages. It was running on a VIBE firmware.
I checked online on how to Flash the phone to international version and downloaded some ROMs to do the flashing.
I managed to get the Flashing done, with this ROM, P780_ROW_S110_130629, but afterwards the Phone was completely unusable.
The problems are as follows,
1. The Phone does not boot up at all after pressing the power key, nothing on screen!
2. Pressing the power and volume keys shows nothing!
3. when plugged to the computer, i get the USB device not recognized error message! (I have all the necessary drivers installed)
The computer only see the phone as follows, Alcatel Single RNDIS Interface in the USB Device not Recognized window.
4. The computer keeps playing the plugged in devices sounds, plugged sound the followed by unplugged sound, repeatedly, and that is when the phone is still connected.
It´s only later I found some tip saying that one cannot flash a device produced 03.2014 and later with the ROM I used. Mine happens to be such a device Prod. Date 09.03.2014!
I have read through some almost similar problems but have not encountered my specific problem.
I am hoping to have someone who knows a workaround share with me how to get the phone back up running. I will highly appreciate your Help.
Solution Found!
Found solution :laugh:
1. Restored the comp to 3 days ago, before installation of any drivers
2. Downloaded and installed this driver, http://www.mediafire.com/download/lbdo0sglhdhrje9/MTK+Divers.rar
3. Downloaded my ROM here, used this one, P780_S123_ROW_131231
http://www.needrom.com/mobile/lenovo-p780-2/
4. I downloaded a newer version of Flashtools from this forum,
5. I downloaded this preloader,
http://forum.xda-developers.com/attachment.php?attachmentid=2744499&d=1400125492
6. I prepared the files for flashing as usual, (USB speed set to „do not switch speed“), changed the preloader´s location to the one I downloaded, (Trying to flash with the one in the ROM gave an error)
7. I removed the Phone´s back cover, plugged the usb cable to the phone, and holding down the reset button, connected the usb cable to the computer
8. Then released the reset buton and VOILA!, the flashing began :fingers-crossed: and ran without any errors.:laugh:
9. The greatest moment was to see the phone reboot fully after this. :victory:
After rebooting and connecting to the internet, I upgraded the FW and everything is running smooth.
I liked the preinstalled VIBE ROM, only that it had some flows here n there, plus the preinstalled Chinese apps annoyed me! I am now getting used to the original P780´s ROM.
Anyone who lands in my previous mess,- Flashing with wrong ROM and cannot get Phone to boot up, or get it recognized by PC, can try out my solution, of-course at YOUR OWN RISK!
PS, Always take time to inform yourself fully before performing this task, it will save you some Headaches!
Happy flashing
Uritam said:
Found solution :laugh:
1. Restored the comp to 3 days ago, before installation of any drivers
2. Downloaded and installed this driver, http://www.mediafire.com/download/lbdo0sglhdhrje9/MTK+Divers.rar
3. Downloaded my ROM here, used this one, P780_S123_ROW_131231
http://www.needrom.com/mobile/lenovo-p780-2/
4. I downloaded a newer version of Flashtools from this forum,
5. I downloaded this preloader,
http://forum.xda-developers.com/attachment.php?attachmentid=2744499&d=1400125492
6. I prepared the files for flashing as usual, (USB speed set to „do not switch speed“), changed the preloader´s location to the one I downloaded, (Trying to flash with the one in the ROM gave an error)
7. I removed the Phone´s back cover, plugged the usb cable to the phone, and holding down the reset button, connected the usb cable to the computer
8. Then released the reset buton and VOILA!, the flashing began :fingers-crossed: and ran without any errors.:laugh:
9. The greatest moment was to see the phone reboot fully after this. :victory:
After rebooting and connecting to the internet, I upgraded the FW and everything is running smooth.
I liked the preinstalled VIBE ROM, only that it had some flows here n there, plus the preinstalled Chinese apps annoyed me! I am now getting used to the original P780´s ROM.
Anyone who lands in my previous mess,- Flashing with wrong ROM and cannot get Phone to boot up, or get it recognized by PC, can try out my solution, of-course at YOUR OWN RISK!
PS, Always take time to inform yourself fully before performing this task, it will save you some Headaches!
Happy flashing
Click to expand...
Click to collapse
So you can confirm that the P780_S123_ROW_131231 version works on a Chinese model ?
No problems with bad signal, SIM not detected and so on ? I'm trying to figure out if it is safe to go ROW.
And as I see your steps, it would also be an option to remove the drivers again I think.
For me, it worked by simply plugging the device into a different port, and then I could install the drivers (as a regular Mediatek USB device, not as the Preloader device).
......confirm?.......
casaben said:
So you can confirm that the P780_S123_ROW_131231 version works on a Chinese model ?
No problems with bad signal, SIM not detected and so on ? I'm trying to figure out if it is safe to go ROW.
And as I see your steps, it would also be an option to remove the drivers again I think.
For me, it worked by simply plugging the device into a different port, and then I could install the drivers (as a regular Mediatek USB device, not as the Preloader device).
Click to expand...
Click to collapse
I can confirm with my device, I bought it directly from China and as I mentioned earlier, it had several Chinese apps that really annoyed me. I was really stressed up trying to configure what to do. But after reading several forums and stitching the different opinions together, I managed to do what I did earlier on today and everything is working out fine.
I had not done any backup of IMEI and co before flashing my phone yesterday, and that worried me the more. But after re-flashing it with the above ROM, everything got back together and even the IMEI was found automatically without further hustles.
Please do some more reading before trying my steps, my tryout worked good with my Phone, cannot tell whether it will with yours!
Saying this coz am not really sure whether the date written at the bottom of the Accu. represents the phone´s production date!
Uritam said:
Please do some more reading before trying my steps, my tryout worked good with my Phone, cannot tell whether it will with yours!
Saying this coz am not really sure whether the date written at the bottom of the Accu. represents the phone´s production date!
Click to expand...
Click to collapse
Well pretty sure the unbricking works, you got the preloader from my post
I'm now testing with VIBE 1.5 (KitKat), pretty good (almost not Chinese there) but some battery issues. Next step is to find out if I can get the 3G 900Mhz band to work.
Not sure if I'm going to switch to ROW, don't see any reason now.
Thanks for the feedback!
casaben said:
Well pretty sure the unbricking works, you got the preloader from my post
I'm now testing with VIBE 1.5 (KitKat), pretty good (almost not Chinese there) but some battery issues. Next step is to find out if I can get the 3G 900Mhz band to work.
Not sure if I'm going to switch to ROW, don't see any reason now.
Thanks for the feedback!
Click to expand...
Click to collapse
Sure it worked out just fine. Didn´t notice you were the same person with almost the same problem in the post with the preloader.
I will be checking out this pages to see how the Kitkat versin goes. Am am curious just how it will be.
Have a great week!
Thank you, you saved me!
I have bricked my lenovo p780 while trying to change the rom.
It was shipped from china with Vibe rom, I tried to install S113 rom and the phone went dead.
I have followed your guide and it worked. The phone is working!!!!
Edit: Just to add some more details in case some one else is having the same issue.
I made it with windows 8.1, drivers from this post, and S123 Row rom.
Then the firmware had 5 or 6 updates to 4.4.2 Kit Kat.
I have 2 more to go.... Total of 3 phones. Will update if any changes are found.
Also I will keep the software in case some of the links does not work or the code can't be found.
i dont understand the part where you hold the reset button and release it.
Uritam said:
Found solution :laugh:
1. Restored the comp to 3 days ago, before installation of any drivers
2. Downloaded and installed this driver, http://www.mediafire.com/download/lbdo0sglhdhrje9/MTK+Divers.rar
3. Downloaded my ROM here, used this one, P780_S123_ROW_131231
http://www.needrom.com/mobile/lenovo-p780-2/
4. I downloaded a newer version of Flashtools from this forum,
5. I downloaded this preloader,
http://forum.xda-developers.com/attachment.php?attachmentid=2744499&d=1400125492
6. I prepared the files for flashing as usual, (USB speed set to „do not switch speed“), changed the preloader´s location to the one I downloaded, (Trying to flash with the one in the ROM gave an error)
7. I removed the Phone´s back cover, plugged the usb cable to the phone, and holding down the reset button, connected the usb cable to the computer
8. Then released the reset buton and VOILA!, the flashing began :fingers-crossed: and ran without any errors.:laugh:
9. The greatest moment was to see the phone reboot fully after this. :victory:
After rebooting and connecting to the internet, I upgraded the FW and everything is running smooth.
I liked the preinstalled VIBE ROM, only that it had some flows here n there, plus the preinstalled Chinese apps annoyed me! I am now getting used to the original P780´s ROM.
Anyone who lands in my previous mess,- Flashing with wrong ROM and cannot get Phone to boot up, or get it recognized by PC, can try out my solution, of-course at YOUR OWN RISK!
PS, Always take time to inform yourself fully before performing this task, it will save you some Headaches!
Happy flashing
Click to expand...
Click to collapse
when did you install the drivers cuz im having the same problem . i already opened my phone and coudlnt find the said button not the same lenovo though i have a lenovo a360t with same problem , the pc do not recognize mtk port but the alcatel single thing . pleaseeee hellp . im so glad i found this . thank you sir.
Uritam said:
Found solution :laugh:
1. Restored the comp to 3 days ago, before installation of any drivers
2. Downloaded and installed this driver, http://www.mediafire.com/download/lbdo0sglhdhrje9/MTK+Divers.rar
3. Downloaded my ROM here, used this one, P780_S123_ROW_131231
http://www.needrom.com/mobile/lenovo-p780-2/
4. I downloaded a newer version of Flashtools from this forum,
5. I downloaded this preloader,
http://forum.xda-developers.com/attachment.php?attachmentid=2744499&d=1400125492
6. I prepared the files for flashing as usual, (USB speed set to „do not switch speed“), changed the preloader´s location to the one I downloaded, (Trying to flash with the one in the ROM gave an error)
7. I removed the Phone´s back cover, plugged the usb cable to the phone, and holding down the reset button, connected the usb cable to the computer
8. Then released the reset buton and VOILA!, the flashing began :fingers-crossed: and ran without any errors.:laugh:
9. The greatest moment was to see the phone reboot fully after this. :victory:
After rebooting and connecting to the internet, I upgraded the FW and everything is running smooth.
I liked the preinstalled VIBE ROM, only that it had some flows here n there, plus the preinstalled Chinese apps annoyed me! I am now getting used to the original P780´s ROM.
Anyone who lands in my previous mess,- Flashing with wrong ROM and cannot get Phone to boot up, or get it recognized by PC, can try out my solution, of-course at YOUR OWN RISK!
PS, Always take time to inform yourself fully before performing this task, it will save you some Headaches!
Happy flashing
Click to expand...
Click to collapse
But you said your pc was not recognizing your phone. Then how did you flashed the rom with sp flash tool because it requires connecting the phone to the pc via usb cable. How did you solved it ? I haved bricked my phone. Its not turning on or charging in off mode either..help :crying:
Suvam Mondal said:
But you said your pc was not recognizing your phone. Then how did you flashed the rom with sp flash tool because it requires connecting the phone to the pc via usb cable. How did you solved it ? I haved bricked my phone. Its not turning on or charging in off mode either..help :crying:
Click to expand...
Click to collapse
What did you done?
How the phone "died"?
Bad flash?
stympy said:
What did you done?
How the phone "died"?
Bad flash?
Click to expand...
Click to collapse
Solved
Dont know how the SP Flash tool flashed the firmware even after the pc was showing could not recognize device
help flashing not starting and pluged in pluuged out sounds are coming
---------- Post added at 07:18 PM ---------- Previous post was at 07:12 PM ----------
Uritam said:
Found solution :laugh:
1. Restored the comp to 3 days ago, before installation of any drivers
2. Downloaded and installed this driver, http://www.mediafire.com/download/lbdo0sglhdhrje9/MTK+Divers.rar
3. Downloaded my ROM here, used this one, P780_S123_ROW_131231
http://www.needrom.com/mobile/lenovo-p780-2/
4. I downloaded a newer version of Flashtools from this forum,
5. I downloaded this preloader,
http://forum.xda-developers.com/attachment.php?attachmentid=2744499&d=1400125492
6. I prepared the files for flashing as usual, (USB speed set to „do not switch speed“), changed the preloader´s location to the one I downloaded, (Trying to flash with the one in the ROM gave an error)
7. I removed the Phone´s back cover, plugged the usb cable to the phone, and holding down the reset button, connected the usb cable to the computer
8. Then released the reset buton and VOILA!, the flashing began :fingers-crossed: and ran without any errors.:laugh:
9. The greatest moment was to see the phone reboot fully after this. :victory:
After rebooting and connecting to the internet, I upgraded the FW and everything is running smooth.
I liked the preinstalled VIBE ROM, only that it had some flows here n there, plus the preinstalled Chinese apps annoyed me! I am now getting used to the original P780´s ROM.
Anyone who lands in my previous mess,- Flashing with wrong ROM and cannot get Phone to boot up, or get it recognized by PC, can try out my solution, of-course at YOUR OWN RISK!
PS, Always take time to inform yourself fully before performing this task, it will save you some Headaches!
Happy flashing
Click to expand...
Click to collapse
help flashing not starting and plugin out sound is coming
I know this is a very old thread, but, I was fixing up a P780 for a friend (he was constantly getting gapps.com stopped working and such) so I flashed some (stock?, Lenovo_P780_S115_MT6589_20130807) rom I found via SP Flash tool. It worked fine. So the next thing I was supposed to do was write IMEIs back, and for the life of me, i couldn't get that to work ( i would always get to "start searching kernel com port and handshake", and after that would get something like enter AP meta mode fail default, or something like that) so I started looking for alternatives, and found that one of the easiest ways is to root the phone, and install mobile uncle or MTK tools or whatever, anyway, I download twrp, flashed it using SP Flash Tool, and now the phone won't turn on, can't be detected by the Flash tool, it is in a way detected by windows (Unknown USB Device, Device descriptor Request failed), although it sort of goes on an off. LED lights up when connected to a charger or PC via USB

Redmi 3 updater doesn't update from storage

Hi guys,
I got unlock permissions from Xiaomi today, and I wanted to install Cyanogenmod 13 beta 2 as I hate MIUI with passion. Yet I couldn't unlock my device ("Couldn't verify device" on 50% of verifying). Went through some googling, found out I have to update my 7.3.2.0.0 Global to Developer version. (Yes, I have that infamous 7.3.2.0.0 rom everyone hates and I am trying hard to get rid of it.)
So I tried it. Went to Updater, chose "Choose update package" and chose the package I've downloaded from official miui site, which was located in "downloaded_rom" folder in root right as official manual said.
And the phone turned off and started again.
Yet nothing happened. It just restarted without actually doing anything. My all data are as they were, my version is still 7.3.2.0.0 Global.
Recovery mode update doesn't work, as I don't get that usual recovery mode menu, but just a picture showing me I should plug my Redmi into PC (does nothing when I do).
Fastboot update has this notice underneath it: "If your device is locked. please click here to unlock it first." ... hell, I'm trying to do that whole time, that's why I need to change that ROM first.
I've ran out of options. And so I'm turning to you guys - help me, please.
I'm not an experienced user, haven't owned Android for like 3 years, although I've flashed some roms earlier. But I need to get rid of this vendor rom. Google play services are terribly unstable on it, for example.
Ask me any additional questions you need to know. I'm not married and I own a dog, for example.
Any help is appreciated. Thank you very much.
EDIT: That title doesn't really reflect my thread at all. I just wanted to talk about the first updating option, but then I started ranting about it all and couldn't stop. Please, forgive me the title isn't really pinpoint right.
EDIT2: My recovery looks like this: choimobile *dot* vn/attachments/vao-che-do-download-redmi-3-jpg.21534/ ... as a newbie user I can't post links, so please, exchange that *dot* for an actual dot and you'll see. I don't speak chinese.
I had that too, you need to flash it via fastboot
http://en.miui.com/a-234.html
Edit: or you could flash SpaceX via fastboot without unlocking bootloader, and then flash via the TWRP installed with that. People say that works.
Thing is, I can't see my device in MiFlash. No idea why - on "adb devices" it shows up without any problems, but in fastboot mode it just doesn't cooperate.
Could that be because I'm not using the original cable? Heard it can cause some issues. Can't try it atm sadly.
Sent from my Redmi 3 using Tapatalk
Barty19 said:
Thing is, I can't see my device in MiFlash. No idea why - on "adb devices" it shows up without any problems, but in fastboot mode it just doesn't cooperate.
Could that be because I'm not using the original cable? Heard it can cause some issues. Can't try it atm sadly.
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
In normal Google fastboot.exe, I couldn't see my device, but in MiFlash's fastboot.exe, I could.
Open the folder with the fastboot.exe you want to check if it's working, shift+right click and "open command window here", then run "fastboot devices".
Also, to open fastboot mode you need to use power + vol up and it opens to that image, no menu. Or was it vol down? Try the one that opens to that image directly, no menu.
Vol down it was. Anyway meanwhile you were writing your advice I've deleted some drivers that were apparently messing with my device and now I see it in MiFlash! Yay!!!
Well, let's hope I won't screw it now. I'm in a middle of SpaceX download. Should I try to MiFlash a normal MIUI with a locked bootloader, or should I do it through SpaceX?
Barty19 said:
Vol down it was. Anyway meanwhile you were writing your advice I've deleted some drivers that were apparently messing with my device and now I see it in MiFlash! Yay!!!
Well, let's hope I won't screw it now. I'm in a middle of SpaceX download. Should I try to MiFlash a normal MIUI with a locked bootloader, or should I do it through SpaceX?
Click to expand...
Click to collapse
What I did is I installed SpaceX MIUI 8 by ManhIT and it came pre-loaded with TWRP recovery and then I booted into the recovery by MIUI 8's updater app and bam....there you go. Now you can flash any ROM you'd like. Btw, I did this while my bootloader is still locked; never went to Xiaomi to unlock it for me. I've flashed several locked bootloader roms such as CM 13, CM12.1 , and locked versions of MIUI roms and I've never encountered any bricks....yet lol
I DID IT!
Not quite your way, to be honest - the fault was in my already installed (and faulty) PC drivers. Yet I did it with your support and I really appreciate the fact you were willing to help me with the problem. Thank you very much, mate.
Anyway, good night.
*a very happy Barty*
Barty19 said:
I DID IT!
Not quite your way, to be honest - the fault was in my already installed (and faulty) PC drivers. Yet I did it with your support and I really appreciate the fact you were willing to help me with the problem. Thank you very much, mate.
Anyway, good night.
*a very happy Barty*
Click to expand...
Click to collapse
Cheers to you my friend!!

Soft brick mode after 13 of September update. I tried it all. Geniuses speak up!

Hello Awesome People!
I've read and I've tried a lot to unbrick my Xiaomi Redmi Note 4 on Snapdragon 625.
What happened?
After software actualization my phone stuck on Mi logo for 36+hours.
What has been tried?
I manually unblocked bootloader and I tried several ROMs. Every time I had this error in MiFlash critical partition flashing is not allowed or partition flashing is not allowed. I tried to edit in TextEditor some files but with no success after all.
1. One thing I didn't do was disabling driver signature enforcements in windows. What is this needed for?
2. Is this kind of malfunction can be reported during warranty period? Who is responsible for making my phone unusable?
3. Which ROM would you recommend to stick with during my following flashing tryouts?
4. I am going to check all the USB cables. Might it help when I've got the "critical partition flashing is not allowed" error?
5. What causes this "critical partition flashing is not allowed" error?
6. I've got no deep flash cable and I'm at the end of the world, so it's very difficult to get one of these here. Should I start trying to get one anyway? Someone had the same issue and could resolve it this way?
7. What to do now guys? Any ideas? -> For now I'll be checking all the usb cables I can get my hands on.
I know that some of the answers can overlap, but I chose the questions intentionally. I've been researching and checking solutions for over a week now. I would like to have deeper understanding of what the heck is going on with my phone and its software. There are no service centers here which can help me (their workers have less knowledge than I have, a sad lol), so I am dependent on your knowledge and your good will.
Best Regards
PatchMe said:
Hello Awesome People!
I've read and I've tried a lot to unbrick my Xiaomi Redmi Note 4 on Snapdragon 625.
What happened?
After software actualization my phone stuck on Mi logo for 36+hours.
What has been tried?
I manually unblocked bootloader and I tried several ROMs. Every time I had this error in MiFlash critical partition flashing is not allowed or partition flashing is not allowed. I tried to edit in TextEditor some files but with no success after all.
1. One thing I didn't do was disabling driver signature enforcements in windows. What is this needed for?
2. Is this kind of malfunction can be reported during warranty period? Who is responsible for making my phone unusable?
3. Which ROM would you recommend to stick with during my following flashing tryouts?
4. I am going to check all the USB cables. Might it help when I've got the "critical partition flashing is not allowed" error?
5. What causes this "critical partition flashing is not allowed" error?
6. I've got no deep flash cable and I'm at the end of the world, so it's very difficult to get one of these here. Should I start trying to get one anyway? Someone had the same issue and could resolve it this way?
7. What to do now guys? Any ideas? -> For now I'll be checking all the usb cables I can get my hands on.
I know that some of the answers can overlap, but I chose the questions intentionally. I've been researching and checking solutions for over a week now. I would like to have deeper understanding of what the heck is going on with my phone and its software. There are no service centers here which can help me (their workers have less knowledge than I have, a sad lol), so I am dependent on your knowledge and your good will.
Best Regards
Click to expand...
Click to collapse
What do you mean my manually unlocked the bootloader? Did you perform steps other than those in official guide?
1. Driver verification has to be disabled because mi flash has to install some drivers for mido.
2. Warranty isn't going to be valid here somehow.
3. Miui. Latest miui 9.5 fastboot rom.
4. Up and until your device is being recognised you don't need to change usb cable.
5. Probably driver verification?
6. No. It isn't required as of now.
7. For now perform disabling driver verification and try again.
MyNameIsRage said:
What do you mean my manually unlocked the bootloader? Did you perform steps other than those in official guide?
1. Driver verification has to be disabled because mi flash has to install some drivers for mido.
2. Warranty isn't going to be valid here somehow.
3. Miui. Latest miui 9.5 fastboot rom.
4. Up and until your device is being recognised you don't need to change usb cable.
5. Probably driver verification?
6. No. It isn't required as of now.
7. For now perform disabling driver verification and try again.
Click to expand...
Click to collapse
Thanks for advice!
Sorry for late reply. Lack of laptop, time and internet connection is a harsh hybrid
I've disabled driver verification and went on to minimal adb and fastboot. Command "adb devices" doesn't show any devices. And "adb reboot boatloader" gives error: no devices/emulaters found.
I've tried it on 3 different laptops including one with iOS. When I plug in my Redmi Note 4 SD every laptop beeps and only MiFlash detects a device. Tried out 4 different USB cables and 3 of 4 detected my Note 4.
Check the screenshots:
dropbox.com/s/u7xoewalgho9kh5/adb%20reboot%20boatloader.png?dl=0
dropbox.com/s/a782soi5aub2puf/ios%20device%20oem%20locked.png?dl=0
Sorry for cutting the link but couldn't post whole.
What do you mean my manually unlocked the bootloader? Did you perform steps other than those in official guide?
Click to expand...
Click to collapse
I tried the TEST POINT approach.
en.miui.com/thread-729246-1-1.html
What do you think MyNameIsRage?
Cheers
Hello all,
Anyone having the same problem was able to overcome it?
I'm still wishing to unblock my phone. Will the deep flash cable be of any help in this case?
Cheers!
PatchMe said:
Thanks for advice!
Sorry for late reply. Lack of laptop, time and internet connection is a harsh hybrid
I've disabled driver verification and went on to minimal adb and fastboot. Command "adb devices" doesn't show any devices. And "adb reboot boatloader" gives error: no devices/emulaters found.
I've tried it on 3 different laptops including one with iOS. When I plug in my Redmi Note 4 SD every laptop beeps and only MiFlash detects a device. Tried out 4 different USB cables and 3 of 4 detected my Note 4.
Check the screenshots:
dropbox.com/s/u7xoewalgho9kh5/adb%20reboot%20boatloader.png?dl=0
dropbox.com/s/a782soi5aub2puf/ios%20device%20oem%20locked.png?dl=0
Sorry for cutting the link but couldn't post whole.
I tried the TEST POINT approach.
en.miui.com/thread-729246-1-1.html
What do you think MyNameIsRage?
Cheers
Click to expand...
Click to collapse
Sorry for replying late. I see what you did there, and to be honest that wasn't really the correct steps.
First of all, in order to flash the rom, you should try to make sure that fastboot works. Boot into fastboot and check if device shows up. To do that execute
"fastboot devices" and if it returns some data then you are good to go for flashing fastboot rom. We'll go step wise. Try performing fastboot check and report if it works. Also if you have telegram you can contact me at @MyNameIsRage
MyNameIsRage said:
First of all, in order to flash the rom, you should try to make sure that fastboot works. Boot into fastboot and check if device shows up. To do that execute
"fastboot devices" and if it returns some data then you are good to go for flashing fastboot rom. We'll go step wise. Try performing fastboot check and report if it works. Also if you have telegram you can contact me at @MyNameIsRage
Click to expand...
Click to collapse
Ok, thanks!
I did "fast boot devices" and it shows the device.
dropbox.com/s/9qqpjdev31ssuw3/Zrzut%20ekranu%202018-09-29%20o%2014.40.00.png?dl=0
but still adb devices doesn't give any numbers back and flashing is impossible.
What now?
PatchMe said:
Ok, thanks!
I did "fast boot devices" and it shows the device.
dropbox.com/s/9qqpjdev31ssuw3/Zrzut%20ekranu%202018-09-29%20o%2014.40.00.png?dl=0
but still adb devices doesn't give any numbers back and flashing is impossible.
What now?
Click to expand...
Click to collapse
Now you should try mi flash. And possibly on a windows machine.
http://en.miui.com/thread-565784-1-1.html
MyNameIsRage said:
Now you should try mi flash. And possibly on a windows machine.
http://en.miui.com/thread-565784-1-1.html
Click to expand...
Click to collapse
My phone is in a bootloop. Can't do this.
2. Enable Developer options:- Go to About phone > tap MIUI version at least 7 times to activate the Developer options.
and neither installing VPN.
PatchMe said:
My phone is in a bootloop. Can't do this.
2. Enable Developer options:- Go to About phone > tap MIUI version at least 7 times to activate the Developer options.
and neither installing VPN.
Click to expand...
Click to collapse
Skip that part. Try as it is. Mi flash should detect your device. Jump straight to the part of flashing.
MyNameIsRage said:
Skip that part. Try as it is. Mi flash should detect your device. Jump straight to the part of flashing.
Click to expand...
Click to collapse
I did it on Mac (lack of windows laptop atm) and it said again "device oem locked". As in the screenshot I uploaded before.
PatchMe said:
I did it on Mac (lack of windows laptop atm) and it said again "device oem locked". As in the screenshot I uploaded before.
Click to expand...
Click to collapse
afaik mac won't work. You'll need a windows machine and mi flash tool.
MyNameIsRage said:
afaik mac won't work. You'll need a windows machine and mi flash tool.
Click to expand...
Click to collapse
Ok
Will do that in the next 24h and will report back.
Tried it all!
I tried to unlock boot loader via MiUnlock. Failed to "couldn't verify device" - unknown error (-1)
Same problem with trying to install ROM on windows as on MacBook.
I positively performed PIN TEST but couldn't install ROM. I am struggling with putting the device into fast boot mode after positively connecting it to windows pc with PIN TEST.
Any suggestions?
PS. I've sent info to xiaomi support as well.
Finally done it!
Hey guys!
I'm glad to tell you that after million tries with different ROMs and different approaches to PIN forcing i was able to reinstall my ROM. The working ROM for me was mido_global_images_V9.6.2.0.NCFMIFD_20180716.0000.00_7.0_global_228dc638d1
THANK YOU so much for help. You kept me going and finally i was able to overcome the obstacle
I hope I can be of help when you need it.
Take care,
Cheers
Edit: PS. I've done it on Mac

[HELP] Red Light Blinking, [init:storage:fail]

Conditon :
Can't boot up into anything (Fastboot, recovery)
No Mi Logo
No Vibration
*Phone goes into EDL WITHOUT having to touch the pins on the mobo*
So, my phone was working like 3 days ago, until today it just went to "Red Light Blinking and Nothing Else", So i searched around the internet and basically on YT i got videos like "Heating up the Power IC Fixes this" but i really didn't wanted to try it so i went again and thought maybe i need to flash the Phone so i downloaded the "Global Stock Rom" so i then took the back cover off of my phone and plugged it the USB Cable and i saw "QualComm HS-USB QLoader 9008" which is right i guess and tried to flash it via MiFlash Tool. And indeed i got error BUT in sequence.
1st one was "cannot recieve hello packet"
which i solved by reconnecting my phone
Then
2nd "Object reference not set to an instance of an object"
I only got this ONCE, searched around again and found out that it's something with WRONG ROM type. So i redownloaded the ROM and got the third error.
3rd "init:storage fail" Which i again searched around and found this could be related to "EMMC Fail" which i have no idea how it went there.
So please if anyone have any info or can lend me some help then please let me know as soon as you can.
Thanks in advance.
(I also have a Note 4 (mido) in the same condition (Red Light Blinking and Nothing Else, it DOEN"T EVEN go in EDL mode)
PRemBh0i said:
Conditon :
Can't boot up into anything (Fastboot, recovery)
No Mi Logo
No Vibration
*Phone goes into EDL WITHOUT having to touch the pins on the mobo*
So, my phone was working like 3 days ago, until today it just went to "Red Light Blinking and Nothing Else", So i searched around the internet and basically on YT i got videos like "Heating up the Power IC Fixes this" but i really didn't wanted to try it so i went again and thought maybe i need to flash the Phone so i downloaded the "Global Stock Rom" so i then took the back cover off of my phone and plugged it the USB Cable and i saw "QualComm HS-USB QLoader 9008" which is right i guess and tried to flash it via MiFlash Tool. And indeed i got error BUT in sequence.
1st one was "cannot recieve hello packet"
which i solved by reconnecting my phone
Then
2nd "Object reference not set to an instance of an object"
I only got this ONCE, searched around again and found out that it's something with WRONG ROM type. So i redownloaded the ROM and got the third error.
3rd "init:storage fail" Which i again searched around and found this could be related to "EMMC Fail" which i have no idea how it went there.
So please if anyone have any info or can lend me some help then please let me know as soon as you can.
Thanks in advance.
(I also have a Note 4 (mido) in the same condition (Red Light Blinking and Nothing Else, it DOEN"T EVEN go in EDL mode)
Click to expand...
Click to collapse
So u cant successfully flash rom using edl mode??
What windows pc u r using 32bit or 64 bit ?
Black_Stark said:
So u cant successfully flash rom using edl mode??
What windows pc u r using 32bit or 64 bit ?
Click to expand...
Click to collapse
I have a 64 Bit Windows 10 with drivers installed, it just get stuck on "init Storage : Fail" after 7 seconds.
I have attached a .log.
PRemBh0i said:
I have a 64 Bit Windows 10 with drivers installed, it just get stuck on "init Storage : Fail" after 7 seconds.
I have attached a .log.
Click to expand...
Click to collapse
Try window driver signature disabled.
Try with diffrent usb ports.
Redownload fastboot rom. Extract it and try.
If still getting storage error then Emmc is dead. Repair it or buy new phone.
Black_Stark said:
Try window driver signature disabled.
Try with diffrent usb ports.
Redownload fastboot rom. Extract it and try.
If still getting storage error then EmmC is dead. Repair it or buy new phone.
Click to expand...
Click to collapse
I've tried a different port and re-downloaded the ROM, but i haven't tried to "Disable Driver Enforcement" yet, But if the EMMC is dead then how do i deal with it? And how does it dies? I was using it like 3 days ago with no problem and suddenly it's just gone.
PRemBh0i said:
I've tried a different port and re-downloaded the ROM, but i haven't tried to "Disable Driver Enforcement" yet, But if the EMMC is dead then how do i deal with it? And how does it dies? I was using it like 3 days ago with no problem and suddenly it's just gone.
Click to expand...
Click to collapse
Its phone . not human body which comes with 80 yrs warranty.
If u r gamer then its faster. It has limited write cycles. Disk can go corrupt and dead. How old u r using phone?
Black_Stark said:
Its phone . not human body which comes with 80 yrs warranty.
If u r gamer then its faster. It has limited write cycles. Disk can go corrupt and dead. How old u r using phone?
Click to expand...
Click to collapse
Okay i understand nothing lasts forever but still there could've been some signs that it might be die some time ,i also have a Moto E (1st Gen) it even has gone through water submersion but still works just as fine but recently it's batter died to i decided to lay it in his grave, but alas it's gone, So i just needed to know if you could let me know What can i do to fix the EmmC? Like any tutorials or something? I also have a Note 4 with the same problem as this. Or maybe i'll just never buy a Mi phone again
But still thanks for your time.
PRemBh0i said:
Okay i understand nothing lasts forever but still there could've been some signs that it might be die some time ,i also have a Moto E (1st Gen) it even has gone through water submersion but still works just as fine but recently it's batter died to i decided to lay it in his grave, but alas it's gone, So i just needed to know if you could let me know What can i do to fix the EmmC? Like any tutorials or something? I also have a Note 4 with the same problem as this. Or maybe i'll just never buy a Mi phone again
But still thanks for your time.
Click to expand...
Click to collapse
Its not harddisk which will give u alert or noisy sound before it dies. Its Sd. Thats the demerits of solid drive.
Emmc means embedded multi media card or disk. Its cant be repaired. It can be replaced in service center. May be.
But better buy new phone.
Nothing wrong in buying xiaomi phone.
Most problems happen when u stay on miui and keep doing OTA update for entire life which creates lots of bugs and issues.
U must do factory reset once in a six months. Or flash fastboot rom clean all flash using computer is best to keep phone healthy. Its not true that stock rom is always best. Sometimes its bloated and hogs ur phone like hell like miui.
So installing Custom debloated roms are best here to keep rom smooth running and increasing phones health.
Only upgrading using OTA is not good. Userdata and internal sd must be wiped after few months to clear bugs.

Question Broke my Sony Xperia 1 III trying to root it. Any help is gratefully received

Hi guys
I followed this guide for unlock bootloader and install magisk: https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4344371/
I don't blame the author of the guide, it is my device, my responsibility, my decision to attempt this. My fault.
Everything was going great, I unlocked the bootloader successfully and my device wiped and rebooted. It boot back into android, I turn off, go to fastboot mode, and try to flash magisk img file I made earlier in the guide. It says success, then last step of the guide is to wipe with fastboot -w. This fails, says cannot wipe metadata. Reboot, now my phone says "your device is corrupted and cannot be trusted and will not boot"
No idea what to do here, so i try to use Xperia Companion to restore. But it refuses because it detect bootloader is unlocked. Now I try to use NewFlasher to flash firmware from XperiFirm, this starts off fine but then NewFlasher reaches this point
"Extracting sparse chunk super.040"
"Uploading sparse chunk C:\temp\xperiafirmware\flash_sesson_super.0.40"
"download:03b4c9c"
"ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress
I have tried to do this with another computer, I have tried 2 other USB cables, I have tried another firmware (originally tried the latest version with open carrier but also tried with carrier specific one) I am now running out of ideas to try.
I can get to fastboot mode or flash mode, but if I try to boot OS it says "your device is corrupted and cannot be trusted and will not boot"
Any help or a point in the right direction would be much appreciated
Thank you so much in advance
Last week that happened to me. As long as you can go to fastboot you're good. First is relock the bootlaloader via fastboot then repair it using xperia companion. Or if you can download the firmware via xperifirm then flash it via flasher.
Also make sure that the PC your using has both an Intel CPU or AMD CPU and a full windows install not that cheap windows store only crap..but one you can actually install windows .exe files and make sure you have installed the Xperia drivers by turning off driver verification...o tried without and my 2 in 1 couldn't find my phone for Xperia companion nor the other flashing tool...
Thank you @Mangtas_666 @Ainz_Ooal_Gown I have no idea why but I just couldn't flash the UK firmware, tried 2 versions but neither would flash with NewFlasher. kept getting these timeout errors. But then i randomly decide to try the US firmware (XQ-BC62 instead of XQ-BC52) and it worked 1st try. My phone is up and running again!
The strangest part, when it connect to the internet and I apply all my UK settings, it somehow change back to XQ-BC52 on its own. It is detected as such in "about phone" now even though I didn't re-install firmware since fixing it with the US one. Oh well, i'm not going to complain, I'm just happy it's fixed. Thanks for replying
marshedpotato said:
Thank you @Mangtas_666 @Ainz_Ooal_Gown I have no idea why but I just couldn't flash the UK firmware, tried 2 versions but neither would flash with NewFlasher. kept getting these timeout errors. But then i randomly decide to try the US firmware (XQ-BC62 instead of XQ-BC52) and it worked 1st try. My phone is up and running again!
The strangest part, when it connect to the internet and I apply all my UK settings, it somehow change back to XQ-BC52 on its own. It is detected as such in "about phone" now even though I didn't re-install firmware since fixing it with the US one. Oh well, i'm not going to complain, I'm just happy it's fixed. Thanks for replying
Click to expand...
Click to collapse
No problem fam, glad it got sorted out

Categories

Resources