Related
Hello there, after an hour of search and no useful results, i've decided to ask my question (sorry, if it's already been answered, but i didn't find anything)
I used the following procedure to flash the CWM recovery, but something goes wrong:
( http://forum.xda-developers.com/android/development/ufficial-thread-lenovo-k3-note-t3102997 )
1. "adb devices" shows the phone correctly (At this state the phone is properly shown in my windows device manager)
2. "adb reboot bootloader" pushes the phone to boot in fastboot mode
... but ...
3 "fastboot devices" doesn't find it anymore. (At this state the phone is shown as an unknown device in my windows device manager)
4. after some attempts I tried "fastboot flash recovery recovery.img" anyway, but as I expected, i was unable to reach the device, the image should be written to.
5. every the phone stucks in fastboot mode, and the only way to restart it is by pulling out the battery.
So, what is the possible reason, to loosing connection to the device after the reboot in fastboot mode? (phone drivers already installed, pc rebooted, ADB SDK installed too)
Thanks in advance for any help!
Regards!
thudrumble said:
Hello there, after an hour of search and no useful results, i've decided to ask my question (sorry, if it's already been answered, but i didn't find anything)
I used the following procedure to flash the CWM recovery, but something goes wrong:
( http://forum.xda-developers.com/android/development/ufficial-thread-lenovo-k3-note-t3102997 )
1. "adb devices" shows the phone correctly (At this state the phone is properly shown in my windows device manager)
2. "adb reboot bootloader" pushes the phone to boot in fastboot mode
... but ...
3 "fastboot devices" doesn't find it anymore. (At this state the phone is shown as an unknown device in my windows device manager)
4. after some attempts I tried "fastboot flash recovery recovery.img" anyway, but as I expected, i was unable to reach the device, the image should be written to.
5. every the phone stucks in fastboot mode, and the only way to restart it is by pulling out the battery.
So, what is the possible reason, to loosing connection to the device after the reboot in fastboot mode? (phone drivers already installed, pc rebooted, ADB SDK installed too)
Thanks in advance for any help!
Regards!
Click to expand...
Click to collapse
Hi,
I have the same problem. Any solution exists for that?
Thanks.
Same here. Some one saying it's driver issue, but I didn't have any errors installing the drivers and I tried different PCs, all the same...
Another reason I said it might not be a driver issue was that I used that PC to root the device successfully a while ago. But after updating to the newly released stock ROM, now this rooting method stuck in the fastboot mode.
I've tried another PC too ... same situation. It should be a phone problem and not a PC, since I've never used the second PC for rooting or such things before. Did someone tried other ways to root the K3 Note (apps etc.)?
Regards!
marskingbeatgates said:
Same here. Some one saying it's driver issue, but I didn't have any errors installing the drivers and I tried different PCs, all the same...
Another reason I said it might not be a driver issue was that I used that PC to root the device successfully a while ago. But after updating to the newly released stock ROM, now this rooting method stuck in the fastboot mode.
Click to expand...
Click to collapse
I've tried another PC too ... same situation. It should be a phone problem and not a PC, since I've never used the second PC for rooting or such things before. Did you tried other ways to root the K3 Note (apps etc.)?
Regards!
thudrumble said:
I've tried another PC too ... same situation. It should be a phone problem and not a PC, since I've never used the second PC for rooting or such things before. Did you tried other ways to root the K3 Note (apps etc.)?
Regards!
Click to expand...
Click to collapse
Hi,
I tried this method.. I can not add link. Try to find "How to root and install Google Play Store on Lenovo K3 Note" in youtube . And it did work for me. Root checker showed that root access is not fully. But I manage to install another rom.
This might help:
Go to the main thread...and jump to page 73 and read post #722
http://forum.xda-developers.com/k3-...vo-k3-note-t3102997/post61860445#post61860445
For a change, you could use another method:
Lenovo K3 Note Manager by Pr1nc3V located here: http://forum.xda-developers.com/k3-note/general/tool-lenovo-k3-note-manager-t3261285
freelancer81 said:
This might help:
Go to the main thread...and jump to page 73 and read post #722
http://forum.xda-developers.com/k3-...vo-k3-note-t3102997/post61860445#post61860445
For a change, you could use another method:
Lenovo K3 Note Manager by Pr1nc3V located here: http://forum.xda-developers.com/k3-note/general/tool-lenovo-k3-note-manager-t3261285
Click to expand...
Click to collapse
Thanks dude! The first method is the one, that won't work with my K3Note, but I'll try your plan B later today. Fingers crossed
cloudinio said:
Hi,
I tried this method.. I can not add link. Try to find "How to root and install Google Play Store on Lenovo K3 Note" in youtube . And it did work for me. Root checker showed that root access is not fully. But I manage to install another rom.
Click to expand...
Click to collapse
Thanks! I found the video and try this one too, if the freelancer81's method fail.
Mission accomplished
Mission accomplished? Kindly share how you were able to resolve it as I am still faced with the problem. I have tried all the recommendations here
same issues..
ADB sees the phone. but fastboot doesnt seem to connect / see it..
And no thats not the issue of not booting into the recovery as suggested, its not even able to flash the recovery.
stinvilla said:
Mission accomplished? Kindly share how you were able to resolve it as I am still faced with the problem. I have tried all the recommendations here
Click to expand...
Click to collapse
Anyone?
No one?
Lenovo k3 note stuck on logo
I want volte support in k3 note so I know the cm14 is with volte support when I am trying flash cm14 with twrp the zip file successful install. But in log show "E: unknown commad[log] two rows
After that when I power on the phone its stuck on logo.
Sorry for grammar errors
Give me solution....
I tried flashing "RR-N-v5.8.0-20170118-oneplus3-Unofficial-Test.zip" onto my new phone after I installed the lastest OTA via VPN Canada. Everything seemed find when I was flashing it through TWRP so I rebooted and my phone won't start or regonized by my PC. I'm currently trying to following the instructions from the following thread:
https://forum.xda-developers.com/on...ick-tutorial-oneplus-3t-t3515306#post69989929
If it doesn't work, is there any hope for this phone or should I contact OnePlus and ask for a replacement/return? I received it two days ago so my warranty shouldn't have been voided from me unlocking the bootloader and rooting my device.
Do You still boot into twrp?
bebanghonbi said:
Do You still boot into twrp?
Click to expand...
Click to collapse
Unfortunately no, but I followed the following guide and it worked like a charm:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Edit: I don't know how I got into this situation, but while trying to install TWRP and root my device on OxygenOS 3.5.1 I've ended up to a point where whenever I boot I'm stuck in an infinite loading screen where two white circles are circling a red dot in the center.
I have access to the stock recovery, but it doesn't seem like my device is being recognized when I type "adb devices". Can someone help me reboot to stock completely. At this point I've given up trying to do anything and if this problem is solved I probably won't do anything with my phone unless my hand is being held throughout the process.
Blkdrgn415 said:
Unfortunately no, but I followed the following guide and it worked like a charm:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Edit: I don't know how I got into this situation, but while trying to install TWRP and root my device on OxygenOS 3.5.1 I've ended up to a point where whenever I boot I'm stuck in an infinite loading screen where two white circles are circling a red dot in the center.
I have access to the stock recovery, but it doesn't seem like my device is being recognized when I type "adb devices". Can someone help me reboot to stock completely. At this point I've given up trying to do anything and if this problem is solved I probably won't do anything with my phone unless my hand is being held throughout the process.
Click to expand...
Click to collapse
If you use my tool, it will work every time
LloydSmallwood said:
If you use my tool, it will work every time
Click to expand...
Click to collapse
I tried the same method to solve my current device problem but there's an issue with it. My phone seems to just be soft bricked. I can still access the bootloader and stock recovery. The problem is that it's stuck in an infinite boot that I occurred when I tried to install SuperSU. When I plug my device in it lists it either as Android Phone or some kind of Qualcomm in device manager.
I assumed I could just flash an OTA of OxygenOS 3.4.1 or some stable variant, but it's my phone isn't being recognized when I type "adb devices". In addition, I'm not sure exactly what command I should use to flash. I hope someone can walk me through it step by step.
Hi,
I use a oneplus 3T
I had previously rooted my phone successfully using SuperSu and TWERP and I used it for 6 months. Now I tried to unroot it and did a full unroot using SuperSu. But my phone is stuck now. when I restart it oneplus logo comes. If I go to recovery mode, it just restart again and if I go to fastboot, nothing happens. When I connect my device to pc, it doesnt show up there. So I am not able to do fastboot because when I tried typing it, an error came.
Please someone help me out with this and guide me with a solution.
Thanks
EDIT:
Hey Guys after 5 hours of research and experimentation, I found the solution. If anyone in future have a similar problem, please PM me.
Abhimanyubadola said:
Hi,
I use a oneplus 3T
I had previously rooted my phone successfully using SuperSu and TWERP and I used it for 6 months. Now I tried to unroot it and did a full unroot using SuperSu. But my phone is stuck now. when I restart it oneplus logo comes. If I go to recovery mode, it just restart again and if I go to fastboot, nothing happens. When I connect my device to pc, it doesnt show up there. So I am not able to do fastboot because when I tried typing it, an error came.
Please someone help me out with this and guide me with a solution.
Thanks
Click to expand...
Click to collapse
Just download and flash your rom, assuming it's the stock OOS.
It will be unrooted afterwards.
Unleashed by ONEPLUS 3T rooted
RASTAVIPER said:
Just download and flash your rom, assuming it's the stock OOS.
It will be unrooted afterwards.
Unleashed by ONEPLUS 3T rooted
Click to expand...
Click to collapse
Hi, thanks for the reply.
I found out, I can fastboot because when I typed fastboot devices, it showed me the serial number.
Now I can't switch on my phone, because it gets stuck on the oneplus logo screen. I tried going in recovery but it still restarts. but i'm not able to access any screens other than fastboot.
I tried flashing TWRP. On pc it said successful. but no changes on my phone. I think I have accidentally deleted my OS and TWRP. but I cant figure out how to install these again.
How do I flash a ROM, if I can't access the storage of my phone.
I don't know what to do now.
Abhimanyubadola said:
Hi, thanks for the reply.
I found out, I can fastboot because when I typed fastboot devices, it showed me the serial number.
Now I can't switch on my phone, because it gets stuck on the oneplus logo screen. I tried going in recovery but it still restarts. but i'm not able to access any screens other than fastboot.
I tried flashing TWRP. On pc it said successful. but no changes on my phone. I think I have accidentally deleted my OS and TWRP. but I cant figure out how to install these again.
How do I flash a ROM, if I can't access the storage of my phone.
I don't know what to do now.
Click to expand...
Click to collapse
Try flashing another version of twrp using fastboot...open recovery....if it stuck on boot logo then wait for few minutes....it will work
Use power button and volume down button to boot into recovery!
Sent from my OnePlus3T using XDA Labs
Solved
Hey admin I got the solution. Please close this thread
Hey everybody
My friend gave me his Mi 9t Pro to repair it as he bricked it accidentally and he knew I had experience with changing ROMs and recoveries.
From what I know, what he did is tried to change dpi and then phone jumped into bootloop.
Let me just state that:
- bootloader is locked
- there is no custom recovery
- I have no authorization for ADB
I am stuck and would be really thankful for any ideas. Wiping data is not an option at the moment as we want to recover data from the phone.
Dropping battery to 0% and then charging didn't work.
Adb is only possible at the very short moment phone gets into boot animation, but as I have no authorization I can't pull files from it.
For whatever I tried ADB sideload when connected with Mi Assistant in recovery didn't help me neither.
If you have any ideas please share them with me, I'll appreciate that a lot
Hilus said:
Hey everybody
My friend gave me his Mi 9t Pro to repair it as he bricked it accidentally and he knew I had experience with changing ROMs and recoveries.
From what I know, what he did is tried to change dpi and then phone jumped into bootloop.
Let me just state that:
- bootloader is locked
- there is no custom recovery
- I have no authorization for ADB
I am stuck and would be really thankful for any ideas. Wiping data is not an option at the moment as we want to recover data from the phone.
Dropping battery to 0% and then charging didn't work.
Adb is only possible at the very short moment phone gets into boot animation, but as I have no authorization I can't pull files from it.
For whatever I tried ADB sideload when connected with Mi Assistant in recovery didn't help me neither.
If you have any ideas please share them with me, I'll appreciate that a lot
Click to expand...
Click to collapse
I can't see any way you're going to keep the data. Recovering the phone is going to wipe everything. Without an unlocked bootloader I can't see any way your going to be able to access the data first before restoring the phone.
As far as restoring the phone, if you can access the official recovery, then you should, hopefully, be able to flash an official recovery ROM from there, or so I believe, I've never actually tried it.
If that fails, then you will need to EDL flash the phone.
This involves taking off the back to put the phone in EDL mode, then paying someone, who has an authorised account, to remotely flash the phone for you.
Robbo.5000 said:
I can't see any way you're going to keep the data. Recovering the phone is going to wipe everything. Without an unlocked bootloader I can't see any way your going to be able to access the data first before restoring the phone.
As far as restoring the phone, if you can access the official recovery, then you should, hopefully, be able to flash an official recovery ROM from there, or so I believe, I've never actually tried it.
If that fails, then you will need to EDL flash the phone.
This involves taking off the back to put the phone in EDL mode, then paying someone, who has an authorised account, to remotely flash the phone for you.
Click to expand...
Click to collapse
Yeah, that's kinda hard situation :/
I can't really flash recovery ROM, cause official recovery has no option for that and adb sideload didn't want to install 'update.zip'. just rebooted the phone and that's all.
I've seen that it's actually possible to put device into EDL without having to disassemble the phone, but fastboot command just reboots the phone.
Thanks for answering either way
Hilus said:
Yeah, that's kinda hard situation :/
I can't really flash recovery ROM, cause official recovery has no option for that and adb sideload didn't want to install 'update.zip'. just rebooted the phone and that's all.
I've seen that it's actually possible to put device into EDL without having to disassemble the phone, but fastboot command just reboots the phone.
Thanks for answering either way
Click to expand...
Click to collapse
Have you tried updating ROM through Mi PC Suite (latest version)?
0xFast said:
Have you tried updating ROM through Mi PC Suite (latest version)?
Click to expand...
Click to collapse
I tried through MiFlash, but it only allows fastboot ROMs, and because bootloader is not unlocked I couldn't flash it. But that's a good idea, I'll try Mi PC Suite, I'll let you know how it ends.
0xFast said:
Have you tried updating ROM through Mi PC Suite (latest version)?
Click to expand...
Click to collapse
I tried, but seeing that mipcsutie is same program as mi assistant, I cannot do anything because it doesn't recognize my phone.
Which version? I'm using https://c.mi.com/thread-1015363-1-0.html on Redmi 6 (locked bootloader & bootloop) and successfully restore. Make sure you've correct driver installed.
---------- Post added at 12:13 AM ---------- Previous post was at 12:10 AM ----------
Because not possible if your bootloader was locked to enter EDL mode, then AFAIK you need Mi Account with authorization to flashing with EDL mode.
Hilus said:
I've seen that it's actually possible to put device into EDL without having to disassemble the phone, but fastboot command just reboots the phone.
Click to expand...
Click to collapse
Are you talking phones in general, or this phone specifically. For this phone the only way is to take the back off and do the 'Test point' method. I've never heard of anyone successfully entering EDL mode using any other method.
Hilus said:
I can't really flash recovery ROM, cause official recovery has no option for that and adb sideload didn't want to install 'update.zip'. just rebooted the phone and that's all.
Click to expand...
Click to collapse
ADB sideload needs the phone to be put into ADB sideload mode first, so to speak. This is why you have the ADB sideload option in TWRP. You don't have this option in the standard recovery.
Hilus said:
I tried, but seeing that mipcsutie is same program as mi assistant, I cannot do anything because it doesn't recognize my phone.
Click to expand...
Click to collapse
0xFast said:
Which version? I'm using https://c.mi.com/thread-1015363-1-0.html on Redmi 6 (locked bootloader & bootloop) and successfully restore. Make sure you've correct driver installed.
Click to expand...
Click to collapse
Also make sure you're using a good USB cable and also try a different USB port.
Also try using your friends PC. I assume they have previously connected the phone to the PC successfully before, so they should have the correct drivers already installed.
Robbo.5000 said:
Are you talking phones in general, or this phone specifically. For this phone the only way is to take the back off and do the 'Test point' method. I've never heard of anyone successfully entering EDL mode using any other method.
ADB sideload needs the phone to be put into ADB sideload mode first, so to speak. This is why you have the ADB sideload option in TWRP. You don't have this option in the standard recovery.
Also make sure you're using a good USB cable and also try a different USB port.
Also try using your friends PC. I assume they have previously connected the phone to the PC successfully before, so they should have the correct drivers already installed.
Click to expand...
Click to collapse
If you connect via 'Mi Assistan' option in recovery the phone connects to pc using adb sideload.
I tried different cables and ports, and I have correct drivers.
0xFast said:
Which version? I'm using https://c.mi.com/thread-1015363-1-0.html on Redmi 6 (locked bootloader & bootloop) and successfully restore. Make sure you've correct driver installed.
---------- Post added at 12:13 AM ---------- Previous post was at 12:10 AM ----------
Because not possible if your bootloader was locked to enter EDL mode, then AFAIK you need Mi Account with authorization to flashing with EDL mode.
Click to expand...
Click to collapse
As I mentioned before, I am not able to enable USB debugging, which is required for this program to work as far as I can see.
Hilus said:
As I mentioned before, I am not able to enable USB debugging, which is required for this program to work as far as I can see.
Click to expand...
Click to collapse
In this case your only option now is to EDL flash. Sorry. Search for guides on how to do this, within these forums. XDA admins have been removing contact details of anyone with an authorised account, who will remotely flash for you. These people charge for doing this, so it's against XDA policy to give details of people who perform paid for services. You will find recent posts from people who've got details of these people who can EDL flash, that will kindly allow you too PM them for details of such persons.
Hilus said:
As I mentioned before, I am not able to enable USB debugging, which is required for this program to work as far as I can see.
Click to expand...
Click to collapse
AFAIK, USB debugging not required just adb sideload to work.
Have you tried looking at the .bat files miflash executes from the fastboot images. You can flash system etc.. without dating perhaps this will reset the dpi
after updating from miui 13 to miui 14 via OTA was a disaster. My phone stuck into the bootloop. Can use it anymore. Is there any solution to get rid of it?
asifneowaz2 said:
after updating from miui 13 to miui 14 via OTA was a disaster. My phone stuck into the bootloop. Can use it anymore. Is there any solution to get rid of it?
Click to expand...
Click to collapse
No way to know what parts are missing. You can reflash your current ROM or the original ROM via fastboot.
Can you enter fastboot mode?
asifneowaz2 said:
after updating from miui 13 to miui 14 via OTA was a disaster. My phone stuck into the bootloop. Can use it anymore. Is there any solution to get rid of it?
Click to expand...
Click to collapse
If your bootloader was unlocked you can recover the device via fastboot.
If not you have the same situation as described here:
Redmi Note 10 pro stuck on Mi logo loop after update
I tried wiping my data, but no success. I tried mi flash tool but no scucces. My bootloader is lock. I can boot into fastboot and recovery mode only. Safe mode also loop into logo only. can anyone tell how i can flash stable rom.
forum.xda-developers.com
Interesting to see that several people are reporting bootloop after upgrading to MIUI 14.
My advice to anyone is to unlock the bootloader before upgrading to MIUI 14 to avoid having a brick, which you can't recover by your own by just flashing.
minax007 said:
If your bootloader was unlocked you can recover the device via fastboot.
If not you have the same situation as described here:
Redmi Note 10 pro stuck on Mi logo loop after update
I tried wiping my data, but no success. I tried mi flash tool but no scucces. My bootloader is lock. I can boot into fastboot and recovery mode only. Safe mode also loop into logo only. can anyone tell how i can flash stable rom.
forum.xda-developers.com
Interesting to see that several people are reporting bootloop after upgrading to MIUI 14.
My advice to anyone is to unlock the bootloader before upgrading to MIUI 14 to avoid having a brick, which you can't recover by your own by just flashing.
Click to expand...
Click to collapse
Excellent advice about "waiting" to first unlock and actually unlocking it before doing any upgrades.
Sheist! said:
Excellent advice about "waiting" to first unlock and actually unlocking it before doing any upgrades.
Click to expand...
Click to collapse
Thank you.
But could you please explain what you mean with "waiting"?
I assume that you mean the seven days until Xiaomi grants you the possibility to unlock the bootloader, right?
minax007 said:
Thank you.
But could you please explain what you mean with "waiting"?
I assume that you mean the seven days until Xiaomi grants you the possibility to unlock the bootloader, right?
Click to expand...
Click to collapse
Don't upgrade software until you first unlock bootloader.
Sheist! said:
Don't upgrade software until you first unlock bootloader.
Click to expand...
Click to collapse
I agree with regards to this device.
But usually it is not a problem.
With regards to this device I see from two other people that they are facing a bootloop when updating to MIUI 14.
I also did the update and my device ended up in a bootloop.
But I had unlocked the bootloader in advance and could recover the device by flashing.
waw .... 1,000,000 phones sold, update ban ... 50 year old aunty needs to unlock bootloader soon to run update ....
The xda community will grow
Ashle said:
waw .... 1,000,000 phones sold, update ban ... 50 year old aunty needs to unlock bootloader soon to run update ....
The xda community will grow
Click to expand...
Click to collapse
You think that aunty will know about XDA either?
How can I unlock bootloader on my Redmi note 10 pro (global) please
asifneowaz2 said:
after updating from miui 13 to miui 14 via OTA was a disaster. My phone stuck into the bootloop. Can use it anymore. Is there any solution to get rid of it?
Click to expand...
Click to collapse
Could you explain the nature of ur bootloop please... Does it just stay in the MI logo with the three loading dots underneath or does it reach lock screen occassionally?
Dheerajvirgo said:
Could you explain the nature of ur bootloop please... Does it just stay in the MI logo with the three loading dots underneath or does it reach lock screen occassionally?
Click to expand...
Click to collapse
Hi
Greetings, I am facing the same problem, after upgrade to miui14 the phone is in bootloop,
Explanation
1) The phone starts and enters menu(reboot, wipe data, connect with MI assistant, safe mode)
2) If i click reboot, it will reboot and reach to welcome screen and then it will ask me to activate the phone
Thats it
Then it restarts automatically
This process repeats untill battery drain
The phone is not unlocked
Advice .........
Justfamous said:
How can I unlock bootloader on my Redmi note 10 pro (global) please
Click to expand...
Click to collapse
That is actually very easy. There is a tool. Mi_Unlock-en-5.5.224.24. you will need to- (a) go into fastboot mode(Switch on by pressing power+volume down) (b) Connect phone via USB Cable. Have the proper drivers installed. (c) Launch Mi Unlock tool and login into Mi Account. (d) refresh to search phone, select and press unlock. Takes a couple of seconds to unlock the bootloader.
Agent03 said:
Hi
Greetings, I am facing the same problem, after upgrade to miui14 the phone is in bootloop,
Explanation
1) The phone starts and enters menu(reboot, wipe data, connect with MI assistant, safe mode)
2) If i click reboot, it will reboot and reach to welcome screen and then it will ask me to activate the phone
Thats it
Then it restarts automatically
This process repeats untill battery drain
The phone is not unlocked
Advice .........
Click to expand...
Click to collapse
Unlock the bootloader by following the solution described above .
Download and install MiFlashtool 2017.4.25.0.
Download a stable fastboot ROM suitable for your device and place the unzipped folder in the same folder as MiFlashtool C:\xiaomi\XiaoMiFlash
Boot device into fastboot mode and connect.
Flash the ROM. Just it.
jinvary said:
That is actually very easy. There is a tool. Mi_Unlock-en-5.5.224.24. you will need to- (a) go into fastboot mode(Switch on by pressing power+volume down) (b) Connect phone via USB Cable. Have the proper drivers installed. (c) Launch Mi Unlock tool and login into Mi Account. (d) refresh to search phone, select and press unlock. Takes a couple of seconds to unlock the bootloader.
Click to expand...
Click to collapse
Hmmmm
A lot of people face difficulty unlocking MIUI bootloader.
To avoid frustration I suggest you do some Googling to find the full guide to unlocking.
Like this one ...https://new.c.mi.com/global/post/101245
Note the 168 hrs wait
Does unlocking the bootloader erase the device's data?.
andrescm said:
Does unlocking the bootloader erase the device's data?.
Click to expand...
Click to collapse
Yes