Hello guys! I am following you since yesterday morning when I wake up because my HTC Desire 320 was in a continous vibration restarting again and again every 10 seconds. Only the Android logo appears for a few secs and new restart and so on. I looked around a liitle, downloaded all the tools including Sp flash tools, preloader drivers for Windows 7, MT6582 scatter and so on. The phone was never rooted, is unlocked. I tried with Sp flash tools unsuccesful, the write process fails I guess because connecting and disconnectiong from usb even with the battery removed. Can't access recovery mode with volume down and power button and battery inside, same event appears. What is the next step? Thank you
Related
A friend of my bring me this morning her HTC Wildfire and tell that is broken. When i power phone on it stuck on fastboot screen and it can`t recognize when i press volume up or down button. I have managed to power on phone with android sdk tool. After that i have back up data and try to enter hboot. Again same problem volume up and down are not responding and when i try just to power on phone it stuck on fastboot screen. I have downloaded shipped rom and try with instaling that one first time it boot up but next time when i power on phone it again stuck in fastboot screen. I have try also to boot directly from sd card not from pc, same problem. Everything works fine with android sdk i have managed to enter recovery in hboot using android sdk but when i power on phone it just stay stacked at fastboot screen. Any suggestion what is next step to try, do you think that rooting will help?
update
update : I have also done rooting and flash CM7 everything works normal but when I power off phone and want to power on it again it stuck on fastboot screen and volume up and down are not responding. I can power on it with android sdk, but this mean that i will need android sdk every time when my phone goes off
possible hardware fault? are you sure the vol button isnt broken?
yes i am sure, buttons works normaly when i power on or access bootloader recovery using android sdk
Hello ! I had a problem on my FE375CG. It was rooted, and after an ASUS update, my device stuck with only a USB logo on the screen ! No Boot Droid nothing. There was a lot of error and I was unable to flash my device with Fastboot...
But I prepared a kit with a lot a tools to unbrick the devices ! I don't really know who are the authors of this tools, but here is the pack !
First Download the package : "Unbrick_Fonepad_7.zip" : https://mega.nz/#F!qM0EECyA
Second, unzip the package. Install the ADB drivers and the Intel DnX USB Drivers.
Then, Maintain + and - and power on your device for 4 secondes. The screen should remain off.
Connect the tablet to your computer : It should be recognize, screen remaining off.
Then you have to run the "Predowngrade.cmd" in the "3 - PreDebrick" directory.
At the end, you will see an Intel Logo (hourra). Disconnect you device, power off.
Then you have to run the "Downgrade.cmd" in the "3 - Full Debrick" directory.
The processus will stop, and the intel logo appears again.
Maintain + and - and power on your device for 4 secondes. The screen should remain off.
Disconnect you device, power off.
Then, Maintain + and - and power on your device for 4 secondes. The screen should remain off.
Reconnect your device
And hit enter on your computer.
And... Tadaaaaaaaaaaaaaaaaa ! It should work again ^^ ! You have just to flash the last firmware with Bootdroid ! Last firmware can be found here : https://www.asus.com/support/Download/28/7/0/10/Ss6JyhD8bOcmeH6f/32/
Sorry for my english, I'm french ^^ ! Hope it will help some peoples.
Will this work for k004?
Hello,
my FE375CG is bricked: when I turned it on, it's stuck on INTEL logo.
I tried your method, but, after third passage, I can't turned it off. So I waited battery discharge, but when I plug to recharge, the tablet turned on and stuck on INTEL screen, I' can't proceed to the fourth step (I' can't maintain + and - and power on your device for 4 seconds, it turns itself on, remains on INTEL bootscreen and I can't do anything)
Have you some suggestions?
This tutorial work for K01N/FE171CG??
Alviyansyah said:
This tutorial work for K01N/FE171CG??
Click to expand...
Click to collapse
I'd like to know as well.
Sent from my ASUS_Z00LD using Tapatalk 2
Successfully unbrick my ASUS FONEPAD 7 (FE375CG)
after trying more than 10 times i am succeeded. 2nd step of fulldebrick is quite difficult but it works.... volume + and - and power button pressing just 4 second and at 3rd second the screen will flash lightly which can be observed in dark environment.
help me please......... i have an FONEPAD 7 , but its ME175CG... probably i've bricked the device... i cant load recovery mode, the device is blocked in logo android green, and my pc doesn't read nothing!!! PLEAZ HELP ME!!!!
Fonepad k004 me371mg
Hello. I need a help tô my fonepad k004 me371mg. Its bricked. No droidboot. .. no system... nothing. .. only asus logo or usb cable logo. .. the imagem o found only raw formar. ... Tks
Is work in K00E? i need help
suzukube said:
Hello ! I had a problem on my FE375CG. It was rooted, and after an ASUS update, my device stuck with only a USB logo on the screen ! No Boot Droid nothing. There was a lot of error and I was unable to flash my device with Fastboot...
But I prepared a kit with a lot a tools to unbrick the devices ! I don't really know who are the authors of this tools, but here is the pack !
First Download the package : "Unbrick_Fonepad_7.zip" : https://mega.nz/#F!qM0EECyA
Second, unzip the package. Install the ADB drivers and the Intel DnX USB Drivers.
Then, Maintain + and - and power on your device for 4 secondes. The screen should remain off.
Connect the tablet to your computer : It should be recognize, screen remaining off.
Then you have to run the "Predowngrade.cmd" in the "3 - PreDebrick" directory.
At the end, you will see an Intel Logo (hourra). Disconnect you device, power off.
Then you have to run the "Downgrade.cmd" in the "3 - Full Debrick" directory.
The processus will stop, and the intel logo appears again.
Maintain + and - and power on your device for 4 secondes. The screen should remain off.
Disconnect you device, power off.
Then, Maintain + and - and power on your device for 4 secondes. The screen should remain off.
Reconnect your device
And hit enter on your computer.
And... Tadaaaaaaaaaaaaaaaaa ! It should work again ^^ ! You have just to flash the last firmware with Bootdroid ! Last firmware can be found here : https://www.asus.com/support/Download/28/7/0/10/Ss6JyhD8bOcmeH6f/32/
Sorry for my english, I'm french ^^ ! Hope it will help some peoples.
Click to expand...
Click to collapse
Your tutorial is not working for ASUS K004 and file xfstk-dldr-solo can not be run..
My device is not recognized by the pc. It shows the usb logo everytime. I opened the back cover and disconnected the battery. As soon as i connect the battery it turns on by itself, vibrates twice and shows the usb logo. it only turns off if i disconnect the battery. Without the battery it has the same behaviour if i connect the usb cable. None of the keys works except the VOL- or VOL+ and VOL - or PWR and VOL-. If i press vol- or any combination that has VOL- and connect the battery or the cable the device wont turn on and is not detected by the pc. If i do it with vol + or power or a combination of both it starts like i said earlier with two vibrations and the usb logo but not being detected. I'm lost because it being detected by the pc is a requirement. I installed drivers from folder 1 - ASUS_Android_USB_drivers_for_Windows and folder 2 - IntelDnXUSBDriverSetup.
The device is a FE375CG (K019) Asus Fonepad 7
Tried with windows 10 x64 on 2 different computers.
PS: I have disabled driver signature enforcement.
Hi
How can I obtain .img files for K00E (me372cg) ?
if Predownload Cmd worked just proceed to full debrick Download-3cmd then install updated firmware BESURE TO RENAME OFFICIAL FIRMWARE TO MOFD_SDUPDATE.zip it will auto install in recovery mode.
Hi,
My phone : ZE550ML
When I tried to update the TWRP recovery I installed .img file then everything collapsed.
My phone was only booting in bootloader, even if I chose normal boot.
I tried to install another .img file and since my phone doesn't want to do anything. No asus logo, no usb logo, no color nothing.
When I press power button nothing happen however how long I press even with volume button.
I charged it for a day long then I tried like a lot of times this procedure : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 .
(Surprisingly when I connect my phone to my computer sometimes the xfstk software recognize it)
But I always get : FW+OS download did not complete because of limit reconnecting to device attempt number reached.
Does someone have any idea ?
Hi everyone
my desire 320 suddenly gets into boot loop and i tried to get to recovery mode (by pressing up and power and even down and power) nothing happens just htc logo and restart. and disconnected the battery for about 6 hrs but the same.
And when connect it to PC just start --> HTC logo --> reboot and connect and disconnect sound form PC.
It's not rooted and on its stock status and i wasn't try to do anything for it just wake up at morning to find it at this loop.
so any help please
THANKS :good:
Use SP Flash Tools.
Sent from my Lenovo A526 using XDA-Developers Legacy app
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.