Related
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script to get into fastboot at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
So you solve it! :good:
:/
tawhid111 said:
How to fix partion problem !!!
After countlss hours of messing with the LG P769 This is how i got into S/W mode to work !:laugh:
ASSUMING you know how to install fastboot drivers there are instructions on the forum ...so follow those guide note fastboot drivers work best on windows 7 windows 8 was giving me hard time ...
1.install fastboot drivers
2.run lelus script at the same time hold vol+ button once the script shows the OMAP device close the script and immediately put the battery back in .The LG phone will boot into S/W mode !
Make sure you write down your imei or serial number AND make sure battery is fully charged . then
Now simply use the LG software tool or the KDZ offline flasher look around the forum for how to guides
Thats it
Click to expand...
Click to collapse
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
foreverman said:
Still unable to do it, when I plug the cable holding vol+ it just reboot normally :/
Click to expand...
Click to collapse
Then try enter in lelus fastboot mode, ad then flash x-loader, uloader, boot.img and recovery.img from stock rom for your device type model. Then repeat steps 1 and 2
Where can I find the lelus script?
Sent from my Note II
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Then you need a Technician with a Octopus Box to repair your partition table...
ciccillover said:
Sorry for reviving such an old thread, but oh well...
Your procedure doesn't seem to work with my device. Just to make sure we are using the same driver packages, can you post a link to the fastboot driver you have successfully used?
My L9 is always showing this "partition doesn't exist" error message, no matter what I try. Lelus's script seems to do the job and the phone is detected as a fastboot device, and can even be detected in LG Flash Tool (using a 910K cable), but flashing will stop after a little over 2 minutes, because the phone disconnects. During all of my attempts, the screen stays black.
Any hint?
Click to expand...
Click to collapse
Can you boot into recovery? We now have a custom recovery for locked bootloaders (and CM roms). If you can get into recovery, I would try some adb commands to mount the partitions.
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
ciccillover said:
No, no recovery. Just to make sure that I'm not doing it wrong, what is the key combination to boot to recovery?
I have also tried:
Code:
fastboot boot some_recovery_image.img
It says ok, but the phone just hangs at the black screen and becomes undetectable as a fastboot device, until I pull the battery. So, unless the some_recovery_image.img is unsuitable for my P760 (which may be!), there is something seriously wrong I think.
Or maybe I can try the same command with the custom recovery for bootloader locked phones... Where can I find it?
Click to expand...
Click to collapse
Your EMMC partition is wiped or fried... you really need a JTAG service or a Box like octopus because your L9 is Hard-bricked...
Thanks for your opinion. Yet, I still want to hear from others.
I'm running into more and more problems with the L9 as their me grows.
-Fastboot doesn't work under Windows 8.1 and 10, but under the now obsolete(for me) Windows 7, unlike my other devices, which are fine with Win 10.
-ADB seems to work, but requiring the device to be still able to boot.
-I always boot to recovery from within Android as long as the L9 ain't bricked. After a failed rom install, during which the sd card failed(could no longer write or be formatted afterwards, the last time stamps of files and folders were set during the failed install) I discovered a problem with TWRP(Artas182x's and Edwin's), which may have been present since a long time: Trying to invoke TWRP via keypress will brick the device!
So, if my P760 no longer boots, there's only download mode available, sort of the final line of defense.
-There's sort of a trick if even download mode fails: After a failed attempt unplug phone, force switch-off, if the phone is in brick state. Then switch on, force switch-off again, and only then attempt download mode again. And have patience while holding down the vol button, it might take up to 20 seconds for the phone to switch itself on into download mode. (A single forced powerdown will cause Fastboot NOT to work the next time)
But I'm absolutely clueless about the recovery issue, for now TWRP is semi-working, can only be accessed via Android, as long as the phone is fully working.
W/o Fastboot, I now have flashed stock rom several times and rooted it with Kingo rooter just to be able to run Flashify to install TWRP. If Flashify is the culprit for the TWRP issues, I could need a recommendation for a better working app.
ciccillover said:
Thanks for your opinion. Yet, I still want to hear from others.
Click to expand...
Click to collapse
Tried OMAP flasher ? It needs memory configuration file in order to work with our device
No, I didn't. I have sold the phone for spares.
Inviato dal mio LG-D855 utilizzando Tapatalk
I never needed the OMAP drivers and tools. As they are ancient, they will probably make even more problems with newer Windows versions.
I could by no means invoke Fastboot on this device with Windows 8.1 and 10, Seven worked. So you had to go for Download Mode instead to recover to stock rom, then root with the Kingo tool, then install TWRP via Rashr or Flashify, the most time consuming way to recover from the frequent bricks.
And the LG Flash Tool 2014 always needed several attempts to get the job done. The latest official recovery tool from LG works in D/L Mode, but will always download the rom image anew.
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
privateriem said:
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
Click to expand...
Click to collapse
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : https://www.androidfilehost.com/?fid=24591000424940129
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
HParra97 said:
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : snip
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
Click to expand...
Click to collapse
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
privateriem said:
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
Click to expand...
Click to collapse
Read this thread : http://en.miui.com/thread-91415-1-1.html
Make sure that you've disabled driver verification signature, your path to the image folder does not contain any spaces, and also the flash all data except data and storage option.
Hi,
I'm new here, so please excuse me if I am posting in the wrong category.
So I tried to root my Doogee F7 (not the pro version) using fastboot and TWRP, and it resulted in a sort of bootloop where it says:
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then it restarts and gives the same message again. This loop has been going on for some time and I can't stop it because the phone has a non-removable battery and I have tried every possible combination of buttons (i.e. Power + Volume Down + Volume Up).
The process I used in my attempt to root was as following:
1. I used
Code:
adb reboot bootloader
to go into fastboot. (I already set up everything like USB debugging and OEM unlocking in the developer options)
2. I then used
Code:
fastboot oem unlock
and pressed Volume Up to unlock the bootloader. All was successful.
3. I then tried to flash TWRP to recovery and I believe this is where everything went wrong. I flashed it using
Code:
fastboot flash recovery recovery.img
and it was successful, according to the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\Users\momen\Downloads\recovery (1).img"
target reported max download size of 134217728 bytes
sending 'recovery' (12832 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.779s
4. After it finished I used
Code:
fastboot reboot
to reboot the phone and that's when it got stuck.
At the moment I am just letting my battery run out, as I have no other way of turning off the phone, and neither adb nor fastboot is working.
I don't really know if my device was even supported, but I followed the instructions on various websites stating that I should first unlock my bootloader, then flash TWRP, then flash superSU onto it, and my phone would be rooted. I used the latest TWRP image, and I think that was where I went wrong. Is there anything I can do to get my phone to work again?
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
solartediego said:
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
Click to expand...
Click to collapse
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Hello there. I suggest that you use "fastboot boot recovery.img" than using "fastboot flash" if you are not sure if the custom recovery works (or if you just want to test/try it). In this way, you'll just boot the custom recovery temporarily (and your stock recovery is still in tacked).
For rooting your device, first you'll need a working custom recovery for your device (you used TWRP, very first if it works or compatible with your device).
Insyder28 said:
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Click to expand...
Click to collapse
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
ciubsy2004 said:
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
Click to expand...
Click to collapse
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
TheBidan said:
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
Click to expand...
Click to collapse
I have managed to get the flash tool recognizing my phone.Had to keep pressed volume up,if i recall properly(or try volume down) before connecting usb cable to phone with flash tool opened and . It was a while ago though and i can't remember exactly which key was for sure. Hope this helps
Hello,
This morning I turned off and on my phone (RN5 Global).
Now, If I try to start it, phone goes directly to Mi-Recovery 3.0 and, no matter how hard you try to restart, it always ends there.
More info:
- The phone is completely from stock. No root, no bootloader unlock, nothing.
- Mi-Recovery only let me Wipe All Data, so this would be an unfeasible option without first having recovered the data.
- My PC Suite does not recognize the phone.
- If I connect the mobile to the pc, 'adb devices' command says "sideload".
- If I try to make a backup by 'adb shell' it says "error: closed".
- I do not know if 'debug usb' is activated. I remember i activated it in the past, but I think that MIUI10 update deactivated it again.
- I can enter fastboot mode.
- I tried to open the phone, disconnect and connect the battery, but nothing has been fixed.
What can I do? My priorities now are:
1.- Recover the data (at least photos).
2.- Revive my phone.
Thank you.
Found this on MIUI, what do you think?
http://en.miui.com/thread-2171064-1-1.html
CiDsTaR said:
Found this on MIUI, what do you think?
http://en.miui.com/thread-2171064-1-1.html
Click to expand...
Click to collapse
If your device is Redmi Note 5 from other country but India then it´s Whyred and this Forum is for Redmi 5 Plus/Redmi Note 5 (only India) that is Vince.
In the case I´m right and your device is Whyred (two rear cameras is a simple way to note it) then as far as I know you will need an EDL authorized account to flash a rom through MiFlash Tool.
Other tool that you can use is XiaomiFlash Tool by Francesco Tescari through Mi-Recovery but you will need too have enable USB debugging (maybe you have) but the same way you can flash a rom also you´ll lose all your data.
Adb shell works only in rooted devices, you can´t backup nothing in this state and fastboot mode is limited to just few commands like list device/reboot devices and nothing more in locked bootloaders.
In this scenario you have two things in order to solve this issue:
1- Highly probable loosing all your data.
- Doing format data through recovery and try to boot (data lost for sure)
- Flashing a rom through recovery with the mentioned tool (99% data lost probabilities)
- Flashing a rom through EDL; if you have Vince you can do it but if you have Whyred I don´t think so (if you choose second option "Flash without erase userdata" in MiFlash Tool I guess your data will be preserved)
2- If you enabled before USB debugging and binded your Mi account with device wait the time to unlock bootloader and maybe booting first of all in TWRP you can recover some data from your device, if you unlocked but first of all you boot on system for sure all your data will gone.
So what happened? Were you able to solve it? PLs share if you were...
I am also faced that situation.
When i tried to flash stock miui through fastboot it locked the bootloader and cant boot into rom then mi flash tool cant flash as boot loader is locked.
Worst part is in order flash another rom i need recovery, unable to reach developers option as rom not booting up.
Lost hope on the device
After all so many google searches and sleep less nights
I found application called mi pc suite china
Try to flash miui rom through mi pc suite mode
It says boot loader locked do you want to unlock
Finally it unlocked boot loader without booting into mobile.
In your case that will app will work. try it
gldvs007 said:
I am also faced that situation.
When i tried to flash stock miui through fastboot it locked the bootloader and cant boot into rom then mi flash tool cant flash as boot loader is locked.
Worst part is in order flash another rom i need recovery, unable to reach developers option as rom not booting up.
Lost hope on the device
After all so many google searches and sleep less nights
I found application called mi pc suite china
Try to flash miui rom through mi pc suite mode
It says boot loader locked do you want to unlock
Finally it unlocked boot loader without booting into mobile.
In your case that will app will work. try it
Click to expand...
Click to collapse
THANK YOU THIS HELPED ME OUT A LOT
I JUST INSTALLED THE APP THROUGH THIS LINK - https://miui.blog/any-devices/china-mi-pc-suite-english-translation/
AND THEN CONNECTED MY MI4i TO THE PC. IT AUTOMATICALLY ADDED THE STOCK REQUIRED FROM THE INTERNET AND I DIDNT CLICK ANYTHING IN THE APP.
RehanSiddiqui said:
THANK YOU THIS HELPED ME OUT A LOT
I JUST INSTALLED THE APP THROUGH THIS LINK - https://miui.blog/any-devices/china-mi-pc-suite-english-translation/
AND THEN CONNECTED MY MI4i TO THE PC. IT AUTOMATICALLY ADDED THE STOCK REQUIRED FROM THE INTERNET AND I DIDNT CLICK ANYTHING IN THE APP.
Click to expand...
Click to collapse
BIG THANKSS, THIS HELP ME TOO
In my case my Redmi Note 7 MIUI 11.xx and had a update notification
im accidenly hold my power button my, and ALWAYS go to MI-Recovery 3.0 after several reboot
Im downloading that app and updating that app,
And copy the translate file from China to English (my pc WINDOWS 10 64x)
i chose "Connect to Mi Assistant" in phone connect to my pc and open the app, that can see my current ROM (MIUI 11.xx) can be update to "MIUI 12.xx" ,im flashing(updating) with "LEFT" option
that say "CAN SAVE UR SEVERAL FILES" than option RIGHT(DELETE ALL FILES) i guess i dont much remember
Im flashing(updating) with hope my files still in there,
The app start downloading the ROM and instaling to my phone 0% to 100%
My phone reboot and had notify "The system has been destroy"
After restarting several time, Im lossing hope on my phone,
Im trying hold my -Volume button while rebooting, then my phone booting on MIUI 12 in several minute
And "EVERYTHING ITS FINE" i have my all files,app,photos, just like my regular phone but have new MIUI 12 update Introduce changelog
I just wanna share my experience
THANK YOU A LOT
Seeing this Stuck in Mi Recovery 3.0 with a stock device
Thanks Dude... It works for my MI Poco F1.
Steps
Download chinese version of mi app (version 3 beta) from below link
Replace English Translated mi_phone_assistant.res file in installation folder.
Connect Mobile with PC
Open the Mi App Then Click the update button which shows upon opening
Phone automatically came back to normal (No loss in Data) and Remove Cable. Don’t Flash Data.
China Mi PC Suite with English Translation | MIUI Blog
Mi app recovery will not work on older phones like vince i suggest flashing through test point by removing the back cover and reconnect both points
mccholai said:
Seeing this Stuck in Mi Recovery 3.0 with a stock device
Thanks Dude... It works for my MI Poco F1.
Steps
Download chinese version of mi app (version 3 beta) from below link
Replace English Translated mi_phone_assistant.res file in installation folder.
Connect Mobile with PC
Open the Mi App Then Click the update button which shows upon opening
Phone automatically came back to normal (No loss in Data) and Remove Cable. Don’t Flash Data.
China Mi PC Suite with English Translation | MIUI Blog
Click to expand...
Click to collapse
it stuck at 99%
CiDsTaR said:
Hello,
This morning I turned off and on my phone (RN5 Global).
Now, If I try to start it, phone goes directly to Mi-Recovery 3.0 and, no matter how hard you try to restart, it always ends there.
More info:
- The phone is completely from stock. No root, no bootloader unlock, nothing.
- Mi-Recovery only let me Wipe All Data, so this would be an unfeasible option without first having recovered the data.
- My PC Suite does not recognize the phone.
- If I connect the mobile to the pc, 'adb devices' command says "sideload".
- If I try to make a backup by 'adb shell' it says "error: closed".
- I do not know if 'debug usb' is activated. I remember i activated it in the past, but I think that MIUI10 update deactivated it again.
- I can enter fastboot mode.
- I tried to open the phone, disconnect and connect the battery, but nothing has been fixed.
What can I do? My priorities now are:
1.- Recover the data (at least photos).
2.- Revive my phone.
Thank you.
Click to expand...
Click to collapse
Just remove SD card & SIM tray from phone and restart. I work for me. try at our end. Don't flash or connect anything.
CiDsTaR said:
Hello,
This morning I turned off and on my phone (RN5 Global).
Now, If I try to start it, phone goes directly to Mi-Recovery 3.0 and, no matter how hard you try to restart, it always ends there.
More info:
- The phone is completely from stock. No root, no bootloader unlock, nothing.
- Mi-Recovery only let me Wipe All Data, so this would be an unfeasible option without first having recovered the data.
- My PC Suite does not recognize the phone.
- If I connect the mobile to the pc, 'adb devices' command says "sideload".
- If I try to make a backup by 'adb shell' it says "error: closed".
- I do not know if 'debug usb' is activated. I remember i activated it in the past, but I think that MIUI10 update deactivated it again.
- I can enter fastboot mode.
- I tried to open the phone, disconnect and connect the battery, but nothing has been fixed.
What can I do? My priorities now are:
1.- Recover the data (at least photos).
2.- Revive my phone.
Thank you.
Click to expand...
Click to collapse
how u solved your problem , i am stuck in same stage .. help please
I was stuck in Mi Recovery Mode 3.0 on my Mi Redmi Note 5.
Even after doing reboot to system, it wasn't going back to normal.
After scratching my head for a lot of time I decided to do the old school thing, i.e. REMOVING the SIM card and SD card and pressing the VOLUME DOWN + POWER KEY until the vibration occurred (NOTE: Mi logo will appear while you have pressed but keep the 2 buttons pressed until vibration occurred).
harsimran27 said:
I was stuck in Mi Recovery Mode 3.0 on my Mi Redmi Note 5.
Even after doing reboot to system, it wasn't going back to normal.
After scratching my head for a lot of time I decided to do the old school thing, i.e. REMOVING the SIM card and SD card and pressing the VOLUME DOWN + POWER KEY until the vibration occurred (NOTE: Mi logo will appear while you have pressed but keep the 2 buttons pressed until vibration occurred).
Click to expand...
Click to collapse
were any files deleted? and do you perhaps know if it would work on redmi note 7?
hello guys just look this video i solved it
Hi all,.
I also faced the same issue my redmi note 5 Pro which was on I believe MIUI 10 because it was never updated from the day it was purchased got stuck in bootloop and not getting ahead after recovery mode no matter how much time you reboot it was all working fine but some apps were updating such as youtube when this incident occurred I tried every solution like pressing keys pressing all three keys simultaneously or ADB method but none could work since the phone was locked also there was no USB debugging so adb method wouldn't work to also if an if ADB connected I couldn't flash because it will remove the data, in recovery mod you can see in option connect with MI Assistant but the Indian English version shown no connection so found one youtube video (channel name -" Ach Sharif ", video link-
which helped to install chinese version and and solved login issues I used Google translate translate to read the Chinese characters and understand what is going on I connected the device intending to take a backup backup but as no option was available I had to click on flash device so it downloaded upgraded recovery rom and automatically flash to MIUI 11 but still same problem then again I connected and upgraded to MIUI 12 and the phone was able to boot so the phone finally got fixed all data and all apps were intact and working as originally also all data of WhatsApp chats etc remained even the open apps at the time when problem happened were still present.
I believe guys this is the only solution to the problem because while flashing it replaces the recovery module of the rom which was corrupted earlier in my case when MIUi 12 installed not 11 I feel that it replaced recovery module due to update and it was able to work so please try once and I hope you get your files back, now lesson learned please do regular backups to live worry free life otherwise we will be spending time and energy here only.
I believe ADB methods or other methods won't work because they will flash and you won't be able to get data only flashing through recovery ROM not fastboot rom just like update package will be able to solve your problem if it is a software problem it will be can be fixed fixed this way only and saving data if it's a hardware problem such as power of all volume buttons are stucked you just get change and everything will be fine it happened in my other phone redmi Y2 so from speaking from experience thats all as I was going through trouble these things really help me so I thought to spend time in creating this guide please follow and I hope it will be solved.
You must open back cover( easily you can do it by hair dryer) and disconnect and connect again the battery, it will fix
I am currently trying to install LineageOS on my phone. I personally have never unlocked or reinstalled a new operating system on my phone. I looked on some XDA forums for some guides and i found one and followed the steps. I unlocked my phone and I installed a custom TWRP because I was trying to downgrade the phone back to android 11. Once i was done flashing the file to the phone and rebooted it doesn't boot anymore and only gives me a booting screen for a few seconds after I hold down the power and volume up button for a few seconds nothing else works. I have use the MSM tool and put my phone into EDL mode and it detected the phone with a black screen. Every time I use the tool it works till about 18% then it gives me a Sahara communication failed error and then my phone gets out of EDL mode.. I installed all the drivers needed on my PC and used multiple USB 2.0 slots but it still fails. Any help would be appreciated.
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
scanman0 said:
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
Click to expand...
Click to collapse
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
z67gp said:
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
Click to expand...
Click to collapse
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com