Database Users

[Help] I bricked my Axon. Need help.

So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Edit: I solved my issue by downloader the stock B08 system on my S5 and then i placed it in the external sd. Then i put the SD back into the Axon and installed the system. After i had installed the system and booted into the OS i could enter adb with my device being recognized and after that i flashed twrp by using ADB.
I have a new problem though and that is that i can't install the 3.1.0.0. twrp. it only boots into black screen when i enter recovery. I can use the 3.0.4.0. version though.

You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?

senny22 said:
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Click to expand...
Click to collapse
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?

nonamesl said:
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
Click to expand...
Click to collapse
Correct. It simply reboots.
Yup, i tried installing the B29 stock system on my G model and so i suppose i had the wrong bootstack becasue this is where my problems started.
I get to the stock android recovery.

raystef66 said:
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
Click to expand...
Click to collapse
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.

senny22 said:
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
Click to expand...
Click to collapse
You should see your phone as QUSB_BULK. Installed the ZADIG drivers ? That may cure the problem.
After that, imo, it is important you can reboot edl and flash TWRP recovery again AND when it recounts, you pull usb.
Normally you will have replaced recovery , reboot ok and you can enter TWRP and fastboot also.
ps : sometimes it is also advisable to go to ADB RECOVERY directly and do the processes.
ps2 : when TWRP backup, you can always put it on SD via other phone and in TWRP restore. Normaly you're good to go then...

Try the Marshall London Bootloader Interface driver maybe?

nonamesl said:
Try the Marshall London Bootloader Interface driver maybe?
Click to expand...
Click to collapse
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?

senny22 said:
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
Click to expand...
Click to collapse
Installing the driver and using it for the phone (device manager -> change driver manually (or something of the sort)) worked for me, but it could differ. Let me know. You don't have to uninstall other drivers just use that specific one for your phone by switching the driver manually via device manager.

system deleted, TWRP ready

Hello,
i delete the System and Data on my LeEco Le Pro3.
TWRP is installed.
Can i flash a rom with an usb flash drive in TWRP or fastboot?
greeting gizez

Boot into TWRP and use MTP to transfer ROM file from your PC to Phone. Then flash the ROM.

I have this problem, but I can't see the phone when connected to a PC. adb sideload doesn't work (adb devices doesn't find anything). Do I need to install driver for the phone? I originally used fastboot to unlock the bootloader and flashed TWRP, then installed LineageOS and gapps just fine. I then proceeded to wipe system in TWRP (I was trying to get back to new phone setup so I can transfer stuff from old phone, which I skipped the first time).
Any idea how to get around this? I tried plugging in pen drive through an micro USB OTG and a usb-c to micro usb adapter, but it's not recognized in TWRP, either. Would very much appreciate any help!

You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
marik1 said:
[...]
Go Advanced -> ADB Sideload, type "adb sideload aicp_zl1_n-12.1-NIGHTLY-20170516.zip" (zip of OS should be downloaded and put into "Minimal ADB and Fastboot" installation folder with name as same as the text of command). It should let you turn on system.
[...]
Click to expand...
Click to collapse
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0

marik1 said:
You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0
Click to expand...
Click to collapse
Thanks, but unfortunately no luck. Both adb sideload and adb push said error - device '(null)' not found. It seems like the PC is not recognizing the phone. I checked device manager on the PC, it showed LEX727. I right-click and had it install the driver. It says driver successfully installed. Then device manager showed MTP device with a !. I again tried having driver installed, but this time it doesn't find any driver.
I'm at my wit's end... Any more suggestion?

TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.

marik1 said:
TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.
Click to expand...
Click to collapse
Actually, the problem is solved, by using another PC. This one showed LEX727 in windows explorer as soon as i plug in the phonr (in twrp). I was able to drag and drop the zip files to the phone and go on my merry way. Now back in business!

[OP5, encrypted] Open Beta 3 broke my display!

Tried to flash OB3 and SuperSu on my encrypted OP5 with TWRP. Was stuck at OP logo.
Tried to go back to stable Oreo build for OP5. Again, was stuck at OP logo.
Now the screen is unresponsive in TWRP (can't even swipe to allow modifications on the first screen!).
If I install stock recovery, I can navigate recovery with buttons. I tried installing OOS 5 with stock recovery from internal storage. It doesn't work. I tried to adb sideload. The computer throws a bad_alloc error.
Anyone in the same boat, or good enough to advice?

pentruexperiment said:
Tried to flash OB3 and SuperSu on my encrypted OP5 with TWRP. Was stuck at OP logo.
Tried to go back to stable Oreo build for OP5. Again, was stuck at OP logo.
Now the screen is unresponsive in TWRP (can't even swipe to allow modifications on the first screen!).
If I install stock recovery, I can navigate recovery with buttons. I tried installing OOS 5 with stock recovery from internal storage. It doesn't work. I tried to adb sideload. The computer throws a bad_alloc error.
Anyone in the same boat, or good enough to advice?
Click to expand...
Click to collapse
but u'll lost your data
i had this too, you need to flash stock recovery from cmd in yor pc by:
"fastboot flash recovery recovery_name.img"
then wipe everything,
reboot again into recovery
click on adb
and then download the stable firmware oreo 5
in adb mode with stock recovery put firmware in the same folder
and input - adb sideload name_of_firmware.zip
That fixed my phone, i'll hope and yours will be fixed

sk.c0de said:
but u'll lost your data
i had this too, you need to flash stock recovery from cmd in yor pc by:
"fastboot flash recovery recovery_name.img"
then wipe everything,
reboot again into recovery
click on adb
and then download the stable firmware oreo 5
in adb mode with stock recovery put firmware in the same folder
and input - adb sideload name_of_firmware.zip
That fixed my phone, i'll hope and yours will be fixed
Click to expand...
Click to collapse
Thanks,
The device is recognized well by the computer (when I write 'adb devices'). But when I try to sideload ('adb sideload OOS5.zip'), it gives me an error with bad_alloc. any ideas?

pentruexperiment said:
Thanks,
The device is recognized well by the computer (when I write 'adb devices'). But when I try to sideload ('adb sideload OOS5.zip'), it gives me an error with bad_alloc. any ideas?
Click to expand...
Click to collapse
Try unbrick method I think it's the quickest way to get back your device.

OS gone, won't boot. TWRP recovery but can't copy ROM!

So I seem to have wiped/formatted completely through TWRP and it wiped out the original stock rom, so I have absolutely no OS...
I can still get to bootloader and TWRP Recovery, but USB OTG won't mount no matter how many times I try to connect it (which I need to install the downloaded ROM)
I was hoping I could copy the rom via ADB command but it won't recognize the device with 'adb devices'. It does however recognize when I do "fastboot devices"
What should I do? I think since it wiped out the OS, my device no longer is able to run in USB Debugging mode... how could I load the ROM onto my device?

IF you download the WUG toolkit, you can flash the ROM .img files in Fastboot mode (Boot/System/Recovery/Cache etc).

Nokia 6.1 plus Stuck on TWRP Splash screen. PLEASE HELP!!

Hello everyone,
I have recently unlocked the bootloader on my Nokia 6.1 plus, and rooted it. I then went ahead and installed TWRP ( App install method - found in the twrp website ). However after I rebooted my phone has been stuck on the TWRP splash screen , I Tried going to download mode , and that just got me back to the twrp splash screen. I turned off the phone and powered it on again , same result . Whatever I do it just keeps going back to the TWRP splash screen .. What is even worse is that my device can not be recognized by my pc while stuck on the splash screen , thus I can not use ADB or Fastboot ...
I am feeling really hopeless and stuck , Help would be much appreciated!! Thanks

Now, dissemble the device and enter edl mode
Sent from my Nokia 6.1 using Tapatalk

MaxTurner771 said:
Hello everyone,
I have recently unlocked the bootloader on my Nokia 6.1 plus, and rooted it. I then went ahead and installed TWRP ( App install method - found in the twrp website ). However after I rebooted my phone has been stuck on the TWRP splash screen , I Tried going to download mode , and that just got me back to the twrp splash screen. I turned off the phone and powered it on again , same result . Whatever I do it just keeps going back to the TWRP splash screen .. What is even worse is that my device can not be recognized by my pc while stuck on the splash screen , thus I can not use ADB or Fastboot ...
I am feeling really hopeless and stuck , Help would be much appreciated!! Thanks
Click to expand...
Click to collapse
You shouldn't have installed TWRP on a A/B device let alone install it via the app. It's okay, We're here to help.
If you have OSTLA in your PC, Just open it up and load all files and select to flash the stock ROM. Select Normal Download/Erase User Data options and if the option to Chech AP status is enabled, Disable it. Select on start or the option to flash stock ROM.
Power off your phone completely. If you can't, Then press the volume+ button and power button. Once the screen goes off, Immediately connect phone to PC.
Phone should now reboot into download mode and stock rom should start flashing. Then it's just a matter of waiting for it to flash and reboot.

CarbonGTR said:
You shouldn't have installed TWRP on a A/B device let alone install it via the app. It's okay, We're here to help.
If you have OSTLA in your PC, Just open it up and load all files and select to flash the stock ROM. Select Normal Download/Erase User Data options and if the option to Chech AP status is enabled, Disable it. Select on start or the option to flash stock ROM.
Power off your phone completely. If you can't, Then press the volume+ button and power button. Once the screen goes off, Immediately connect phone to PC.
Phone should now reboot into download mode and stock rom should start flashing. Then it's just a matter of waiting for it to flash and reboot.
Click to expand...
Click to collapse
I had a problem in that my device would never be recognized by my pc even when i finally manage to put in download mode, However after many days trying I was finally able to do it , and to use OSTL.... so thank you!!
I am wondering now how I will do the thing i wanted from the start which is to flash a kernel if i shouldn't use twrp?

MaxTurner771 said:
I had a problem in that my device would never be recognized by my pc even when i finally manage to put in download mode, However after many days trying I was finally able to do it , and to use OSTL.... so thank you!!
I am wondering now how I will do the thing i wanted from the start which is to flash a kernel if i shouldn't use twrp?
Click to expand...
Click to collapse
So to my understanding what you want to achieve is flash a custom kernel on stock rom. And after you messed up your stock recovery by installing twrp, if you have flashed stock rom using ostla then follow these steps.
First without tampering anything finish an ongoing/pending ota/sp update cause after you install custom kernel you phone won't be able to install OTAs. The last sp is of june so install that.
Now coming to installing the kernel-
*Place your twrp and kernel zip file into your adb folder*
1. Setup usb debugging and connect your device normally to your pc, check if the device is communicating with pc type in "adb devices" and allow on your phone for authorisation.
It should reply with your serial on cmd window.
2. Type in "adb reboot bootloader" that should put your device in download mode.
3. Type in "fastboot boot twrp.img" (replace twrp.img with whatever your twrp image file name is)
4. Go to advanced and select adb sideload, swipe to start.
5. Now move to your cmd window and type in "adb sideload kernel.zip" (replace kernel.zip with whatever your kernel zip file name is)
Wait for the process to finish
Now press home go to wipe>advanced wipe select dalvik cache and swipe to wipe
again press home and select reboot, select system
Now final important step
6. don't swipe, select "do not install twrp"

D-Mi said:
So to my understanding what you want to achieve is flash a custom kernel on stock rom. And after you messed up your stock recovery by installing twrp, if you have flashed stock rom using ostla then follow these steps.
First without tampering anything finish an ongoing/pending ota/sp update cause after you install custom kernel you phone won't be able to install OTAs. The last sp is of june so install that.
Now coming to installing the kernel-
*Place your twrp and kernel zip file into your adb folder*
1. Setup usb debugging and connect your device normally to your pc, check if the device is communicating with pc type in "adb devices" and allow on your phone for authorisation.
It should reply with your serial on cmd window.
2. Type in "adb reboot bootloader" that should put your device in download mode.
3. Type in "fastboot boot twrp.img" (replace twrp.img with whatever your twrp image file name is)
4. Go to advanced and select adb sideload, swipe to start.
5. Now move to your cmd window and type in "adb sideload kernel.zip" (replace kernel.zip with whatever your kernel zip file name is)
Wait for the process to finish
Now press home go to wipe>advanced wipe select dalvik cache and swipe to wipe
again press home and select reboot, select system
Now final important step
6. don't swipe, select "do not install twrp"
Click to expand...
Click to collapse
This might sound like a stupid question but I am a major newbie when it comes to this,
Right now i managed to compile a custom kernel and I have a boot image along with the kernel, so to get the kernel.zip do I just zip up all these files? also I read that I could simply flash the image by rebooting to my bootloader and then using " fastboot flash boot boot.img " would this work , and if so does this mean i don't need twrp...
Thanks again for the help , it is much appreciated

MaxTurner771 said:
This might sound like a stupid question but I am a major newbie when it comes to this,
Right now i managed to compile a custom kernel and I have a boot image along with the kernel, so to get the kernel.zip do I just zip up all these files? also I read that I could simply flash the image by rebooting to my bootloader and then using " fastboot flash boot boot.img " would this work , and if so does this mean i don't need twrp...
Thanks again for the help , it is much appreciated
Click to expand...
Click to collapse
If you just want to flash your custom kernel there's no need to flash a boot.img if you've a running rom installed. You can flash the kernel.zip it via twrp or adb sideload via twrp.
Sorry for the late reply, if you have a bootloader-unlocked 6.1 Plus you should join Nokia 6.1 Plus community on telegram you'll get much faster response from the community regarding your device ?