Neffos X-1 stuck in bootloop - General Questions and Answers

Heya folks,
I have just attempted my first time flashing TWRP on my TP-Link Neffos X-1 following this guide: https://rootmygalaxy.net/twrp-root-...nd_Install_TWRP_Recovery_On_TP-Link_Neffos_X1.
Its looking kinda grim. It starts with the orange state Message and that the device will boot in 5 seconds, however after that it starts with an infinite bootloop. I also cannot access the Recovery (vol up + power), for it simply doesnt work anymore after the guide. When I plug it into my pc, it will automatically start with the bootloop (I can shut the phone off with vol down + power).
Attempting to get into fastboot mode over ADB (adb reboot bootloader), returns with the message error: device '(null)' not found. I think that is due to it not being recognized in the device manager(it doesnt show my phone anymore but unknown device). I tried to install the phone driver for the uknown device, however that keeps failing. I think its due to the phone permanently connecting and reconnecting to the pc.
So I'm wondering of what to do. I guess the biggest issue is that the drivers are not recognized, but as long as the phone keeps on restarting every couple of seconds i doubt i can properly install the driver. You guys got any ideas?

My guess is you haven't installed on Windows PC the appropriate Android USB Driver matching the device

I mean the appropriate USB driver had to be there for me to flash it with the TWRP in the first place, right?

Think I clearly said that the additionally required USB-driver has to be installed on Windows PC.

I have this one installed https://rootmydevice.com/download-neffos-usb-drivers/, is this the additionally required usb driver?

So far, despite what driver I pick for the device, it shows the code 10, device couldnt be started - probably because it never gets past the starting screen but keeps rebooting

slayingduck said:
Heya folks,
I have just attempted my first time flashing TWRP on my TP-Link Neffos X-1 following this guide: https://rootmygalaxy.net/twrp-root-...nd_Install_TWRP_Recovery_On_TP-Link_Neffos_X1.
Its looking kinda grim. It starts with the orange state Message and that the device will boot in 5 seconds, however after that it starts with an infinite bootloop. I also cannot access the Recovery (vol up + power), for it simply doesnt work anymore after the guide. When I plug it into my pc, it will automatically start with the bootloop (I can shut the phone off with vol down + power).
Attempting to get into fastboot mode over ADB (adb reboot bootloader), returns with the message error: device '(null)' not found. I think that is due to it not being recognized in the device manager(it doesnt show my phone anymore but unknown device). I tried to install the phone driver for the uknown device, however that keeps failing. I think its due to the phone permanently connecting and reconnecting to the pc.
So I'm wondering of what to do. I guess the biggest issue is that the drivers are not recognized, but as long as the phone keeps on restarting every couple of seconds i doubt i can properly install the driver. You guys got any ideas?
Click to expand...
Click to collapse
Try this TWRP file: TWRP_3.2.3_NeffosX1_TP902A_by_kiruha_21.img

The thing is, I cannot flash anything due to my phone constantly rebooting while inserted in the pc usb-slot. Neither ADB nor my device manager recognize the device and as mentioned before, I cannot install any drivers

slayingduck said:
The thing is, I cannot flash anything due to my phone constantly rebooting while inserted in the pc usb-slot. Neither ADB nor my device manager recognize the device and as mentioned before, I cannot install any drivers
Click to expand...
Click to collapse
Some MTK devices has this: Press both VOL+ & Power buttons. Only remove 2 buttons when you see Bootloader mode (recovery; fastboot; reboot system) or directly in the Recovery mode. Now you can use fastboot.
With the SPFT you can use same tip above. In the SPFT choose DOWNLOAD and plug USB device. Process to flash stock ROM or stock recovery.img & boot.img start.
If not start pugging USB: choose DOWNLOAD - press VOL- and plug USV device. You can try with buttons like only VOL- or VOL+ or combo buttons VOL+&VOL- or VOL-&VOL+ or other button combination.
You can try FIRMWARE UPGRADE too.
That's depend about LOCKED or Unlocked bootloader process that you made before actions!
If you unlocked bootloader so only need patience. If not so that's no good.

Related

[Q] Nexus S not appearing in device manager in fastboot

I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
stoo said:
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
Click to expand...
Click to collapse
in the main setting, application, developer settings.. is usb debugging enabled?
stoo said:
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
Click to expand...
Click to collapse
When I first set up ADB and Fastboot on my pc, I was getting a response when writing 'adb devices' in the console. However, 'fastboot devices' returned absolutely nothing.
Solution (with phone connected to pc and usb debugging cheched):
1-shut down the phone
2-press and hold Volume Up key + Power
3-once in bootloader interface, in the pc command prompt, type 'fastboot devices'.
Voila!
By the way, don't mount the phone as usb storage device.
Thanks for the responses guys but yes, USB debugging is enabled and yes, I've used that way to get to fastboot mode as well as adb reboot bootloader
Hi stoo
I have a same issue - did you managed to find solution for yours?
Cheers,
Wiktor
vstar said:
Hi stoo
I have a same issue - did you managed to find solution for yours?
Cheers,
Wiktor
Click to expand...
Click to collapse
easy way to set up fastboot
Any solution
Have the same problem: locked bootloader, not rooted 4.1.2. In ADB everything is ok, drivers ok (in device manager), can get it through "adb devices". But when I boot in fastboot (adb reboot bootloader), I hear the ti-da windows sound (usb unpluged - from adb session), but no ta-di when the phone re-boot in fastboot. No exclamation mark in device manager, nothing. The USB receive nothing when in fastboot. Is it possible that the fastboot image is corrupted? Can I reflash it? Or any other advice?
Thanks
EDIT - SOLVED - at least this step
The problem was the famous "broken power button"! I knew that I had problems with the power button (didn't work - that's why I try to flash a rom (4.2.1 or customized) with sleep tile in notification area).
I thought that the button is all the time OFF and don't switch to ON, but I finally understood that when when I boot in fastmode it freeze before installing device on the PC (I also had no volume up / down navigation in fastboot, a sign that it was frozen). So I ended to consider that the power button was permanently in ON position. I opened my phone and I measure the impedance on the power button. I had ~ 4ohms in off position of the button and 1.8 ohms (cheap multimetter.... probably should be almost 0) in on position. I measured also on volume switch where I had ~ infinite on off position, so I concluded that the button if blocked. I tried to see if I can resurrect it but no choice, so I took it off (unsoldered). I put the battery and the USB cable and boot it. From ADB I reboot it in fastboot and voila! The device popped in device manager! One problem solved! BUT...
I tried to use the Nexus Root Toolkit and it boots in fastmode and try to unlock the bootloader, but it asked me on phone screen if I agree for unlocking. I was able to use the volume to select Yes but I couldn't choose it with power! I had no option but to take the battery off. Starting from that point it was almost impossible to power it again. When I plugged the USB it shown the battery icon (charging). I tried every trick that I found on web, but nothing worked (even to fast plug / unplug many times the USB to overcharge it, but nothing). I was able only by pressing on the middle of volume (so Up and DOWN in the same time) and plus the USB to get to the screen of unlocking bootloader, but without the options YES/NO on the screen. Seems that it saves this state between boots, but why no option? Finally I was unable to boot at all, and it is like totally bricked
I thought that the power button is a simple switch ON / OFF, so I soldered 2 wires and I tried to touch them (short circuit) to simulate the ON, but nothing happened. Is it the button more complex that a simple switch? no ideea...
So now have a better phone than before (at least theoretically it should be able to fastboot), but it values zero because I can't power it on....
OK So I am in the exact same situation.
Nexus S, Broken power button, adb can see the device, fastboot cannot. fastboot cannot be navigated with the volume keys.
I also want to put an other rom onto it, but firstly I want to put TWRP recovery on it, as it supports touch, CW needs the power
button which like mentioned does not work.
I would rather not unsolder my power button to get into fastboot, any suggestions on how that might still be achieved?
thx
catalinu said:
Have the same problem: locked bootloader, not rooted 4.1.2. In ADB everything is ok, drivers ok (in device manager), can get it through "adb devices". But when I boot in fastboot (adb reboot bootloader), I hear the ti-da windows sound (usb unpluged - from adb session), but no ta-di when the phone re-boot in fastboot. No exclamation mark in device manager, nothing. The USB receive nothing when in fastboot. Is it possible that the fastboot image is corrupted? Can I reflash it? Or any other advice?
Thanks
EDIT - SOLVED - at least this step
The problem was the famous "broken power button"! I knew that I had problems with the power button (didn't work - that's why I try to flash a rom (4.2.1 or customized) with sleep tile in notification area).
I thought that the button is all the time OFF and don't switch to ON, but I finally understood that when when I boot in fastmode it freeze before installing device on the PC (I also had no volume up / down navigation in fastboot, a sign that it was frozen). So I ended to consider that the power button was permanently in ON position. I opened my phone and I measure the impedance on the power button. I had ~ 4ohms in off position of the button and 1.8 ohms (cheap multimetter.... probably should be almost 0) in on position. I measured also on volume switch where I had ~ infinite on off position, so I concluded that the button if blocked. I tried to see if I can resurrect it but no choice, so I took it off (unsoldered). I put the battery and the USB cable and boot it. From ADB I reboot it in fastboot and voila! The device popped in device manager! One problem solved! BUT...
I tried to use the Nexus Root Toolkit and it boots in fastmode and try to unlock the bootloader, but it asked me on phone screen if I agree for unlocking. I was able to use the volume to select Yes but I couldn't choose it with power! I had no option but to take the battery off. Starting from that point it was almost impossible to power it again. When I plugged the USB it shown the battery icon (charging). I tried every trick that I found on web, but nothing worked (even to fast plug / unplug many times the USB to overcharge it, but nothing). I was able only by pressing on the middle of volume (so Up and DOWN in the same time) and plus the USB to get to the screen of unlocking bootloader, but without the options YES/NO on the screen. Seems that it saves this state between boots, but why no option? Finally I was unable to boot at all, and it is like totally bricked
I thought that the power button is a simple switch ON / OFF, so I soldered 2 wires and I tried to touch them (short circuit) to simulate the ON, but nothing happened. Is it the button more complex that a simple switch? no ideea...
So now have a better phone than before (at least theoretically it should be able to fastboot), but it values zero because I can't power it on....
Click to expand...
Click to collapse
Yes, it should have been better for me to have also a possibility to enter in fastboot with the power button blocked in ON position, but I didn't find. And now I know no way how to power it up...
fastboot drivers
http://www.samsung.com/us/support/owners/product/GT-I9020PWAATT#
has anybody considered using this executable from samsung ..
from what i understood when installing it ,it only unzips the contents at programfiles/Samsung/drivers
then you can check this thread to install them spesifically http://forum.xda-developers.com/showthread.php?t=1901617
..In short.
Go to
"Device Manager"
find
"Android 1.0" or something like that (i had my device in fastboot/bootloader mode, dont know if it was necessary)
install drivers from the drivers directory and install
P.S. Mine is an ordinary 9023nexus s (slcd) though
be a bit more careful with nexus s4g

bricked huawei g730

hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help
SP log files attached
thanks
elkhopoa said:
hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help
Click to expand...
Click to collapse
I'm not sure but i did find links for G730 official ROM.
There are 6 ROMs for this model, G730-U30, G730-C00, G730-T00, G730-U00 & more..
ROMs LINK
Then another link: Huawei G730-U00,Android 4.2,Emotion UI,V100R001CHNC17B137 Official Firmware
Seem's like there is stuff out there on internet, no offence. Just sharing information. Well, back to the bricked situation.... As i remember, there are methods to restore/fix semi/soft-bricked phone. Hope you find the solution. Search forum/internet.
I'm not an expert. Thats all i can share.
I have same problem.How to solve it.
same problem, what to do???
elkhopoa said:
hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help
Click to expand...
Click to collapse
Universal unbrick guide:
Terminology - types of bricks:
Soft brick - often occurs in the shape of a bootloop or any other problems with booting such as always getting to recovery or not getting past the carrier logo. This type of a brick, which shows some signs of life, can in most cases be fixed.
Hard brick - As the name implies, your phone can essentially used as a brick and it shows no signs of life. This kind of a brick is rare and in theory should be unfixable. However there are advanced methods of fixing your phones such as JTAG, but they require extra tools and accessories.
The decision:
Is my phone soft or hard bricked?
If you answer yes to all of the questions below you probably have a hard birck:
Test as said in order!
Nothing happenes when you hold or press the power button
You cannot get the screen to even turn on by pressing or holding any combination of buttons on your phone
Nothing happenes if you do the same as about but with your phone plugged into a charger
Nothing happenes when you plug your phone into a computer
When you plug in your phone into a computer it does not recognize it as a phone, storage or any other media device
Nothing happenes when you try all of the above again, but with removing the battery in between steps for 10 seconds and putting it back in again
Nothing happenes when you try all of the above again, but after leaving the phone plugged into a charger for 2 hours
If all of the questions are a "yes", then you either have a broken charging port and and a discharged battery or you have a hard brick.
The unbricking:
There are many methods of unbricking and they are all different to each phone. Here I will list the most common methods that often succeed.
Samsung users skip to 4. method.
1. If you have access to a stock recovery:
Method 1:
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Choose “Wipe Cache Partition”.
5. Choose “Wipe Data / Factory Reset” to delete all your settings and apps, using the correct ROM.
6. Reboot your device.
Method 2:
Download the stock rom for your phone. It should be in ".zip" format. Make sure it's the official version
(Find it by Googling something like "[your phone model] stock rom")
Put the file on your phone's external SD card.
Make sure that the rom is for your exact phone model.
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Select "apply update from external storage"
5. Navigate to the zip file you copied to your phone
6. Install it.
If you get Status Error 7 that means you didn't download an official stock rom.
2. If you have access to a custom recovery:
Method 1:
Try stock recovery method 1
Method 2:
1. Find a stable custom rom for your phone or if you want to download the stock rom
Make sure that the rom is for your exact phone model.
2.. Copy the zip file to the phone's external SD.
3. Install the zip
(If you have a custom recovery you probably know the drill)
3. If you have access to fastboot mode:
First install ADB and fastboot drivers (if you haven't already):
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Once you have the drivers installed you have to find a recovery image for your phone to install a custom recovery.
You can try one of the popular recoveries such as CWM or TWRP.
You need to get the recoveryNameHere.img file for your phone.
Find it by Googling:
"[your phone model] TWRP recovery"
or
"[your phone model] CWM recovery"
Make sure that the recovery is for your exact phone model.
Now on your phone enter fastboot mode:
Turn your phone off.
You can try different button combinations. For my phone it's holding power and volume down buttons.
Once you're in fastboot mode plug your phone into a computer and open your terminal/cmd.
Type in:
Code:
fastboot devices
You should see a list of devices. There should be only one device ID number.
If you see the ID it's working. If you don't you didn't install the Google USB driver properly (on Windows) and if it says "'fastboot' is not a recognized command" or "No command 'fastboot' found" then you didn't even install your drivers.
If you have problems with installing Google "how to install adb and fastboot drivers"
Now that you know fastboot is working type in:
Code:
fastboot flash recovery C:\Path\To\Recovery.img
Replace "C:\Path\To\Recovery.img" with an actuall path of the recovery file you downloaded.
It should say success.
If it doesn't try to execute:
Code:
fastboot oem unlock
This will delete all data you had on your phone (games, game progress, apps...).
Now try
Code:
fastboot flash recovery C:\Path\To\Recovery.img
again.
Once you're done type in:
Code:
fastboot reboot
And your phone should still not work. Now what you have to do it try the custom recovery method above (number 2.)
4. If you have a Samsung device:
Try this tutorial of unbricking with Odin: click here

HELP! ROM Manager bricked my O3D - Is it fixable?

NOTE: Before we start, I have now googled it and in hindsight I probably should of left RM alone!
Anyway as the title states my O3D seems totally goosed! I selected the recovery flash in ROM Manager for P920, it rebooted and all it does now is show the logo for a second, vibrate then off. I tried the usual tutorial stuff...
Power button, Vol up battery in - it comes up 'USB Device Unrecognised' and then It also keeps popping up 'Unknown Device' however when I click on properties every entry is 'Unavailable'
Power button, Vol Down, battery in does nothing (tried it a million times)
If I do...
Power button, Vol up then apply the battery - Device Manager finds... 'LG Mobile USB Modem', 'MAP SMS' (Other Devices) and 'LGE Mobile Composite USB Device'
No sign of OMAP44xx so the flash tools don't see it... strangely LG Mobile Support Tool sees the phone and tries to update it however it says it has the latest firmware, when I use the update recover option it gets to 15% but then complains that it can't communicate with the phone.
Is it dead? :crying:
Any help would be much appreciated.
dont worry. its not dead. has happened to my phone a trillion times ..
all you need to is try as below:
1. without connecting phone to usb first hold down 3d button then volume down and keep pressing power untill it starts up and then off again , then release all 3 together as it is off and repeat (remember first 3d then volume down and then power). this time just let the power button go on lg logo but keep pressing the other 2.
2. if this doesnt work, then easiest method - download omap4boot for optimus v1.21 or all in one p920 v1.3 by XDA, remove battery, only press down the volume up button and while pressing connect usb. make sure you hear 1 ding of connect , 1 dong of disconnect then 2 dings of connect. after this the ding dong should end .. if you have all drivers installed , then it will install omap drivers. a window will pop up and everything will have a green check. once it does that you can install a custom recovery twrp or cwm using fastboot . boot into recovery and flash a rom.
still if doesnt work, have patience, post a reply and will tell other steps to proceed with .....
Thanks for your time RVBSD, unfortunately (although I will keep trying!)
In No. 1 - I get the first logo, but when I re-apply the 3D/V and power, I don't get the second logo.
In No.2 - I get the first ding/dong then just 1 ding, no sign of Mr OMAP! - I'll keep trying though.
Once u get the second ding and then this music stops, Open device manager. Look for lg usb modem and disable it. Then look for omap44 something. The device manager may be refreshing quickly. Somehow i had a chance to right click on omap device and chose update driver. Select manual and choose omap.inf from the folder that u have to download as per my previous reply. Restart computer and check again.
Alternatively you can install all inf manually, right click and install, before connecting the device.
Let me know
Sent from my LG-P920 using xda app-developers app
Again, thanks again for your input but I am still no further. I manually clicked the inf and it said it installed fine... but nothing changed in Device Manager. I then attempted to 'force' the driver on the unknown device, however after it installed it returned a 'Code 10' error... unable to start.
Even tried the service software 'LGNPST' but it couldn't even connect to the port! ho-hum...
i tried it again. even on my computer it didnt take the omap drivers this time.... strange .....
but i could install fastboot, then installed cwm recovery . then flashed a rooted rom and its working ...
1. Turn off your Phone, pull out battery.
2. download omap4boot-for_optimus-v1.21 (run "start_fastboot.bat" (it will wait until phone connected)
3. connect phone with USB cable without battery, the usbboot will start
4. insert battery while the usbboot is waiting, it gives 5 secs only
5. unplug USB cable the LG logo will appear with fastboot on top
6. download the attached files to your desktop and extract
7. open cmd and in cmd navigate to fastboot.exe location, where ever downloaded
8. run fastboot.exe from cmd and choose the cwm file to be pushed to your phone
command : fastboot -s flash recovery recovery-clockwork-6.0.1.9-p920.img
9. reboot device into recovery , try to wipe cache and factory reset and try to reboot
if this works it will take you to existing installed rom, then you can reboot to recovery and flash Su_Bbox_1.20.2_gazhead_signed.zip to root it
10. else copy a custom rom to sd card , insert in the mobile , reboot into recovery and flash the cutom rom
PLease help
CAn you tell me how can mount recovery partition

Need help flashing Wiko Lenny 3

Hey, so I had recently tried learning about flashing and custom roms on android, and I had flashed twrp with magisk on my lenny 3. Because my device seems to be unpopular, roms like lineageOS aren't available for it, only some sketchy roms are.
So I was trying to flash a rom with spflash tool, ticked all files except recovery.img cause I didn't wanna remove TWRP in case something went wrong, but I was prompted with some message saying the flash would only work with "Format All + Download" instead of "Download Only", so I selected the format+download, but it seems that by doing so it ticked recovery.img back, formatted all files from my phone and flashed something that doesn't boot at all. What I don't understand is why after doing this I can't reflash the phone. Whenever I tried to use spflash tool again it just didnt detect my phone again. No data signal whatsoever. It also doesn't make the connection alert sound whenever i connect it to windows like it previously did. Perhaps cause of the formatting... It's not a cable problem cause I've tried many different ones.
TLDR My dead lenny 3 doesn't give any data signal when i connect it via usb after a bad flash, so I can't reflash it to fix it
What I've tried:
- Reinstalling VCOM, CDC and ABD drivers on 2 windows computers, spflashtool still couldn't detect my phone and do the flashing;
- Using a stock firmware installer like the one from the blog below, on both computers, after reinstalling the drivers, still couldn't detect my phone.
- Tried charging it on my pc overnight to see if I could somehow boot into recovery, tried long pressing Power + Vol Up, Power + Vol Down, Power + Vol Up + Vol Down. Nothing boots it. I also tried holding Vol Up as I connect it via USB to see if it could connect but nope. No data signal.
- I have adb and fastboot installed, i tried both abd devices and fastboot devices commands, on both pcs, to see if my device was listed at all, and it wasn't.
Any suggestions on how to be able to flash it again? If I could boot it into TWRP i'd be all set cause i have a backup... the problem is that my TWRP is gone and even if I still had it I can't boot my phone (Even tho I left it charging)
Any help would be appreciated, and if this isn't the right forum to ask for unbricking help, where should I?

(Solved) Oneplus 8T Qualcomm logo blinking

Hi!
I have tried to install a custom rom, but there was an error. When I tried to boot back to bootloader mode, the qualcomm logo started blinking and the device is vibrating.
Tried to connect to pc, but I don't see any device in COM Ports in the device manager, also MSM tools says waiting for the device.
If I connect the cable while I am pressing the both volume button, I hear the sound from the pc that something is connected, but after a few seconds the device disconnects.
Can you help me?
Got the same problem installing a wrong firmware, probably. I'm hoping for someone knowing how to solve...
That was easy. Unfortunately I had to format the phone entirely (MSMTool), but it's back with the living.
Install Qualcomm EDL drivers
Download an MSMTool release for OnePlus 8T
Enter in EDL Mode. With the phone connected to a computer running Windows, press volUp + volDown right when you see the Snapdragon logo. The phone will stay with screen off
Follow the usual flashing procedure with MSMTool
Thanks, I just had to install the Qualcomm drivers exe file. After that it appeared in device manager.
Livingsilver94 said:
3. Enter in EDL Mode. With the phone connected to a computer running Windows, press volUp + volDown right when you see the Snapdragon logo. The phone will stay with screen off
Click to expand...
Click to collapse
Nothing happens when i press that. phone keeps on vibrating and flashing the logo
UPDATE: Got a different computer and it worked

Categories

Resources