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....
Hello there.
Just like title says - I've got my hands on new Redmi 9 (lancelot) nfc 4/64 version. I've unlocked it from Mi stuff successfully yesterday and wanted to install there twrp, magisk and titanium backup to clean a bit and maybe to have foundations for further change of rom.
However, my phone gaves answers, that I do not understand correctly.
Firstly - after first instalation of twrp via adb it booted into this. However, after choosing option to boot to system from it, power off via ui and then another try to enter recovery...it gave me stock miui recovery again. When I've tried the same steps for second time, phone finished, but after restart it entered bootloop. I've followed steps from this guide - https://miui.blog/redmi-9/download-install-twrp-and-root-redmi-9-codename-lancelot/
After some time I've managed to make low-level rom instalation again (12.0.4 official lancelot rom, dated 31st of Mar, 21) to at least being able to communicate with it (done with usage of miflash 2018 version and rom in *.tgz file). This time, I've used help from this page - https://www.getdroidtips.com/guide-flash-miui-rom-xiaomi-devices/ - had some troubles with mediatek based phones before in my life, so it wasn't from scratch, but some time to understand it were needed.
Phone is working again, but this rom is based on Android 10 (which I would like to keep, if it won't cause too much trouble). And I think because of that fastboot mode changed now into fastbootD mode, where old commands from adb does not recognize the device, thus no flashing recovery action etc can be taken.
Is there a workaround here? I've stumbled across some articles about installing clean Generic System Image with Android 10 on this phone (since it has been released with android greater, than number 8), but again - this requires to have custom recovery, prefeably twrp. I cannot do anything about it, because I got back to stock recovery (which now at least works, yesterday phone was so twisted at one point, that he cannot even load this recovery, but somehow managed to open system and fastboot modes normally (!!!)).
Is there a way to work it out? Older miui version, older android version, then twrp, then update via twrp? Or an alternative method, since google changed something in partitions again (not sure, if I get it right, but it might be it)? I would actually like to stay somewhere around miui (at least let it be official with ota support without too much issues), but without twrp I cannot do anything. I also do know, that there aren't any official twrp/pbrp yet (just betas). Could it also be the issue with troubles with installing it and staying it on the phone?
buczek0711 said:
Hello there.
Just like title says - I've got my hands on new Redmi 9 (lancelot) nfc 4/64 version. I've unlocked it from Mi stuff successfully yesterday and wanted to install there twrp, magisk and titanium backup to clean a bit and maybe to have foundations for further change of rom.
However, my phone gaves answers, that I do not understand correctly.
Firstly - after first instalation of twrp via adb it booted into this. However, after choosing option to boot to system from it, power off via ui and then another try to enter recovery...it gave me stock miui recovery again. When I've tried the same steps for second time, phone finished, but after restart it entered bootloop. I've followed steps from this guide - https://miui.blog/redmi-9/download-install-twrp-and-root-redmi-9-codename-lancelot/
After some time I've managed to make low-level rom instalation again (12.0.4 official lancelot rom, dated 31st of Mar, 21) to at least being able to communicate with it (done with usage of miflash 2018 version and rom in *.tgz file). This time, I've used help from this page - https://www.getdroidtips.com/guide-flash-miui-rom-xiaomi-devices/ - had some troubles with mediatek based phones before in my life, so it wasn't from scratch, but some time to understand it were needed.
Phone is working again, but this rom is based on Android 10 (which I would like to keep, if it won't cause too much trouble). And I think because of that fastboot mode changed now into fastbootD mode, where old commands from adb does not recognize the device, thus no flashing recovery action etc can be taken.
Is there a workaround here? I've stumbled across some articles about installing clean Generic System Image with Android 10 on this phone (since it has been released with android greater, than number 8), but again - this requires to have custom recovery, prefeably twrp. I cannot do anything about it, because I got back to stock recovery (which now at least works, yesterday phone was so twisted at one point, that he cannot even load this recovery, but somehow managed to open system and fastboot modes normally (!!!)).
Is there a way to work it out? Older miui version, older android version, then twrp, then update via twrp? Or an alternative method, since google changed something in partitions again (not sure, if I get it right, but it might be it)? I would actually like to stay somewhere around miui (at least let it be official with ota support without too much issues), but without twrp I cannot do anything. I also do know, that there aren't any official twrp/pbrp yet (just betas). Could it also be the issue with troubles with installing it and staying it on the phone?
Click to expand...
Click to collapse
After to flash TWRP you have to flash the vbmeta.img and then boot to TWRP not through commands but manually with hardware buttons, don't allow device to boot to system before to boot to custom recovery otherwise this will be overwritten again.
I've done that with this vbmeta, one and only difference might be that I was trying to get into twrp by commands (however, it did not work XD). Overwritten isn't an issue in my opinion, since I do have booted to recovery after installing it yesterday and then from it choose option "reboot to system". After poweroff from system and then trying to get into recovery, then stock showed.
I'm currently trying this - https://c.mi.com/oc/thread-3312019-1-0.html
After putting this command to cmd - bcdedit /set testsigning on lancelot shows somewhere, but I cannot install it (most likely due to this issue about encrypted drivers). I'll try to overcome it now.
Yea, well, I've tried this method from link listed above, phone still enters fastbootd mode, still is not-visible from cmd started from google platform tools folder (which a subfolder to working adb). Not sure what to do now.
buczek0711 said:
I've done that with this vbmeta, one and only difference might be that I was trying to get into twrp by commands (however, it did not work XD). Overwritten isn't an issue in my opinion, since I do have booted to recovery after installing it yesterday and then from it choose option "reboot to system". After poweroff from system and then trying to get into recovery, then stock showed.
I'm currently trying this - https://c.mi.com/oc/thread-3312019-1-0.html
After putting this command to cmd - bcdedit /set testsigning on lancelot shows somewhere, but I cannot install it (most likely due to this issue about encrypted drivers). I'll try to overcome it now.
Click to expand...
Click to collapse
No, this is not the method to boot to recovery from what I pointed out, you don't have to firstly power off device but from fastboot commands you can type either fastboot or fastbootd reboot and inmediately press the volume up till the TWRP logo appears, the fastboot/d command will act same as it be the power button.
The thread explains how to install unsigned drivers in Windows, not to set it on your Redmi but is for your PC. If you succesfully get the drivers installed then you have to reboot your PC entering again in safe mode (not normal mode) and from there the commands through fastbootd are generally the same than those for fastboot.
buczek0711 said:
Yea, well, I've tried this method from link listed above, phone still enters fastbootd mode, still is not-visible from cmd started from google platform tools folder (which a subfolder to working adb). Not sure what to do now.
Click to expand...
Click to collapse
Just to be sure you are doing fine and not missing something the adb commands work while device is on and fastboot/d commands work only in fastboot mode.
Can you attach some SS to see what you are typing and the error that brings the cmd?
Hm, you say, that I can type fastbootd into cmd and this will be recognised? It seems that it cannot be recognised in this case, when I'm trying to type fastbootd powershell says "unknown command".
Typing fastboot /d devices results in "waiting for device", despite phone being in fastbootd all the time.
I'll attach ss tomorrow - it is time to sleep for me now, gotta wake up early. Then we will also know something else, when it comes to behavior after restart pc (once again, I've done it all in one sit, it might be an issue here).
PS. if you want english errors, I'll have to use powershell - cmd is in my native language (polish). Found out, that it doesn't really matter, which program you use, powershell simply can do more, while cmd dates back 30 years or so.
Anyway - phone is still booting to miui 12 and android 10 normally, I do not set there google acc or lock yet, so don't know if there's any issue with it (most likely no).
I've also stumbled across some dude from indonesia, who had the same phone, miui 12.0.1 with android 10 and he installed successfully twrp, then magisk, but he also put some small img - misc misc.img. Could it be the issue?
I'm giving link to this material on YT -
FROM WHAT I SEE IN THE THUMBNAIL, this version of twrp is even the same (code number and english translated from chinese), that once worked here (md5 of the file might be different, though).
There's also an option to reinstall again whole adb, platform tools, drivers from official miunlock app etc, but since I do not had ANY android-related problems on this pc with previous phones, I'm not sure if this is worth our time.
And I think that if I would misspell something in cmd program would give me error instantly, instead of behaving like it was nothing - i've made tons of errors before and cmd/powershell always informed me about it in first line of their texts.
buczek0711 said:
Hm, you say, that I can type fastbootd into cmd and this will be recognised? It seems that it cannot be recognised in this case, when I'm trying to type fastbootd powershell says "unknown command".
Typing fastboot /d devices results in "waiting for device", despite phone being in fastbootd all the time.
Click to expand...
Click to collapse
Yes, fastboot works normally while in cmd, this is intended for that, no problem to enter firstly toi Power Shell but you can switch to cmd from PS just typing cmd and all the commands from here will be for cmd, doesn´t matter at all how many old is, cmd can work inside PS keeping the same aspect.
buczek0711 said:
I'll attach ss tomorrow - it is time to sleep for me now, gotta wake up early. Then we will also know something else, when it comes to behavior after restart pc (once again, I've done it all in one sit, it might be an issue here).
PS. if you want english errors, I'll have to use powershell - cmd is in my native language (polish). Found out, that it doesn't really matter, which program you use, powershell simply can do more, while cmd dates back 30 years or so.
Anyway - phone is still booting to miui 12 and android 10 normally, I do not set there google acc or lock yet, so don't know if there's any issue with it (most likely no).
I've also stumbled across some dude from indonesia, who had the same phone, miui 12.0.1 with android 10 and he installed successfully twrp, then magisk, but he also put some small img - misc misc.img. Could it be the issue?
I'm giving link to this material on YT -
FROM WHAT I SEE IN THE THUMBNAIL, this version of twrp is even the same (code number and english translated from chinese), that once worked here (md5 of the file might be different, though).
There's also an option to reinstall again whole adb, platform tools, drivers from official miunlock app etc, but since I do not had ANY android-related problems on this pc with previous phones, I'm not sure if this is worth our time.
And I think that if I would misspell something in cmd program would give me error instantly, instead of behaving like it was nothing - i've made tons of errors before and cmd/powershell always informed me about it in first line of their texts.
Click to expand...
Click to collapse
You don't need to reinstall nothing, just from the downloaded SDK platform do all that you want to avoid misspelling path and folder directories, I mean place the files you need to use in the same directory and open terminal prompt (PS) in the same folder where adb/fastboot binaries are, pressing right mouse button and shift at same time.
I feel you are missing something simply here, not so hard to do.
The misc.img partition that you mentioned is just to restore something that went wrong in the process.
But if you are happy with this Miui ROM then great. No hurry to answer that, give your time to rest.
I also feel, that there is something simply to overcome, Only the fastbootd is new Stuff to me. However, any time I was doing something with Snap, i was long after finish by the current time (almost a month with It and 3rd day with fastbootd issue).
I don't get it. Now when I've tried to enter fastboot mode...phone entered it (fastboot, not fastbootD). Then I've installed pitch black recovery and sucessfully booted into it by restarting phone and then pressing vol up. Now I'm trying with magisk and another entry to pbrp.
Second try gave me stock recovery again. What is wrong with it XD?
something is wrong. Installing twrp resulting in nothing (stock recovery is still there), installing pitch black resulting in successfully boot into new recovery. However, this recovery does not see any zip (magisk zip, to be exact, that I've put there before it to root phone). After boot into system and then power it off to boot into recovery...phone boots into stock recovery. Should I downgrade system to miui 11 to be able to get over it? Or should I wait until miui 12.5 enters redmi 9?
My tries of installing it has been done by using cmd with admin rights, if it does make any difference.
buczek0711 said:
something is wrong. Installing twrp resulting in nothing (stock recovery is still there), installing pitch black resulting in successfully boot into new recovery. However, this recovery does not see any zip (magisk zip, to be exact, that I've put there before it to root phone). After boot into system and then power it off to boot into recovery...phone boots into stock recovery. Should I downgrade system to miui 11 to be able to get over it? Or should I wait until miui 12.5 enters redmi 9?
My tries of installing it has been done by using cmd with admin rights, if it does make any difference.
Click to expand...
Click to collapse
I think you are not following the right direction, if you want consider what I pointed out; you don't have to power off device prior to boot to recovery for first time but you have to type from fastboot (no matter fastbootd) and inmediately from there boot to the custom recovery, when you succesfully booted to custom recovery then flash the recovery zip if there is one (PBR and OFR have one) and if not a zip then flash the image again to the recovery partition, also check if there is some installer apart from the image that can fix it in the ramdisk partition, at this point your issue is solved, next step is to reboot device to system normally, if you don't have any issue on that then OK but if you can´t there some steps more that you should do, but let this for last.
Ok, let's group it.
I do not think that particular matter of how do I restart phone matters here (at least, I do not believe it, that it does anything).
Option to restart to recovery from adb still not working.
Trying to find magisk.zip in main directory of internal storage still fails under pitch black recovery project.
From new stuff - I now got an error message, while opening pbrp, most likely with the issues about system being read-only (not sure though, since I do not remember it now, might look into it once more). I have the options to mount partitions, available from main menu, but since I do not used it at all before, I do not know, how to deal with it.
Also - my system boots normally, it must have overwritten recovery (or at least header of it) sometime during boot, since custom recovery is unavailable to access after first full reboot.
I'll try now to install newer version of twrp from yt that I've posted days back. I would also try with orange fox (however, i cannot find img for it, just source code, don't get it).
Is there someone, who can and will to help me?
Situation looks this - on this 12.0.4 MIUI with android 10 I'm unable to install ANY recovery (either phone do not restart to recovery after proper command from cmd or it boots into it, but after visiting system and then to recovery again it shows stock (even without any operations or updates from ota).
I cannot force to work either twrp 3.4.2b, twrp 3.5.2, pitch black recovery 3.0.0 beta.
After trying to install magisk 21.4 zip from twrp 3.4.2b phone entered bootloop, because f**k you, user, I cannot even get it to fastboot mode now (btw, fastboot now works, fastbootD is luckily a long-gone crap).
All cmd's have been run with admin rights. There are NO SUCH THING, as misspelling (cmd and adb would not execute command ,if it is misspelled, either command or filename). I've installed drivers once again and used cmd from dedicated folder with adb fastboot portable version (runned as admin, of course).
Now I'm downloading older version of rom for fastboot (miui 11.0.9) with android 10. Something has to finally work on this piece of junk.
Writting each time is success (cmd says "OKAY" nad displays time, it took to do so), downloading recovery image to start from it also works, there aren't any errors in cmd, yet phone still isn't working.
Where's the issue with it? Apart from being mediatek, which seems to somehow enormously hardened any flashing? I did not encounter anything like this with qualcomm, yet mediatek still manages to pisses me off with their really weird implementations and working (???) of their stuff.
another update from battlefield. Managed to finally get mediatek verify bypass in smart phone flashing tool, however it ended with forcing me to format anything in the phone (if not, program would not let me install anything).
Second problem is forcing me to disable verify, yet command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img put in fastboot mode (yes, it works now) does not work, because adb says, that "--disable-verity" is not a recognised command.
SPFT cannot properly download images from phone and welcomes me with error about download exception, happening either in recovery part or in boot part. SInce I do have access to fastboot now, I can overcome it (I think).
Old miflash tool to install roms via fastboot says it cannot flash rom in locked stage (I might have lost unlocked status, but I'm not sure about it). Do you know ways to overcome it?
It is me again (inb4 use edit). Had to unlock phone again by using miphone unlocker (it went ok). Still cannot flash using SPFT, miflash started showing idiotic errors like "no file in directory" or "cannot access to directory" (it could before, I did not changed name of it). Will continue reporting of progress (or the so-called "progress").
After trying to flash TWRP (by following this guide: https://www.thecustomdroid.com/root-oneplus-6t-guide/ ) my device would no longer boot to the OS,but (stock) recovery and fastboot modes worked, so I tried to fix it by flashing some Android 9 roms from https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-6t.3862516/ , and flashing a stock Android 10 boot.img (for some reason).
But my attemps at fixing it by flashing only made things worse, my current situation is as follows:
Device: Oneplus 6T (6/128)
Version (either Global or T-Mobile): Unsure
OxygenOS Version: Unsure, only know that it is Android 9
Bootloader: Unlocked
- Neither Recovery mode nor TWRP work
- Bootloader and Baseband versions show as empty
- I can only access Fastboot mode and EDL mode
- A power outage left my main pc (which had the drivers, permissions and backup i had been using, and need, to do this) a burning mess
- I´m currently using an old desktop computer i had stored (which has Windows 7), but it fails to recognize my device.
- I have installed and tried multiple versions of the Qualcomm, Oneplus, Adb and Android drivers, but it never recognizes it
- Windows doesnt allow me to manually select the drivers for the Unknown device as ¨the specified folder doesnt contain a software driver compatible with this device¨
- By searching the system and internet it always says that ¨the best software driver for this device is already installed¨
- Both of the above were tried with a disabled driver signature requirement
- When using it on the other PC, the msm download tool, it always said that the image didnt match the device, no matter which of the 13 versions I tried
- On my current PC, the msm download tool doesnt detect my device
I implore anyone that can provide any help or advise to do so, as I´ve already spent an entire week scouring the Internet (including the Oneplus and XDA forums) for any solution, but so far, nothing has worked. Have a good day and thank you for reading my post.
Hey man.
I'm a dude with no OnePlus 6T but have a OnePlus Nord N10. But I do know the really bad punch-in-the-gut feeling of not having a device work at all.
What does "fastboot reboot bootloader" show?? (Does your phone reboot to the bootloader upon that command being ran?)
Also did you try to flash the stock Android 9 boot.img that your device was updated to?
As for the MSM download tool, the last replies I've seen show that some people trying that on Win11 recently have got it working.
Also check if these work? https://www.thecustomdroid.com/oneplus-6-6t-unbrick-guide/
How to Unbrick Your OnePlus 6T When All Else Fails
When flashing files through TWRP, ADB, or Fastboot, there's a slight chance for things to go wrong. Whether it's user error related or something else entirely, it's always good to have a backup plan. In most cases, you'll be dealing with a semi-brick or soft-brick, which can usually be solved by...
oneplus.gadgethacks.com
Sorry if it sounds stupid but I want to try to help.
I really hope your phone gets fixed, man. Good luck!