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.
Related
I can't for the life of me get adb to recognize my max. It's Verizon, H-boot 2.46. Trying to root and unlock. I've tried everything here....nothing. A little help please.
Only thing I can suggest, because it's happened to me, is to make sure you have the correct, most current device drivers loaded on your PC.
Sent from my HTC6525LVW using Tapatalk
they are correct up to date and most current.
HellRayzer said:
I can't for the life of me get adb to recognize my max. It's Verizon, H-boot 2.46. Trying to root and unlock. I've tried everything here....nothing. A little help please.
Click to expand...
Click to collapse
Are you unlocked, s-off, and rooted? Do you have developer options activated on your phone? Please explain what you´ve done up till now.
What happens when you type adb reboot. Does it start and not find it or come back with command not recognized?
Sent from my HTC6525LVW using xda app-developers app
i was having issues myself. then I found this thread and things worked again. http://forum.xda-developers.com/showthread.php?t=2588979
it doesn't find anything. I haven't been able to root s-off or anything because adb cant find my device. Do I need adb files in rumrunner folder on C drive to make it recognize it and work or what the hell am I doing wrong? I have rooted and s-offed every htc device I have ever owned...this one isn't working out. It's showing as a portable media player not android device. In the past I remember when I connected the usb I had the option to select media storage or connect as android.
HellRayzer said:
it doesn't find anything. I haven't been able to root s-off or anything because adb cant find my device. Do I need adb files in rumrunner folder on C drive to make it recognize it and work or what the hell am I doing wrong? I have rooted and s-offed every htc device I have ever owned...this one isn't working out. It's showing as a portable media player not android device. In the past I remember when I connected the usb I had the option to select media storage or connect as android.
Click to expand...
Click to collapse
my rumrunner folder was still in my downloads folder no where near my adb files and everything worked ok for me. also my Max shows up as a media device also but adb/fastboot still working fine. did you try to reinstall your adb with the link I provided in the above post, its the only thing that helped me when I was having pretty much the same problem as you.
you may also need to unlocked dev tools in your settings... have you done that yet
Where and how do you unlock developer tools...haven't found that under anything in the settings?
HellRayzer said:
Where and how do you unlock developer tools...haven't found that under anything in the settings?
Click to expand...
Click to collapse
Enter Settings, then scroll down to about... pick "Software Information" -- then "More" --- Then press the "Build" 8 times fast. You´ll then have access to the developer tools.
Well thanks for the help. still can't get anything to work, guess this will be the first device I've owned that will never be rooted unless I find something that tells me what to put where and what to do.
HellRayzer said:
Well thanks for the help. still can't get anything to work, guess this will be the first device I've owned that will never be rooted unless I find something that tells me what to put where and what to do.
Click to expand...
Click to collapse
When you type in adb devices, can you see your seriel number?
RayHeath said:
When you type in adb devices, can you see your seriel number?
Click to expand...
Click to collapse
no. it says list of devices, then it's blank.
HellRayzer said:
no. it says list of devices, then it's blank.
Click to expand...
Click to collapse
Ok, I´m not sure what you time zone is, but I can help you tomorrow. It´s 10pm here right now, and I´m gonna hit the hay soon. When you´re online tomorrow, pm me. I´ll log in, and we´ll start.
Hey relax bud, do me a favor and PM and I will help you out with everything and getting your phone to be recognized by dab and fast boot and make sure you properly s-off unlock and root if that's what you are trying to accomplish! Hit me up, I have nothing going on tonight so I can jump right in to it with you right away
HellRayzer said:
no. it says list of devices, then it's blank.
Click to expand...
Click to collapse
Have Win XP or server 2003?!?
This: http://forum.xda-developers.com/showthread.php?p=49045175
Don't know if you guys ever got this issue solved or not. I'm having the same issue S-on, cannot get adb devices command to recognize my t6spr for the life of me. on Hboot 2.46, it will detect the USB device malfunction if I put the device in fastboot mode, but thats about it. Device manager shows Unknown USB (Device Descriptor Request Failed). Tried the KB update for devices that fail enumeration on Windows 8.1 for x64 but the update package said my system is not affected so that never installed. Tried the alternative miniadb pakage previously mentioned but didnt seem to have an affect installing fastboot, adb, and drivers, across the system universally. Just not having any luck apparently. I guess I could just sell the phone Tampered and Unlocked haha with no fingerprint scanner functionality, flash ViperRom or some other stock look alike ROM. Was just really hoping to go back completely stock. At one point it time I was trying different PCs to see if it was just a system issue for me. Occasionally it seemed like if I let it sit in Fastboot AC it would eventually get detected and flip over to Fastboot USB long enough for me to push a couple commands to the phone. I have the right RUU but it dosent do me any good if the computer cant see the phone haha. Now no computer seems to recognize it. It all seemed to happen after I tried to S-Off the device with Firewater's method. Idk if I bricked something because it never worked or changed a CID or some other ID to where the USB isnt recognizable, but all I can get this phone to do is take an electric current from the USB, lol thats about it. I thought I had it fixed enough to where I knew what to do if i absolutely needed to get fastboot to recognize the phone but now, nothing.
Just a curiousity question here....a bad usb cable can produce this also...read through posts didnt see anyone trying a new cable...
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.
Please help me !
my phone is kiw-l21
I download the application to operate the network in a telephone because they do not work and says there is no SIM card
This application is called GSII_Repair
He wrote in description it's only for Galaxy S 2, but I did not watch out and used it
after that my phone has been restarted in black screen& nothing work no light no led
buttons dont not respond to any thing
& I looked for it in forums & I did not find a solution Please help me
SiZeN said:
Please help me !
my phone is kiw-l21
I download the application to operate the network in a telephone because they do not work and says there is no SIM card
This application is called GSII_Repair
He wrote in description it's only for Galaxy S 2, but I did not watch out and used it
after that my phone has been restarted in black screen& nothing work no light no led
buttons dont not respond to any thing
& I looked for it in forums & I did not find a solution Please help me
Click to expand...
Click to collapse
Have you tried adb to see if you can get into recovery. Should see if you can start over with ROM wipe wise.
press and hold all the three buttons after having placed a full stock rom of your model under dload folder of your sd card
thilak devraj said:
press and hold all the three buttons after having placed a full stock rom of your model under dload folder of your sd card
Click to expand...
Click to collapse
Can you explain to me in detail more than that, becaue i didnt know how can i do that
GrimReaper24 said:
Have you tried adb to see if you can get into recovery. Should see if you can start over with ROM wipe wise.
Click to expand...
Click to collapse
i,m tried that but nothing happen its dead
but when i connect it to laptop the driver called (qhsub_bulk)
any information about it ?
SiZeN said:
i,m tried that but nothing happen its dead
but when i connect it to laptop the driver called (qhsub_bulk)
any information about it ?
Click to expand...
Click to collapse
You may, I repeat MAY be able to use ADB Fastboot after extracting the boot and recovery images. I believe there's a thread here that may help you out.
Absolute worst case you can google other solutions, but you are definitely hard bricked...and you may have no choice but to RMA the phone. I would connect the phone to your computer for about 15 mins or so to put charge on battery then try "ADB Devices" command to see if ADB picks it up. If so you may be in luck and can use the thread mentioned to get the phone back to stock or at least to the point where you can go back and fastboot flash Recovery TWRP and then install a ROM of your choice. Again I emphasize you may be able to recover the phone from hard brick.
IF the above worked (and I can not guarantee it will) you should be able to Fastboot flash recovery TWRP or proceed on to the EMUI recovery.
Good luck! :fingers-crossed:
Wolfhawke said:
You may, I repeat MAY be able to use ADB Fastboot after extracting the boot and recovery images. I believe there's a thread here that may help you out.
Absolute worst case you can google other solutions, but you are definitely hard bricked...and you may have no choice but to RMA the phone. I would connect the phone to your computer for about 15 mins or so to put charge on battery then try "ADB Devices" command to see if ADB picks it up. If so you may be in luck and can use the thread mentioned to get the phone back to stock or at least to the point where you can go back and fastboot flash Recovery TWRP and then install a ROM of your choice. Again I emphasize you may be able to recover the phone from hard brick.
IF the above worked (and I can not guarantee it will) you should be able to Fastboot flash recovery TWRP or proceed on to the EMUI recovery.
Good luck! :fingers-crossed:
Click to expand...
Click to collapse
I want to thank you very much to try to help me, but nothing useless
Well, I opened my door and the wide range of information for how to fix it, but nothing happened after all attempts
I guess I will not be able this and thank you again for your assistant & kindness
Wolfhawke said:
You may, I repeat MAY be able to use ADB Fastboot after extracting the boot and recovery images. I believe there's a thread here that may help you out.
Absolute worst case you can google other solutions, but you are definitely hard bricked...and you may have no choice but to RMA the phone. I would connect the phone to your computer for about 15 mins or so to put charge on battery then try "ADB Devices" command to see if ADB picks it up. If so you may be in luck and can use the thread mentioned to get the phone back to stock or at least to the point where you can go back and fastboot flash Recovery TWRP and then install a ROM of your choice. Again I emphasize you may be able to recover the phone from hard brick.
IF the above worked (and I can not guarantee it will) you should be able to Fastboot flash recovery TWRP or proceed on to the EMUI recovery.
Good luck! :fingers-crossed:
Click to expand...
Click to collapse
I want to thank you very much to try to help me, but nothing useless
Well, I opened my door and the wide range of information for how to fix it, but nothing happened after all attempts
I guess I will not be able this and thank you again for your assistant & kindness
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
Hello.
I was trying to install a treble rom on my p20 lite and suddenly after flashing i needed to flash stock recovery to make the stock wipes.
I did.
The rom started but with no keyboard. I couldnt pass google part to get to the rom menu.
Ok.
I decided to flash it again.
I did. But this time, the rom never started and i was with stock erecovery, so couldnt flash again.
I went to flash twrp but FRP is LOCKed. Bootloader unlocked, obviously. And bc of that i cant flash ANYTHING.
Tried to flash system, twrp, anything. I cant. Says FRP lock.
Tried to lock bootloader and relock again: I cant. It says it needs to unlock FRP before.
Tried DC PHOENIX, didn't work on my p20.
Scrolled all google and xda for help, nothing.
Tried erecovery stock rom installation. It downloads the files but never installs, i've spent 5 hours waiting for it to go off the 0%. Nothing happens.
Already made erecovery wipe data/cache. Nothing.
Can someone please help me?
Hi there
Can you tell what's your build number if you already knew before this happened?
Also, right now your only hope is your Stock Recovery so let's focus on that:
Please try to download and install the official ROM via the eRecovery a couple of times and connect it to the best Wifi you have.
Do you have bootloader "unlocked" or "locked" right now?
FRP is locked so no changes possible yup.
If you have your bootloader "locked" not "relocked" you have warranty and you can send it to a customer repair center and they can solve it for you.
With the methods we know it's pretty much impossible, altough try this via fastboot command line:
fastboot erase config
then
fastboot reboot
If this does not do it then try with DC-Unlocker software via this link https://www.dc-unlocker.com/huawei-android-phone-frp-unlock
Sorry for insisting,
Best of hopes,
AS
ars_chelsea said:
Hi there
Can you tell what's your build number if you already knew before this happened?
Also, right now your only hope is your Stock Recovery so let's focus on that:
Please try to download and install the official ROM via the eRecovery a couple of times and connect it to the best Wifi you have.
Do you have bootloader "unlocked" or "locked" right now?
FRP is locked so no changes possible yup.
If you have your bootloader "locked" not "relocked" you have warranty and you can send it to a customer repair center and they can solve it for you.
With the methods we know it's pretty much impossible, altough try this via fastboot command line:
fastboot erase config
then
fastboot reboot
If this does not do it then try with DC-Unlocker software via this link https://www.dc-unlocker.com/huawei-android-phone-frp-unlock
Sorry for insisting,
Best of hopes,
AS
Click to expand...
Click to collapse
Hey, thanks for the answer.
My build number (ane-lx3 c605 b149)
I tried for like 10 times already to install the firmware from erecovery but it refuses to leave the 0% when installing... Ive waited more than 5 hours already.
When trying these fastboot command lines, i got this: https://imgur.com/a/hrSB8iK
Dc also didnt worked for me, i think it doesnt support my phone model?
Bc i can't find it in the list of phone model in the software also tried with similar and doesnt work.
My bootloader is unlocked, i guess warranty wont solve my problem bc of that :crying:
Thanks again for tryna help!
you need sd card
download this file: https://androidhost.ru/cBe
unzip this file, inside software folder are dload folder, coppy that to sd card
put sd card in phone
pres vol+ and vol- and power button (need atlest 50% batery)
give a try.
Arnys said:
you need sd card
download this file: https://androidhost.ru/cBe
unzip this file, inside software folder are dload folder, coppy that to sd card
put sd card in phone
pres vol+ and vol- and power button (need atlest 50% batery)
give a try.
Click to expand...
Click to collapse
He/She does need a micro sd card adapter for that to connect to the pc or use it on another phone and then copy the files.
Yeah I forgot about that I guess XD
Cheers,
AS
ars_chelsea said:
He/She does need a micro sd card adapter for that to connect to the pc or use it on another phone and then copy the files.
Yeah I forgot about that I guess XD
Cheers,
AS
Click to expand...
Click to collapse
Arnys said:
you need sd card
download this file: https://androidhost.ru/cBe
unzip this file, inside software folder are dload folder, coppy that to sd card
put sd card in phone
pres vol+ and vol- and power button (need atlest 50% batery)
give a try.
Click to expand...
Click to collapse
Thank you, guys.
I tried this method just now but after a time with EMUI logo in the screen it said software install failed!
I guess im really lost. :crying:
fcknumb said:
Thank you, guys.
I tried this method just now but after a time with EMUI logo in the screen it said software install failed!
I guess im really lost. :crying:
Click to expand...
Click to collapse
Hey
Did you try the official guide of @Merlin_99?
If not check his thread here: https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
That's the official way to do it
Cheers,
AS
ars_chelsea said:
Hey
Did you try the official guide of @Merlin_99?
If not check his thread here: https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
That's the official way to do it
Cheers,
AS
Click to expand...
Click to collapse
Thanks for your reply and still tryna help me.
As i see, the only thing i didnt do from the official guide is this part:
"Finally, enter to the project menu from dialer typing *#*#2846579#*#* ==> Software Upgrade ==> SdCard Upgrade."
That i cant do cause my phone is systemless and i cant turn it on to use dialer :crying:
fcknumb said:
Thanks for your reply and still tryna help me.
As i see, the only thing i didnt do from the official guide is this part:
"Finally, enter to the project menu from dialer typing *#*#2846579#*#* ==> Software Upgrade ==> SdCard Upgrade."
That i cant do cause my phone is systemless and i cant turn it on to use dialer :crying:
Click to expand...
Click to collapse
Okay then.
It should work though did you put the dload folder into the root your sd card and then power on button + Volume buttons at the same time while powering on?
Cheers,
AS
ars_chelsea said:
Okay then.
It should work though did you put the dload folder into the root your sd card and then power on button + Volume buttons at the same time while powering on?
Cheers,
AS
Click to expand...
Click to collapse
Right bae, its like that into my sdcard: 1. http://prntscr.com/lx74xt 2. http://prntscr.com/lx7im7
And yes, i did pressed power and + - volume buttons at same time!
Thank you for not giving up.
fcknumb said:
Right bae, its like that into my sdcard: 1. http://prntscr.com/lx74xt 2. http://prntscr.com/lx7im7
And yes, i did pressed power and + - volume buttons at same time!
Thank you for not giving up.
Click to expand...
Click to collapse
Hi again
This is really weird... This one should work... Did you download the right version of your build? example: 8.0.0.162(C432)
And try to find the latest version of your build and via your model example: ANE-LX1 which is on the back of the phone with small letters or on the box
Cheers,
AS
ars_chelsea said:
Hi again
This is really weird... This one should work... Did you download the right version of your build? example: 8.0.0.162(C432)
And try to find the latest version of your build and via your model example: ANE-LX1 which is on the back of the phone with small letters or on the box
Cheers,
AS
Click to expand...
Click to collapse
Yeah, i did it all right.
So sad...
fcknumb said:
Yeah, i did it all right.
So sad...
Click to expand...
Click to collapse
Remote instructions are not the best for these problems, so try to get a person on your country which knows some stuff and can help you out there