Database Develop

stuck to fastboot when try to flash recovery [Lenovo K3 Note]

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....

xaiomi mI5 loop,stuck.

hi friends, i need so much your help!.
I have xaiomi mi5, the operating system of the cellphone has been updated, and then the device has entered the loop.
He can not get up at all.
I've tried to do so far:
FAST BOOT - but even the computer can not read the device despite all the permissions I have approved for the computer.
MIPCSUIT - does not work well because the computer does not recognize the device.
Your help must be smart and good people!

I am also stuck with the same problem.
At least I can get fastboot.
I think if you OK to loose data then just go to recovery mode with Volume up + power button pressed together. And wipe all. This may solve the problem. But I don't want to loose data I am skipping this option.
If any one knows other way to unbrick without full wipe then please let us know.
Thanks

have you unlocked bootloader?
you can try run by fastboot twrp recovery mode.
Code:
fastboot boot twrp.img
after few seconds phone boot to recovery, you can encrypt the phone and copy data.
twrp is here

My bootloader is locked I think.
I tried that command. Didn't boot to twrp.
Any other way.
Anyway Thanks for suggesting.

Are you on latest MIUI global stable? I think Xiaomi's guys ****ed it up this time around and got bootloop for everybody on latest update.
Take a read here and good luck: http://en.miui.com/thread-2776961-1-1.html

ok listen me... if you have got unlock permission and unlocked your phone or you have unlock code.. you must bind your acc with other xiaomi phone easly enter your acc and bind acc now go fastboot download mi flash unlocker install adb driver and unlock then you can flash stock rom i had that problem and i solved

Hello,
I had similar issue.
To be able to start phone/miui you should remove sim card,
in my case it was connected to connecting to cell network that caused reboot.
Than it will be possible to update phone using WiFi.
For me issue was solved with V9.5.2.0.NAAMIFA update.
BR Jarek.

jarek102 said:
Hello,
I had similar issue.
To be able to start phone/miui you should remove sim card,
in my case it was connected to connecting to cell network that caused reboot.
Than it will be possible to update phone using WiFi.
For me issue was solved with V9.5.2.0.NAAMIFA update.
BR Jarek.
Click to expand...
Click to collapse
Lifesaver here!
This worked perfectly for me! Go figure?
Cheers

You can try
I tried version gemini global images v10.2.2.0. OAAMIXM 2019115 GLOBAL but failed then tried v8.11.22.20181122.000 8.0 GLOBAL but failed then 2 month later i tried with good battery and good on off and main important is version GEMINI GLOBAL IMAGES 6.11.10 _20161110 and version GEMINI GLOBAL IMAGES V7.2.4.0.MAAMIDC 20160129. AND GUESS WHAT SUCCESS. NEVER TRY WITHOUT BATTERY AND WITHOUT EDL POINT. EDL POINT FOR UNLOCKING BOOTLOCK AND DOWNLOAD SOFTWARE FLASH FILES WITH GOOD INTERNET WITHOUT INTERUPPT SO FLASH SUCCESS. MY 2 MOTHERBOARD OF MI5 SAVED WITHOUT HARDWARE. HOW TO KNOW SOFTWARE OR HARDWARE....1ST CHECK CHARGING HAPPENING OR NOT IN SWITCH OFF AND CAN IT GO TO FASTBOOT MODE OR RECOVERY MODE. IF ALL THIS GOOD GO FOR FLASH IN SAME PROCESS. OTHERWISE HARDWARE AS STATED THAT RESISTOR ALSO PLAY A VITAL ROLE IN BOOTING OR STUCK AT MI LOGO. MOISTURE IN PHONE UNDER IC REQUIRE HEAT WITH PASTE AT HARDWARE LEVEL.

HELP!!!!!! Any unbrick tool for cn rom?

Hey guys,
I need some assistance as I am not able to unbrick my RM3 with unbrick tool. Multiple times I have already got it worked, flashed many times, but this time I am not getting my phone started. Normally, I use the NON-EU unbrick tool, all goes well but this time, it says THIS DEVICE CAN'T BE TRUSTED, WON'T BOOT UP. After multiple tries, I tried that EU unbrick too as well, but the same result.
I think I have locked the bootloader while on CN Rom 5.14, most probably this is the only reason, I was doing some tweakings and got it bricked. Anyone here who can tell me if there is such thing named CN Unbrick tool or any other way around to get it worked. I can enter FASTBOOT and EDL Mode but recovery mode showing black screen and adb is not recognising as didn't enable USB debugging. please help...

[email protected] said:
Hey guys,
I need some assistance as I am not able to unbrick my RM3 with unbrick tool. Multiple times I have already got it worked, flashed many times, but this time I am not getting my phone started. Normally, I use the NON-EU unbrick tool, all goes well but this time, it says THIS DEVICE CAN'T BE TRUSTED, WON'T BOOT UP. After multiple tries, I tried that EU unbrick too as well, but the same result.
I think I have locked the bootloader while on CN Rom 5.14, most probably this is the only reason, I was doing some tweakings and got it bricked. Anyone here who can tell me if there is such thing named CN Unbrick tool or any other way around to get it worked. I can enter FASTBOOT and EDL Mode but recovery mode showing black screen and adb is not recognising as didn't enable USB debugging. please help...
Click to expand...
Click to collapse
I think any unbrick tool should work both EU and non EU

you must pc driver uninstall reboot pc driver install again reboot your pc and also check your port number eld mode

red magic 3 driver reinstall in may case port number change automaticly i m notice this point it will help you to start your device red magic 3

Question The current image (boot/recovery) have been destroyed

Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!

Update: If someone would be able to extract a scatter file from their own OnePlus Ace too, I think that may help me

Sorry that you've ran into this, but thanks for confirming bootloader can be unlocked, and root is possible.
Getting the 10R over the Realme GT 2 (sad situation of bootloader unlock not possible). Hope you get an extract soon

Made some progress!
Got my hands on the Ace's firmware files, which included the scatter file. Redownloaded the newest 6.2 version of SP Flash Tool and loaded the scatter and auth files successfully. Clicked download, connected USB to phone while holding Vol + and Vol - and finally! Sp Flash Tool connected to the phone! However, now I've run into another problem: SP Flash Tool will show a red progress bar at the bottom saying 'Download DA', it will reach 100% quickly then throw me a very vague error simply saying 'error_msg'. And that's it. Tried unchecking different boxes, reinstalled drivers but it will always throw back this error.
Any ideas to figure out what the error is and fix it would be amazing

hello, im here to show support. My ace also bricked because i want to change from color os to oxygen. I used fastboot enhanced, might have missed a step and bricked. Mine also import, but the shop i bought offers 1 year warranty. Shop says have to wait for msm download tools to reflash or i have to pay $60 to send back to China because my own fault. Man, it is going to be a long wait for msm tools. haha

KeepingKeyes said:
saying 'error_msg'.
Click to expand...
Click to collapse
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware

DimRim said:
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware
Click to expand...
Click to collapse
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware

KeepingKeyes said:
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware
Click to expand...
Click to collapse
maybe this is because of the new chip and there is no support for bypassing it.I thought the method would work.also a tip-edit the scatter file, namely partition_name: super or system,changing the value is_download: false to is_download: true.hopefully help
And thank you for sharing the files

I too am stuck with Brick.
Is there a Bypass for the Demesity 8100 being developed?
This device is mostly Oppo, but there is no Oppo flash Tool?
There is very little information available.

KeepingKeyes said:
Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Still stuck or were you able to find any solution?

yashaswee1708 said:
Still stuck or were you able to find any solution?
Click to expand...
Click to collapse
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials

KeepingKeyes said:
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials
Click to expand...
Click to collapse
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.

yashaswee1708 said:
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.
Click to expand...
Click to collapse
I seem to have made fastboot inaccessible on my device, so I've been unable to use Fastboot enhance or utilise any ways to flash using fastboot

Damn!! I hope you find some way to fix your device. Good luck.

关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安

I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate

GTAstar said:
I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate
Click to expand...
Click to collapse
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.

hamsteer said:
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.
Click to expand...
Click to collapse
Are you still able to boot to Fastboot?

yashaswee1708 said:
Are you still able to boot to Fastboot?
Click to expand...
Click to collapse
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.

hamsteer said:
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.
Click to expand...
Click to collapse
So you are not able to boot right?
If not, you can try flashing the partitions manually from fastboot. (If you are willing to try I can provide the steps. This works for other OnePlus devices.)

Question Need Expert who can help in unbrick the realme x7 max. As hard bricking is getting common with new ROMs

Recently hard bricked my x7 max and while using MTK/SP tools gettings errors so need someone to help. I have seen so many people with same issues but no details troubleshooting guide here and also on YT.
Steps i took
Unlock bootloader(with stock rom and RUI4, Android 13, latest update)
Installed TWRP(found one twrp that actually worked but i was not able to backup the rom, showing errors while taking backup, error 255)
I thought i can revert on stock using SP tools so moved ahead
Once in TWRP, i installed Project elixir ROM and rebooted to bootloader, phone got dead.
I tried VCOM,linusb,SP flash tool and MTK Authbypass (brom waiting , maybe some issue in detect)
Today tried again(Somehow Brom was ok, but didnt get Authbypass message)
Tried multiple times but now it show error (image attached)
Need further assistance.
Didnt know how bad all these custom rom installing has become. In my days it was cool and fun without getting any errors( i was taking about 2015/2017....)

Kind of same thing happened to me 2 days ago. Trying to root the device and everything was fine until I restarted the phone. After that it just got hard bricked total black screen no realme logo, fastboot or recovery. Had to go into EDL mode and flash the offical rom. In my case there was no error in the mtk bypass tool and everything flashed without any errors. This time the phone booted normally and straight went to realme recovery mode and from there I just wiped the userdata and this time it got stuck in orange state(no realme animation logo). Although this time I could access the fastboot, so tried to install twrp but after flashing, nothing happened same stuck in orange state warning. After this again I tried to flash using mtk tool and after doing that everything remained same but I couldn't access fastboot anymore. The funny story is now I cannot even flash using mtk tool anymore. So, everything is ****ed, I don't think customer service can fix this, would be better to buy a new phone.
My experience with realme phone specially with mtk processor has been extremely bad , I faced errors after errors. Earlier I had redmi note 7 pro and it was excellent in terms of flashing roms and all. So many times I had bricked the device but could fix it no issues.
Anyway as I didn't faced this error I don't know how to fix this. I also used this exact same version also. Try using https://saransaro.com/SP_Flash_Tool_v6.2216_Win.zip . And see if this works.
Also, don't flash the scatter file of firmware after a.22 as it doesn't work for some reason . I used the a.22 one it worked fine.
Please let me know if you were able to fix it or not.