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
Related
A few days ago my watch restarted on it's own and never got past the startup..which isn't that unusual, it'd happened a few times. No big deal just reset it with the button on the back. I tried that and again an endless loop. I tried searching for any help in this situation and the only lead I found was to reset and power it down through the boot menu and let it sit for a few minutes...but didn't matter. I've wiped and reset from the boot menu, hoping it might do something to get it past the startup, but no luck yet. I didn't open up the developer options and unlock anything...so I don't believe I could try anything from the computer right? Is there any other recourse to take or am I completely hosed?
JRSly said:
A few days ago my watch restarted on it's own and never got past the startup..which isn't that unusual, it'd happened a few times. No big deal just reset it with the button on the back. I tried that and again an endless loop. I tried searching for any help in this situation and the only lead I found was to reset and power it down through the boot menu and let it sit for a few minutes...but didn't matter. I've wiped and reset from the boot menu, hoping it might do something to get it past the startup, but no luck yet. I didn't open up the developer options and unlock anything...so I don't believe I could try anything from the computer right? Is there any other recourse to take or am I completely hosed?
Click to expand...
Click to collapse
You don't need developer options to do "fun" things from the boot menu. Just an unlocked bootloader.
I have a TWRP backup somewhere, so if you have a borked system, you can always flash (or better yet, boot) TWRP (make a backup of your broken), push the backup file folder to your watch (without overwriting the broken backup), and then restore mine.
Last thing to do is a factory reset to clean up any left over garbage. Hope this helps.
But isn't Developer Options necessary to allow that? It lets you turn on ADB Debugging which would then let you get on the computer and unlock the bootloader?
Or is there an alternate way to go about things...can I unlock the bootloader from the boot menu? I've only rooted a couple phones, with a lot of careful reading and reviewing of these forums...I'm not very knowledgeable.
JRSly said:
But isn't Developer Options necessary to allow that? It lets you turn on ADB Debugging which would then let you get on the computer and unlock the bootloader?
Or is there an alternate way to go about things...can I unlock the bootloader from the boot menu? I've only rooted a couple phones, with a lot of careful reading and reviewing of these forums...I'm not very knowledgeable.
Click to expand...
Click to collapse
Fastboot is independent of ADB, so you can unlock the bootloader from the boot menu. That is the way to unlock bootloader 90+% of the time.
Just need to issue these commands (like you would ADB) :
fastboot devices
fastboot oem unlock
...and then complete the on-screen (watch) confirmation. Hope this helps.
Sent from my ASUS_Z00AD
OfficerJimLahey said:
Fastboot is independent of ADB, so you can unlock the bootloader from the boot menu. That is the way to unlock bootloader 90+% of the time.
Just need to issue these commands (like you would ADB) :
fastboot devices
fastboot oem unlock
...and then complete the on-screen (watch) confirmation. Hope this helps.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
All right, my new problem is that the computer doesn't recognize the watch. When I plug it in it only appears as an unknown device and there's an error about the device having malfunctioned. Trying to install drivers despite the error leads nowhere, Windows says that the drivers present on the computer are up-to-date. So with it being an unknown device, I can't communicate with the watch from the command prompt.
Remove the drivers from Device Manager (check delete driver), connect your device again to the computer then reinstall the drivers.
MihaiSG said:
Remove the drivers from Device Manager (check delete driver), connect your device again to the computer then reinstall the drivers.
Click to expand...
Click to collapse
No luck, I'd tried that a couple times before...just no progress, still sees it as an unknown device and trying to force install the drivers does nothing. It says the existing drivers are up to date.
I'm getting more and more discouraged. I can't seem to make any progress. I'm looking into sending it away for repair even though, of course, it's about two months out of the warranty.
You are not removing the drivers correctly, make sure that you have this option checked and try again:
http://www.sevenforums.com/tutorials/77614-device-manager-hidden-devices.html
MihaiSG said:
You are not removing the drivers correctly, make sure that you have this option checked and try again:
http://www.sevenforums.com/tutorials/77614-device-manager-hidden-devices.html
Click to expand...
Click to collapse
Anything more I should be doing? Everything mentioning Android or ADB is removed. I'd never plugged the watch in before and installed drivers, so there's nothing from the watch to delete. But still the same thing, Windows only sees it as a Unknwon Device under USB controllers and sees no need to update drivers when I try, since it doesn't seem to see it as a watch or Android device of any sort.
Are you sure that you have installed the correct drivers? What is the hardware id?
MihaiSG said:
You are not removing the drivers correctly, make sure that you have this option checked and try again:
http://www.sevenforums.com/tutorials/77614-device-manager-hidden-devices.html
Click to expand...
Click to collapse
MihaiSG said:
Are you sure that you have installed the correct drivers? What is the hardware id?
Click to expand...
Click to collapse
I think so? I'm far from an expert but I've messed with a handful of phones and tablets in the last five years and never had issues with drivers I didn't sort out fairly easily. I downloaded the official Google USB driver, I tried the LG Watch Tool which installs the Universal ADB driver.The LG Watch then finds no devices.
I'm a bit ignorant, what hardware ID do you refer to? Of the driver?
Of the device.
Here is a guide:
http://www.makeuseof.com/tag/how-to-find-unknown-device-drivers-by-their-vendor-device-id/
Can you post some screenshots from device manager?
MihaiSG said:
Of the device.
Here is a guide:
http://www.makeuseof.com/tag/how-to-find-unknown-device-drivers-by-their-vendor-device-id/
Can you post some screenshots from device manager?
Click to expand...
Click to collapse
Device Manager wasn't much help for finding the IDs, but I tried using USBDeview and it's reporting something as Android Bootloader Interface, which I'll have to assume is the watch. The vendor ID is 18D1 and the product ID is 4EE0. And here is a screen cap of the entry in the Device Manager that I've been seeing. If there's anything more specific in the device's properties that could be insightful, let me know.
Your device is seen as an unknown device. My only advice is to try on another PC your last working drivers and maybe it will work.
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!!
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.
Hope someone can help me.
My Redmi Note 5 is stucked n Mi-Recovery 3.0 screen with 3 options: Reboot - Wipe data - Connect with MiAssistant. and continue to go in loop until the battery will be zero.
I was try everything to get connected, and flash again the firmware but no result, first and I think main problem is that my PC cannot see the phone, then with all SW I'm sure I can try to re-install everything and recover back my phone. Data is not a problem since I have all backup in MI account and Google account. I hope some one expert can help me to solve this unpleasant situation.
Is already out of warranty and send to MI service cost 36 EURO just for checking and then more than 90 EURO for repairing, is not worthing the cost.
P.S. I downloaded and try with ADB; Flash; MI Tool, USB debug etc..
I'm desperate mother of two kids and I need this phone, now I'm using a very old one.
Thank you
You try mi flash tool, but the phone can not recognized? Fastboot mode working? When yes, maybe Windows install the wrong driver. Look in the device manager and install it when it the wrong one manual
Hi Joke, thank you for your interest in my problem.
You can see the screenshot I just made it and I was trying to connect the phone, I installed any diver as possible but the PC is not recognize it.
joke19 said:
You try mi flash tool, but the phone can not recognized? Fastboot mode working? When yes, maybe Windows install the wrong driver. Look in the device manager and install it when it the wrong one manual
Click to expand...
Click to collapse
matsalleh said:
Hi Joke, thank you for your interest in my problem.
You can see the screenshot I just made it and I was trying to connect the phone, I installed any diver as possible but the PC is not recognize it.
Click to expand...
Click to collapse
And what's with the windows device manager? U look inside
I have an update, now I can flash the Rom using Xiaomi MI tool V2. Then after finish message say that installation was successfully, but when I restart the phone is going back again on same position with Mi-Recovery 3.0. I noted that if I use MI Phone Assistant in certain conditions I can see the phone as "HD" in my PC. There is anything I can do to revive my phone?
I hope someone can help me. Thanks
I am not responsible for bricked devices, dead SD cards, etc!
I have not tested the global unlock, Global version unlock thread.
Make sure you make backups before unlocking the bootloader, as this operation will wipe all user data and apps.
Make sure your system version is the official and latest one.
Requirements
- 60% charge on the phone
- PC and usb data cable
- Installed fastboot and proper drivers on your PC
1. Install Deep Testing Apk attached in this post.
2. Click on the Apply Now button in order to get approval for bootloader unlock.
3. Check the status after apply using the Query Approval Status.
4. If you get an error, force stop the application, change your device language to Chinese and try again (if someone can post screenshot of what to tap, I would update this post)
5. Once the approval is done, tap Start Testing button, this will reboot your device in the bootloader.
6. Last chance, make backups at this point otherwise your data is gone.
7. Run command
Code:
fastboot flashing unlock
8. Done, you can now reboot into system normally
If I missed anything, kindly comment and I'll update OP.
myogui said:
I am not responsible for bricked devices, dead SD cards, etc!
Make sure you make backups before unlocking the bootloader, as this operation will wipe all user data and apps.
1. Install Deep Testing Apk attached in this post.
2. Click on the Apply Now button in order to get approval for bootloader unlock.
3. Check the status after apply using the Query Approval Status.
4. If you get an error, force stop the application, change your device language to Chinese and try again (if someone can post screenshot of what to tap, I would update this post)
5. Once the approval is done, tap Start Testing button, this will reboot your device in the bootloader.
6. Last chance, make backups at this point otherwise your data is gone.
7. Run command
Code:
fastboot flashing unlock
8. Done, you can now reboot into system normally
If I missed anything, kindly comment and I'll update OP.
Click to expand...
Click to collapse
Hi myogui
Do you have the firmware for RMX3300_11_A.19?
Do I run that command from the phone? When I start deep testing and phone reboots I only have the options to start, power off, recovery, and restart bootloader.
I can't get this to work on A19 firmware no matter what I do. Says not supported on this model even though I have the correct RMX3300 so I am going to upgrade to A20 and see if it works
Nope upgrading to A20 doesn't work either. Always get failed to submit in either english or chinese.
wildlime said:
Nope upgrading to A20 doesn't work either. Always get failed to submit in either english or chinese.
Click to expand...
Click to collapse
It did take a couple of tries to get it to work but still that was done in like 10-15 minutes. You could try to factory reset the phone first but if it's still doesn't work for you you'll be stuck re-installing everything on your phone.
wildlime said:
Nope upgrading to A20 doesn't work either. Always get failed to submit in either english or chinese.
Click to expand...
Click to collapse
Same problem. It work for me trying all Chinese languages (simple and another two). It seems stuck for like 30 minutes, then idk why I've exit and re enter the app and it worked.
i cant get my computer to recogize the phone when in bootloader. Anyone else run into this? i ran the fastboot command with the phone plugged in but its still waiting for a device to connect
Bnblare said:
i cant get my computer to recogize the phone when in bootloader. Anyone else run into this? i ran the fastboot command with the phone plugged in but its still waiting for a device to connect
Click to expand...
Click to collapse
Try another USB cable and make sure you are in the folder where fastboot program is.
Bnblare said:
i cant get my computer to recogize the phone when in bootloader. Anyone else run into this? i ran the fastboot command with the phone plugged in but its still waiting for a device to connect
Click to expand...
Click to collapse
Download the attached file, then install manually the driver, select the android_winusb.inf file.
myogui said:
Try another USB cable and make sure you are in the folder where fastboot program is.
Click to expand...
Click to collapse
hacls said:
Download the attached file, then install manually the driver, select the android_winusb.inf file.
Click to expand...
Click to collapse
Thanks! This is definitely a driver issues.
I have an RMX 3300 Chinese model. Build number is RMX3300_11_A.20. When I run the deeptesting_RMX3300.apk it says "Failed to submit application. This phone model does not support deep testing. "
robert3892 said:
I have an RMX 3300 Chinese model. Build number is RMX3300_11_A.20. When I run the deeptesting_RMX3300.apk it says "Failed to submit application. This phone model does not support deep testing. "
Click to expand...
Click to collapse
I finally managed to get past this point. But when I go to step 7 it says waiting for device. I'm using the same USB cable that works for ADB. Might try another cable tomorrow and/or another usb port.
Tried different cables and usb ports. Still stuck on 'waiting for device'
robert3892 said:
I finally managed to get past this point. But when I go to step 7 it says waiting for device. I'm using the same USB cable that works for ADB. Might try another cable tomorrow and/or another usb port.
Click to expand...
Click to collapse
Is a secret how you managed that?
criszz said:
Is a secret how you managed that?
Click to expand...
Click to collapse
I believe that the servers which grant permission for the deep testing app are busy at different times of the day. I simply retried the app during different times of the day until it worked. I still am working on a complete solution
robert3892 said:
Tried different cables and usb ports. Still stuck on 'waiting for device'
Click to expand...
Click to collapse
Fixed this issue finally by installing the android bootloader usb drivers
OK I have this working. I believe I will now need to relock the bootloader
robert3892 said:
OK I have this working. I believe I will now need to relock the bootloader
Click to expand...
Click to collapse
Don't relock the bootloader using the ADB lock command. This will brick your device!
Everithing ok, thanks man.