Hey there. I'mve having problems with installing TWRP on my P8000. What I've done:
Removed W7 drivers signature enforcement, reinstalled the drivers, and tried again running SPFlash. The programs opens, I select the scatter file from the the TWRP recovery folder. However, when I press Download, and connect the phone to the cable, nothing happens in the problem. Windows makes a sound of device connected, and lke 5 seconds later it makes the sound of device disconnected. After that the phone goes into that battery charging mode, and a battery appears in the screen.
Any thoughts on this?
Thank you
I would install TWRP via fastboot but to to answer your question: Is your phone turned off when connecting it to the PC and after you pressed download?
Related
Ahh my phone has had quite the past week on this CM12 Android 5.0 ROM...
I was just listening to music and checking social media on my phone when bam, it turns off.
I held the power button and it didn't turn on the first few times.
Then finally, it boots, but it won't get past the splash screen.
It's stuck in a bootloop and I can't get into the recovery. I can't factory reset it either.
I tried to go to fastboot and flash the recovery again, but my computer doesn't recognize my phone.
I have adb, fastboot, and all of the correct drivers installed and it won't do anything.
I tried flashing with "fastboot flash recovery twrp.img" but it just said "<waiting for device>" even though my phone was connected and in fastboot mode.
I don't know what to do. I can't boot it, I can't get into recovery, I can't factory reset it, and I can't fastboot anything.
What should I do? Please I am open to ANY suggestions at this point. I can't deal with this constantly not having a phone crap.
Thanks, it'll be much appreciated.
Extra Info:
Device manager lists my phone as this: "Unknown USB Device (Device Failed Enumeration)"
Every time I go into fastboot, my computer displays this message: "USB device not recognized. The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
SyrStorm said:
Ahh my phone has had quite the past week on this CM12 Android 5.0 ROM...
I was just listening to music and checking social media on my phone when bam, it turns off.
I held the power button and it didn't turn on the first few times.
Then finally, it boots, but it won't get past the splash screen.
It's stuck in a bootloop and I can't get into the recovery. I can't factory reset it either.
I tried to go to fastboot and flash the recovery again, but my computer doesn't recognize my phone.
I have adb, fastboot, and all of the correct drivers installed and it won't do anything.
I tried flashing with "fastboot flash recovery twrp.img" but it just said "<waiting for device>" even though my phone was connected and in fastboot mode.
I don't know what to do. I can't boot it, I can't get into recovery, I can't factory reset it, and I can't fastboot anything.
What should I do? Please I am open to ANY suggestions at this point. I can't deal with this constantly not having a phone crap.
Thanks, it'll be much appreciated.
Extra Info:
Device manager lists my phone as this: "Unknown USB Device (Device Failed Enumeration)"
Every time I go into fastboot, my computer displays this message: "USB device not recognized. The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
Click to expand...
Click to collapse
Make sure you aren't connected via usb to your computer when you attempt to force a reboot. It should be vol up and power until it reboots and then switch to vol down to enter hboot.
dottat said:
Make sure you aren't connected via usb to your computer when you attempt to force a reboot. It should be vol up and power until it reboots and then switch to vol down to enter hboot.
Click to expand...
Click to collapse
I can get into hboot and all that just fine. The phone won't boot, and I can't get into recovery is my problem. Oh and the fact that the computer doesn't recognize my phone in fastboot
Update: I just whipped out a really old computer running Windows XP and I installed the platform-tools and HTC One drivers on it. I hooked the phone up to the computer, and the drivers worked. I flashed TWRP and it flashed successfully according to fastboot, but it won't go into recovery still. What should I do now? I know I can RUU somehow (I'm not really sure how though), but I want to try and avoid that, if possible. Any suggestions? Thanks people!
EDIT: NVM it actually booted! What a success! This stuff is crazy!
Hey there,
I press volume up + insert the USB, when the LG screen appears I let go of the volume button and leave it. After roughly 1 minute it says Download Mode however it only stays in this mode for roughly 20 seconds and then it goes into Fastboot mode saying "reset" and "changed port". I got the correct ROM for my IMEI and LGFlashTool however I think the main problem could be the LG USB drivers. When I try install the official drivers the installer says success however windows says not successful.
Image 1 - i.imgur.com/hPkZbLx.png
Image 2 - i.imgur.com/nxdYm39.png
I have tried uninstalling all LG drivers/software, restarting etc.
I am fairly sure I can flash if I can just figure out how to successfully install the drivers or connect the phone to the PC. Anybody have any ideas? I can use linux or try any suggestions/alternative software.
Kind regards,
Desperate G3 owner
Just an update that I was able to manually apply the LGE PORT/COM driver in device manager however the PC only recognises the device when it is in Fastboot Mode. When it starts in Download Mode as stated above, nothing happens, but after ~20 seconds it will automatically switch to Fastboot Mode and then the PC will detect the phone and says Fastboot Commands.
I have tried using adb.exe devices and fastboot.exe devices in cmd but nothing shows up, any ideas?
Hey guys, so my Xperia Z's screen broke and the touch is unresponsive, so I took out my old Arc S out of the box and decided to boot it up, apparently I had gotten a new phone because this one had a booting problem.
Things I know:
It's been rooted, bootloader is unlocked, current ROM is Legacy Xperia, can't go into CWM recovery, connecting phone to PC and trying to flash new kernel won't work because flashtool doesn't recognize the device.
In device manager the phone comes up as an unknown device, downloaded the drivers from Sony's site, no luck, get error message saying "this file is not compatible with your version of Windows" or something.
I'm on W10 64bit.
So basically I'm kinda stuck, tried Google and other forums and nothing, I can't seem to get anywhere.
Could you guys help me out?
EDIT: Tried installing Android Studio, launching cmd from /appdata/roaming/android/sdk/platform-tools but when I enter the command line it says "waiting for device".
So I'm thinking this has to do with my PC not detecting my phone in fastboot mode or anyother mode.
This seems like a corrupted /system partition. First off, try another cable. Your current one might not be working (happened to me, kept reporting that it "did not recognize the device"). If that does not work, let's start with the basic troubleshooting steps. Does your phone boot info fastboot (turn off your phone, disconnect USB cable, hold menu button, reconnect USB while holding)? If it does, run "fastboot erase system" (I'm assuming you have the fastboot drivers installed and fastboot.exe in the working directory), and try booting into the recovery.
If not, let's try flashmode (turn off phone, disconnect USB, hold back button, reconnect while holding). If that works, just start up Flashtool (Download), wait for it to do its thing (sync), download the latest 4.1.B.0.587 ICS .ftf file from here. Once done, exit Flashtool, and go to the "drivers" folder. Install the flashmode drivers. Go back to Flashtool now.
In Flashtool, click the flash icon in the top-right of the program, and on the top you will find the working directory. Click the button on the right to it and select the directory where you downloaded the .ftf file. A new entry will show up in the menu on the left side. Click on it. Flashtool will prepare the file for flashing and instruct you how to connect your phone in flashmode. Be patient, this process may take a while. Once done (Flashtool will tell you), disconnect the phone, take the battery out for 5 seconds and put it back in, and then boot up the phone. The "SONY" logo should show up, followed by the "XPERIA" logo.
Set your phone up, and have fun flashing!
P.S. If you have any problems with your PC not recognizing your device while in USB Debugging (ADB says no devices), this worked for me.
bsevcenk said:
This seems like a corrupted /system partition. First off, try another cable. Your current one might not be working (happened to me, kept reporting that it "did not recognize the device"). If that does not work, let's start with the basic troubleshooting steps. Does your phone boot info fastboot (turn off your phone, disconnect USB cable, hold menu button, reconnect USB while holding)? If it does, run "fastboot erase system" (I'm assuming you have the fastboot drivers installed and fastboot.exe in the working directory), and try booting into the recovery.
If not, let's try flashmode (turn off phone, disconnect USB, hold back button, reconnect while holding). If that works, just start up Flashtool (Download), wait for it to do its thing (sync), download the latest 4.1.B.0.587 ICS .ftf file from here. Once done, exit Flashtool, and go to the "drivers" folder. Install the flashmode drivers. Go back to Flashtool now.
In Flashtool, click the flash icon in the top-right of the program, and on the top you will find the working directory. Click the button on the right to it and select the directory where you downloaded the .ftf file. A new entry will show up in the menu on the left side. Click on it. Flashtool will prepare the file for flashing and instruct you how to connect your phone in flashmode. Be patient, this process may take a while. Once done (Flashtool will tell you), disconnect the phone, take the battery out for 5 seconds and put it back in, and then boot up the phone. The "SONY" logo should show up, followed by the "XPERIA" logo.
Set your phone up, and have fun flashing!
P.S. If you have any problems with your PC not recognizing your device while in USB Debugging (ADB says no devices), this worked for me.
Click to expand...
Click to collapse
Hey man thank you so much for replying to the thread.
So I feel like a dumbass, multiple times I've read about changing cables, guess what, that's all it took.
So basically I changed the cable and instead of "unrecognized device" I got "S1 fastboot device", after that I installed the adb drivers for the Xperia Arc and voilà, it recognized as an adb device.
Onto platform-tools folder, cmd, flashed the kernel for Cyanogen 10, finally got into recovery and now after a full system wipe I'm flashing CM.
I'll let you know how it turns out.
Thanks a bunch!
Wolfarm141 said:
Hey man thank you so much for replying to the thread.
So I feel like a dumbass, multiple times I've read about changing cables, guess what, that's all it took.
So basically I changed the cable and instead of "unrecognized device" I got "S1 fastboot device", after that I installed the adb drivers for the Xperia Arc and voilà, it recognized as an adb device.
Onto platform-tools folder, cmd, flashed the kernel for Cyanogen 10, finally got into recovery and now after a full system wipe I'm flashing CM.
I'll let you know how it turns out.
Thanks a bunch!
Click to expand...
Click to collapse
Glad to know I helped!
Everything works fine now! Thanks sooo much!
Dear xda-developers-community,
I'm trying to get a phone of a friend of mine working which just reboots whenever the phone is started. The resulting boot loop can only be interrupted by taking the battery out or wait until it is depleeted.
In order to fix this soft-brick I first tried to use recovery by pressing VOL - & POWER. In the menu, I could select and confirm to recover to factory settings, but after some seconds the boot loop appeared again with (seemingly?) no change having been made. The error kept appeaing over and over again.
After trying recovery mode, I attempted to start the phone in download mode by pressing VOL + on the (switched off) phone and connecting a USB cable. The respective menu also opened, here, showing "Firmware Update" and "Do not unplug the USB connection until the process is complete". According to many tutorials I found on the internet, when having installed the required drivers (I used LG United Mobile drivers from here), this procedure should allow you to flash a recovery image through LG's flashing tool (which one can also find on that page).
However, when I connect the LG G3 (D855) to a computer the driver is installed on, there is no new device shown in the Device manager. I tried this out with Windows 10 x64 and Windows 7 x64 and disabled driver validation on both systems and enabled test signing on Windows 10, respectively. Additionally, I followed these instructions, but in this case the screen stays dark and the device is not detected either. It seems like there are not so many people experiencing this error, but I hope we can find a solution.
nVentis said:
Dear xda-developers-community,
I'm trying to get a phone of a friend of mine working which just reboots whenever the phone is started. The resulting boot loop can only be interrupted by taking the battery out or wait until it is depleeted.
Click to expand...
Click to collapse
This may sound like a dumb question, but have you tried a new battery yet? If it is one of the original batteries it could have gone bad & started bootlooping...like mine did a few months ago.
As far as the PC not recognizing the phone you can try downloading USBDeview and uninstall anything that has the vendor ID's of 1004 & 18d1(pretty much anything that says android or LGE in the description) & reboot the PC. Hopefully it'll recognize your device and install the drivers the next time you plug it in. If it doesn't find the drivers automatically for you then install LG drivers manually.
Link for usbdeview: http://www.nirsoft.net/utils/usb_devices_view.html
Link for LGE drivers: http://www.lg.com/us/support/software-firmware-drivers
Good luck :fingers-crossed:
So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?
I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.
I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.
When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.
With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.
I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.
Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.