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
Related
Hi all,
I have a Lumia 710, with an unlocked Qualcomm bootloader. Yesterday accidently while flashing a rom as the NAND Disk Drive, whilst doing that i 'didn't' select the OSBL mode & the one beneath it which says W7 Qualcomm, before flashing it. Now it got flashed but the problem is its stuck to one rom. The App deployement tools gives errors such as 'make sure the phone is booted' even though its booted & fine. Or the other error it gives is 'request rejected by host machine'. When connected to Zune i now get pop up from Zune stating 'we can't create a connection from your phone to the internet' now this comes up all the time. I can sync stuff but can't deploy stuff or flash stuff
When i did try flashing the same rom again. After flashing it started directly at the livetiles screen as if nothing happened. I was expecting the 'Welcome to Lumia' screen. Please tell me whats happening. Also i was able to flash another rom on it. However still Zune gives the same error when connected so does the Deployment Tool. I can't figure out what can be done to solve this. I suppose the bootloader might be affected. How do i refresh it? I thought about going to Dload & then Back to Qualcomm. But it seems that many people have bricked phones trying to goto Dload from Qualcomm.
I want my Lumia to be unlocked, but more over, i want it working fine...
Any help & info is appreciated, Thanks
try going back to DLOAD..or do a hard reset to your phone and flash another Custom ROM again.
wen u connect the phone..open device manager and uninstall the drivers..reconnect in same mode..let the drivers reinstall.
surya467 said:
try going back to DLOAD..or do a hard reset to your phone and flash another Custom ROM again.
wen u connect the phone..open device manager and uninstall the drivers..reconnect in same mode..let the drivers reinstall.
Click to expand...
Click to collapse
I followed your instructions... Heres what i did...
Step I: Performed a Hard Reset using the Vol Dwn + Camera + Power Up keys.
Step II: Turned the Phone off & connected the phone with Vol Up + Usb connect. Theres an asterisk sign on Qualcomm CDMA Technologies MSM (I had it uninstalled prior to the reset using the Device Manager, It was detected whilst i connected it in Nand mode again)
Step III: Flashed a new rom on it. Lumiatrix v4.3. Still Zune is giving the same error & Application Deployment is not yet possible.
Surya there are three things i need to ask you.
1. In your Noob Guide the rom flash part you are asking people to turn On their phone, select Nokia Connectivity Mode & then select the .nb file & click Write Os. When i try that it asks me for a Nand Drive.
2. If i should try going back to Dload (can i switch to Qualcomm whenever i feel like?), can you please suggest me a clear & concise method, as to how to do it. I wanted to try this (http://forum.xda-developers.com/showthread.php?t=1702815) but its too confusing.
3. Is a bootloader refresh possible? I connected my phone when it was On. I got the Nokia Connectivity Mode. I tried installing the bootloader it found the phone but wanted me to be in the flash mode. However, when i enter the Nand mode it never finds my phone except when i Write Os on it.
I know i have a long list of questions. Its only because of the fact that i want to understand this better. I dun wanna end up bricking my phone. Thanks in Advance. Tc & Godbless!
Ok..wen u connect your phone to the PC while its ON, its in normal mode...the moment u turn on NSS, it will change modes, so it doesnt matter unless u click WRITE OS, which switches the phone OFF and puts it in the NAND dDrive.
as you have a 710, you can try going back to DLOAD and flash a Stock rom and see if that works, and then you can always go back to a qualcomm by my guide.
your at no loss , unless the problem you have a more complicated than we think it is.
surya467 said:
Ok..wen u connect your phone to the PC while its ON, its in normal mode...the moment u turn on NSS, it will change modes, so it doesnt matter unless u click WRITE OS, which switches the phone OFF and puts it in the NAND dDrive.
as you have a 710, you can try going back to DLOAD and flash a Stock rom and see if that works, and then you can always go back to a qualcomm by my guide.
your at no loss , unless the problem you have a more complicated than we think it is.
Click to expand...
Click to collapse
i would try going back to Dload. However, can you please suggest me a clear & concise method, as to how to do it. I wanted to try this (http://forum.xda-developers.com/show....php?t=1702815) but its too confusing.
Are you suggesting using NSS Bootloader Restore? If so, is there a mode that i need to be in? I'm using NSS 0.51b & when I click on restore it brings up a very scary warning message. As I don't want to brick it, i haven't used it yet.
Please suggest me a method... to return to Dload
I'll start out that I'm new to android, been an avid blackberry user that just purchased my note 2. I followed the casual root application, and unlocked and rooted my device. I went to install cm 10.2 mod on my device after wiping the device in development mode then proceeded to install from sdcard and it failed. Now my device will not respond to either download mode or development mode or power on in any way (including using a charger and removing and replacing the battery). I'm kind of stuck and not sure how to approach the correct solution to get my device back up and running. I did make sure that the cm mod I downloaded was for my specific device. Is it possible that maybe the root/unlock method failed and thats where I went wrong when installing the cm mod? I also get no response when the device is plugged into my pc. So its not being read by odin currrently.
Since it appears I have hard bricked my device, not quite sure what steps I can do to recover. I get no power to the device in any situation, I've read online about jtag, if anyone could point me in a direction it would be helpful. Thanks in advance.
Sorry forgot to mention this was a verizon branded note 2
achiquitachaser said:
I'll start out that I'm new to android, been an avid blackberry user that just purchased my note 2. I followed the casual root application, and unlocked and rooted my device. I went to install cm 10.2 mod on my device after wiping the device in development mode then proceeded to install from sdcard and it failed. Now my device will not respond to either download mode or development mode or power on in any way (including using a charger and removing and replacing the battery). I'm kind of stuck and not sure how to approach the correct solution to get my device back up and running. I did make sure that the cm mod I downloaded was for my specific device. Is it possible that maybe the root/unlock method failed and thats where I went wrong when installing the cm mod? I also get no response when the device is plugged into my pc. So its not being read by odin currrently.
Since it appears I have hard bricked my device, not quite sure what steps I can do to recover. I get no power to the device in any situation, I've read online about jtag, if anyone could point me in a direction it would be helpful. Thanks in advance.
Click to expand...
Click to collapse
I guess no one has an idea of where to go with this now?
achiquitachaser said:
I guess no one has an idea of where to go with this now?
Click to expand...
Click to collapse
connecting to pc does your note responds or pc shoes something
remove your battery connect to pc and go to download mode by pressing the button combo if odin shows a port
and you are connected then you are saved if not I guess its tym for service center
anyways try
P.S be sure that you have latest drivers installed on pc and use the original usb cable for conecting
sangalaxy said:
connecting to pc does your note responds or pc shoes something
remove your battery connect to pc and go to download mode by pressing the button combo if odin shows a port
and you are connected then you are saved if not I guess its tym for service center
anyways try
P.S be sure that you have latest drivers installed on pc and use the original usb cable for conecting
Click to expand...
Click to collapse
Thanks for the reply sangalaxy, like I mentioned the phone does not respond at all for download mode, not recognized by Odin or showing any power when connected to a charger. Hence why I was thinking its hard bricked.
I'm not sure if I can send it to samsung, since I bought the phone off craigslist.
achiquitachaser said:
Thanks for the reply sangalaxy, like I mentioned the phone does not respond at all for download mode, not recognized by Odin or showing any power when connected to a charger. Hence why I was thinking its hard bricked.
I'm not sure if I can send it to samsung, since I bought the phone off craigslist.
Click to expand...
Click to collapse
yea sometimes it will not recognize anything and will not show on screen but will work silently
did you tried connecting it to pc without battery as I said and go to download mode by pressing buttons may be odin will recognize
if not you don't have any choice but go to samsung
Your right I didn't fully read your post to try those instructions, unfortunately it didn't work but thank you for the help. It is definitely appreciated. I think I have found someone off eBay with a good reputation for jtagging android devices that might be a solution.
achiquitachaser said:
Your right I didn't fully read your post to try those instructions, unfortunately it didn't work but thank you for the help. It is definitely appreciated. I think I have found someone off eBay with a good reputation for jtagging android devices that might be a solution.
Click to expand...
Click to collapse
ok friend hope it gets fixed
Hi, I think I am in deep trouble now. My p780 8gb is completely dead after trying to flash a TWRP recovery in to it using a flash tool. Not sure what went wrong I fiddled with some settings in flash tool like 'firmware upgrade' and 'download' and at last saw a Dram failed message. I was using the latest s226 Kitkat ROW. Now all I can see is a red led charging light glowing while connecting it to a computer. The device is not getting recognized by VCOM drivers so no use with flash tool any more. Tried to reboot in to recovery and meta mode but the phone simply does not turn on. Anyone knows how to unbrick this, kindly help.
xperimen said:
Hi, I think I am in deep trouble now. My p780 8gb is completely dead after trying to flash a TWRP recovery in to it using a flash tool. Not sure what went wrong I fiddled with some settings in flash tool like 'firmware upgrade' and 'download' and at last saw a Dram failed message. I was using the latest s226 Kitkat ROW. Now all I can see is a red led charging light glowing while connecting it to a computer. The device is not getting recognized by VCOM drivers so no use with flash tool any more. Tried to reboot in to recovery and meta mode but the phone simply does not turn on. Anyone knows how to unbrick this, kindly help.
Click to expand...
Click to collapse
Hi. Please tell me if your phone is made in 2014. From what i see all phones made in 2014 must be flashed with another preloader. The simptoms you are described here seems that way. Waiting fro reply...
2014 vesrsion
stympy said:
Hi. Please tell me if your phone is made in 2014. From what i see all phones made in 2014 must be flashed with another preloader. The simptoms you are described here seems that way. Waiting fro reply...
Click to expand...
Click to collapse
Hi stympy,
Yes it is a 2014 January version. But to be honest I was using a ROM with 2013 version preloader but never faced any problem, Today purposefully changed it to the new 121kb 2014 preloader and everything was fine till I used the v5 flashtool to flash the twrp and I think I selected the upgrade option in it and flashed the twrp> found the ROM and preloaders from needrom.com from the uploader xxxsadistxxx .It worked flawlessly and then after first booting I configured the wi-fi settings again turned it off and tried to install the custom recovery. Now completely helpless because the phone is not getting detected by VCOM drivers.
xperimen said:
Hi stympy,
Yes it is a 2014 January version. But to be honest I was using a ROM with 2013 version preloader but never faced any problem, Today purposefully changed it to the new 121kb 2014 preloader and everything was fine till I used the v5 flashtool to flash the twrp and I think I selected the upgrade option in it and flashed the twrp> found the ROM and preloaders from needrom.com from the uploader xxxsadistxxx .It worked flawlessly and then after first booting I configured the wi-fi settings again turned it off and tried to install the custom recovery. Now completely helpless because the phone is not getting detected by VCOM drivers.
Click to expand...
Click to collapse
Look what you have to do!
Hi. The think was someting like this:
0. Unzip/Unrar those 2 archives.
1. First i install the .exe file from archive LenovoUsbDriver_autorun_1.0.10.zip. Reboot PC.
2. Plug the phone to your PC and new hardware wizard has appeared. Install the drivers by pressing automaticaly search the drivers.
3. Now power off the phone, and open the Device Manager, in Ports section.
4. With the Device Manager open, plug the phone this time powered off.
5. At this time in Device Manager/ Ports section, appeared for a second or two not in USB area something with.. MTK65...
6. Double Click fast on it because that will desapear very fast . If you missed the click for the first time unplug and replug the phone after about 5 seconds.
7. After you clicked on it all you have to do is update driver from MTK_USB__Driver_GOOOOODDD.rar archive, and voila you have drivers installed and now all you have to do is to flash you ROM.
Hope this will help you.
Tell me iff something goes wrong.
Good luck.
help
stympy said:
Look what you have to do!
Hi. The think was someting like this:
1. First i install the .exe file from archive LenovoUsbDriver_autorun_1.0.10.zip. Reboot PC.
2. Plug the phone to your PC and new hardware wizard has appeared. Install the drivers by pressing automaticaly search the drivers.
3. Now power off the phone.
4. Again plug the phone this time powered off.
5. At this time in Device Manager appeared for a second or two not in USB area something with.. MTK65...
6. Click very fast on it because that will desapear fast.
7. After you clicked on it all you have to do is update driver from MTK_USB__Driver_GOOOOODDD.rar archive, and voila you have drivers installed and now all you have to do is to flash you ROM.
Hope this will help you.
Tell me iff something goes wrong.
Good luck.
Click to expand...
Click to collapse
1) Hi, thanks for the troubleshooting steps but for the 3rd and 4th step, the phone is always in a switched off mode only. It simply doesn't get turn on in any mode.
2) I am using Windows 8.1 OS and Lenovo Usb Driver1.0.10 and VCOM drivers are already installed in it after turning off the digital signature check in win 8x OS and now nothing is happening after clicking on install option of LenovoUsbDriver_autorun_1.0.10.exe Is it a problem or in other OS also it wont prompt to click next or something like in a regular driver installation.
3) Phone is not getting detected in device manager after connecting it, so cant update drivers
Please suggest me what to do next.
xperimen said:
1) Hi, thanks for the troubleshooting steps but for the 3rd and 4th step, the phone is always in a switched off mode only. It simply doesn't get turn on in any mode.
2) I am using Windows 8.1 OS and Lenovo Usb Driver1.0.10 and VCOM drivers are already installed in it after turning off the digital signature check in win 8x OS and now nothing is happening after clicking on install option of LenovoUsbDriver_autorun_1.0.10.exe Is it a problem or in other OS also it wont prompt to click next or something like in a regular driver installation.
3) Phone is not getting detected in device manager after connecting it, so cant update drivers
Please suggest me what to do next.
Click to expand...
Click to collapse
Ok. Try this:
1. Open the back case of your phone.
1.1 Open the device manager on your PC.
2. You will find there an small red button.
3. Now plug your phone to your PC.
4. After you plugged the phone press the red button for 20 secconds.not optional
5. Release the button and see what is going on in your device manager.
6. Iff your preloader is messed up something should going on.
7. Should appear something like new hardware detected, that is the point when you update the drivers, and your phone will be detected by your PC
8. Try this and tell me if something goes wrong.
Good luck.
Sent from my Lenovo P780
TWRP magic
stympy said:
Ok. Try this:
1. Open the back case of your phone.
1.1 Open the device manager on your PC.
2. You will find there an small red button.
3. Now plug your phone to your PC.
4. After you plugged the phone press the red button for 20 secconds.not optional
5. Release the button and see what is going on in your device manager.
6. Iff your preloader is messed up something should going on.
7. Should appear something like new hardware detected, that is the point when you update the drivers, and your phone will be detected by your PC
8. Try this and tell me if something goes wrong.
Good luck.
Sent from my Lenovo P780
Click to expand...
Click to collapse
Hi thanks a lot stympy. I am glad that you were spending the time and effort to help me. I saw that red button trouble shooting post in your TWRP thread and luckily for me after clicking on different options in device manager while setting a complete format in sp flashtool the device suddenly got detected and format was done. After the format the device has lost its imei number, BT code and Wlan codes. That was going to be a hectic job to reinstall imei with imei repairing tools and usage of Hexa editor for BT and wi-fi codes just because some drivers were not getting installed properly.. But to my sheer luck I had a "Data' back up in TWRP with my previous version prerooted rom . I was not that confident to get a restore of imei , BT and wlan codes because it is just a 'data' back up not full ROM. I ticked the md5 checksum and voila after installing the back up 'Data' everything , absolutely every single code in my p780 got reinstalled automatically .LONG LIVE TWRP DEVELOPERS......... May be even after formatting the complete flash drive of the phone it still keeps the imei and other codes in factory mode. I am not sure. Now phone is in perfect condition and I am ready for another go. Stympy please create a 2.7.1 twrp for 2014 preloader p780 8gb. thanks again for all your help
xperimen said:
Hi thanks a lot stympy. I am glad that you were spending the time and effort to help me. I saw that red button trouble shooting post in your TWRP thread and luckily for me after clicking on different options in device manager while setting a complete format in sp flashtool the device suddenly got detected and format was done. After the format the device has lost its imei number, BT code and Wlan codes. That was going to be a hectic job to reinstall imei with imei repairing tools and usage of Hexa editor for BT and wi-fi codes just because some drivers were not getting installed properly.. But to my sheer luck I had a "Data' back up in TWRP with my previous version prerooted rom . I was not that confident to get a restore of imei , BT and wlan codes because it is just a 'data' back up not full ROM. I ticked the md5 checksum and voila after installing the back up 'Data' everything , absolutely every single code in my p780 got reinstalled automatically .LONG LIVE TWRP DEVELOPERS......... May be even after formatting the complete flash drive of the phone it still keeps the imei and other codes in factory mode. I am not sure. Now phone is in perfect condition and I am ready for another go. Stympy please create a 2.7.1 twrp for 2014 preloader p780 8gb. thanks again for all your help
Click to expand...
Click to collapse
WARRNING This are only for 8GB PHONES.
Here you are.
Try to flash with scatter files one by one till works.
Use only SP Flash Tool 5.
After flashing TWRP do not reboot the phone, start the phone with Power button Vol + and Vol - pressed. NOT OPTIONAL
Be carrefoul to select Download not Firmware Upgrade.
Good Luck.
Thank you stympy master
stympy said:
WARRNING This are only for 8GB PHONES.
Here you are.
Try to flash with scatter files one by one till works.
Use only SP Flash Tool 5.
After flashing TWRP do not reboot the phone, start the phone with Power button Vol + and Vol - pressed. NOT OPTIONAL
Be carrefoul to select Download not Firmware Upgrade.
Good Luck.
Click to expand...
Click to collapse
whoaa...that worked.. the 1st scatter file just worked..thanks a lot Sir stympy. Thank you very much
xperimen said:
whoaa...that worked.. the 1st scatter file just worked..thanks a lot Sir stympy. Thank you very much
Click to expand...
Click to collapse
You are wellcome. Glad to help
stympy said:
You are wellcome. Glad to help
Click to expand...
Click to collapse
Hey Stympy, you seem to know quite a lot about this! I have the same problem with my p780 4GB. After flashing everything seemed ok, as I got a green circle in SPFlash tools. However now I am not able to boot anymore. When connecting my phone to my computer the red light goes on and Device Manager shows a new MTK USB Port. When pushing the red button it immediately disappears. Does not matter if I push it for 20 seconds, as soon as I let go its bak in device manager.
When trying to reflash using SPFlash, it seems to recognize my phone, but when trying to format or Upgrade or Download, the red bar only loads up to 141776 Bytes and stops. Sometimes I have to push the red button for the phone to get recognized.
Any help would be greatly appreciated!
ps: CMIIT ID on the battery says 2013xxxxxxx so I guess its a 2013 model?
jeerome88 said:
Hey Stympy, you seem to know quite a lot about this! I have the same problem with my p780 4GB. After flashing everything seemed ok, as I got a green circle in SPFlash tools. However now I am not able to boot anymore. When connecting my phone to my computer the red light goes on and Device Manager shows a new MTK USB Port. When pushing the red button it immediately disappears. Does not matter if I push it for 20 seconds, as soon as I let go its bak in device manager.
When trying to reflash using SPFlash, it seems to recognize my phone, but when trying to format or Upgrade or Download, the red bar only loads up to 141776 Bytes and stops. Sometimes I have to push the red button for the phone to get recognized.
Any help would be greatly appreciated!
ps: CMIIT ID on the battery says 2013xxxxxxx so I guess its a 2013 model?
Click to expand...
Click to collapse
Hi. Can you tell me what firmware did you have ?
From what you described your phone seems to be from 2014. This are the simptoms when the preloader is messed up.
Look what you should try:
Download from here the preloader: http://forum.xda-developers.com/lenovo-p780/help/lenovo-p780-chineese-speed-version-t2874161
Replace your Curent ROM preloader with the one you downloaded.
Drivers from here: http://forum.xda-developers.com/len...ial-kitkat-t2835605/post55587780#post55587780
Try this one and tell me if somethin goes wrong.
Waiting for Reply.
stympy said:
Hi. Can you tell me what firmware did you have ?
From what you described your phone seems to be from 2014. This are the simptoms when the preloader is messed up.
Look what you should try:
Download from here the preloader: http://forum.xda-developers.com/lenovo-p780/help/lenovo-p780-chineese-speed-version-t2874161
Replace your Curent ROM preloader with the one you downloaded.
Drivers from here: http://forum.xda-developers.com/len...ial-kitkat-t2835605/post55587780#post55587780
Try this one and tell me if somethin goes wrong.
Waiting for Reply.
Click to expand...
Click to collapse
Excellent! Did exactly what you said, works like a charm. You made my day Sir! Thank you very much!
jeerome88 said:
Excellent! Did exactly what you said, works like a charm. You made my day Sir! Thank you very much!
Click to expand...
Click to collapse
You are wellcome!
Friend HELP me also
xperimen said:
Hi, I think I am in deep trouble now. My p780 8gb is completely dead after trying to flash a TWRP recovery in to it using a flash tool. Not sure what went wrong I fiddled with some settings in flash tool like 'firmware upgrade' and 'download' and at last saw a Dram failed message. I was using the latest s226 Kitkat ROW. Now all I can see is a red led charging light glowing while connecting it to a computer. The device is not getting recognized by VCOM drivers so no use with flash tool any more. Tried to reboot in to recovery and meta mode but the phone simply does not turn on. Anyone knows how to unbrick this, kindly help.
Click to expand...
Click to collapse
I also want get rid of this bricked p780 8gb updated to kitkat 4.2.2 . Kindly, help me also with step by step procedure I'm totally new to this world. My phone is stuck at Lenovo logo... that it.... Please help me... ;(
apsaujla08 said:
I also want get rid of this bricked p780 8gb updated to kitkat 4.2.2 . Kindly, help me also with step by step procedure I'm totally new to this world. My phone is stuck at Lenovo logo... that it.... Please help me... ;(
Click to expand...
Click to collapse
Hi. Download the rom you need for your phone from here !
Download SP Flash Tool 5 from here!
Download drivers from here and here !
BE CAREFUL USE ONLY WINDOWS 7 ! THIS IS NOT OPTIONAL! IF YOU DONT HAVE WINDOWS 7 LOOK FOR VMWARE AND INSTAL THERE A VIRTUAL MACHINE !
Install first the drivers!
Open SP Flash Tool with admin rights!
Use this tutorial! If you dont manage PM me !
Good Luck!
help me too
jeerome88 said:
Excellent! Did exactly what you said, works like a charm. You made my day Sir! Thank you very much!
Click to expand...
Click to collapse
@stympy your statistics are impressive 1 greeting / 2 posts.
I've hope that I'll be more than just grateful. I've problem with modem in P780 "SIM ME locked, do you want to unlock" after unbricking.
It ask me about SIM pin and after no signal.
Regards
ungbar said:
@stympy your statistics are impressive 1 greeting / 2 posts.
I've hope that I'll be more than just grateful. I've problem with modem in P780 "SIM ME locked, do you want to unlock" after unbricking.
It ask me about SIM pin and after no signal.
Regards
Click to expand...
Click to collapse
Hi. Please tell me what rom do you have in this moment. How did you soft brick your phone?
Sent from my Lenovo P780
stympy said:
Hi. Please tell me what rom do you have in this moment. How did you soft brick your phone?
Sent from my Lenovo P780
Click to expand...
Click to collapse
Fool me. I've tried to run CN on russian LiFE ROW with TWRP. You can laugh very loud.
1. unbricked with P780_S136_140306_Lang
cleared IMEI
2. IMEI recovered with Droid Tools
after reboting no gsm signal
3. NVRAM recovered from backup
No success.
SIM cards works fine on other mobile, 911 cal also work on this phone
now running on:
ROM: P780_S226_Life_XVIBE_by_Xakep
Baseband: P780.V23
Last idea is clone p780 (colleague has one) with IMEI change, mac address and sn. Now with which tool it'll be easier?
success
ungbar said:
Fool me. I've tried to run CN on russian LiFE ROW with TWRP. You can laugh very loud.
...
Last idea is clone p780 (colleague has one) with IMEI change, mac address and sn. Now with which tool it'll be easier?
Click to expand...
Click to collapse
Last idea also faild.
And I have done it again.
1. Full format
2. Download Rom P780_S136_140306_Lang
3. Change IMEI
And it works.
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.
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