I've bought used one Spark (A31) that had problems after some kind of update (the only thing i know is that someone tried to update it with custom rom, i don't know what it was). In the past i've bricked Ainol Aurora (A9), but it was easy to unbrick, so i thought that it will be the same with the Spark, but i was wrong.
Spark is booting and hanging with some update message. You can translate it as "Android is updating. Starting aplications" or something like that. I've found that A31 do not let me start in recovery mode ("home, volume + power do not working"), PhoenixSuite (also LiveSuite) can't find the device ("home, plug usb, hit power many times"). I have the newest version of Android SDK and installed USB driver. Win7 x64.
btw: sorry for my english
Anyone help?
I tried PhoenixSuiteTools in few versions and also SDK and Win7 x64 is not recognizing my brick. I tried all the combinations of tablet buttons (back/+/-) with power tapping to force update under Phoenix and still nothing. I bought it from the second hand with a knowledge of update issues (i have no warranty on it) and had no idea that it can be something that i couldn't fix in one day.
I heard somewhere, that there is possibility to prepare bootable sd card, start with it and then force update from PC. I don't know how to do it and found no tuts in google.
Please help, I can't afford for gsm service that is taking 50$ for just opening the case...
Related
I'm stuck here and I need help to resolve this problem.
I'm a noob and I tried to flash my HTC Touch Pro 2 SPRINT with the Rhodium-HardSPL_V1_10_R3 after reading some threads on how to do that now.
But it didn't work kept on displaying Connection Error.I tried so many times but it didn't work out. Then I tried using the SSPL Manual as alternative.
I extracted and copied it to my device ( can't remember if my device was still plugged to my PC or not) and then ran the program.
My device went blank screen and I waited for some time and it didn't come on ( I waited patiently).
when nothing happened,I then removed the battery and tried hard resetting but it won't still come on.
Now,I cannot synchronized my device with my PC because it kept requesting for driver software for Qualcomm CDMA Technologies MSM (guess it no longer recognized my device) and my phone won't come. So I can't complete the flash.
Please I need help to resolve this problem...I have been a little unfortunate with HTC phones nd I need this to work.
I'm new here and will appreciate the help.
cosytony said:
I'm stuck here and I need help to resolve this problem.
I'm a noob and I tried to flash my HTC Touch Pro 2 SPRINT with the Rhodium-HardSPL_V1_10_R3 after reading some threads on how to do that now.
But it didn't work kept on displaying Connection Error.I tried so many times but it didn't work out. Then I tried using the SSPL Manual as alternative.
I extracted and copied it to my device ( can't remember if my device was still plugged to my PC or not) and then ran the program.
My device went blank screen and I waited for some time and it didn't come on ( I waited patiently).
when nothing happened,I then removed the battery and tried hard resetting but it won't still come on.
Now,I cannot synchronized my device with my PC because it kept requesting for driver software for Qualcomm CDMA Technologies MSM (guess it no longer recognized my device) and my phone won't come. So I can't complete the flash.
Please I need help to resolve this problem...I have been a little unfortunate with HTC phones nd I need this to work.
I'm new here and will appreciate the help.
Click to expand...
Click to collapse
the blank screen is fine.
you have a USB driver issue.
reinstall activesync if you are on XP, or windows mobile device center if you are on vista or windows 7.
Hi guys
This is my first thread here, so I hope that it is in right place.
Yesterday I received my elephone p8000 but I noticed a problem which I tried to resolved by myself. When I tried to switch on the phone, there was only a dark screen with booting sound. Recovery mode doesn't work so I thought that sp flash tool help when I use format and root phone and go in some way to recovery mode. I put on memory of phone a supersu, a then I format my phone by sp flash tool. I want to upgrade it by sp flash tool but I can't because I have got some problems with usb drivers, I see some errors during processing upgrade.
I have read the topic bbs.elephone hk viewthread&tid=6616&page=5&authorid=12774#.VfDLzZfLJ6I ( I can't post a full link here as a new guy ) and I had a hope that when I install these drivers it will help me, but it doesn't work.
Probably I made a mistake because I don't know too much about android enviroment, but I have the feeling that I'm close to repair my phone by myself, I would like to try some mtk 6753 usb drivers and MediaTek PreLoader USB VCOM (Android) but I can't find any on windows 7. Is there anybody who could help me? I'm sorry for my english, I tried to explain everything as good as I can.
Regards.
androidxda dot com/download-elephone-usb-drivers
Hi,
so you basically flashed your phone even though you knew that your USB driver is unstable? Don't do that!
Does your phone still boot (in any mode)?
Check if you can at least get into the bootloader. Hold volume up and power at the same time. If you can't, you probably screwed your device. Oh, and fix your Windows setup! The driver needs to be stable in order to flash the phone again!
Same problem!
you have to instal the package you have download with the tool.
i tried it on my laptop and i had all errors with the drivers. i tried my desktop (win 10 ) and it worked very wel.
i hoop i helped you!:good:
use PDAnet driver!!! And use spflash-tool to reinstall the stock rom!
So, this morning my son (who has a Nexus 5X) says his phone is bootlooping. I said "gimme that!..you don't know what you're doing." Lol
Thought I could fix it, but an hour later, a dozen google searches and trying a bunch of different things I can't get ADB mode to work on this phone!!
I'm using a Windows 10 PC that works fine with my Nexus 6P and ASUS tablet. I reinstalled USB drivers just in case but that's not it. I've tried different cables with no luck either.
I can get the 5X to boot into recovery mode where I see the dead Android robot with 'no command' under him. I then press the power button + volume up to get to ADB sideload menu. I can hear the "da da" music of the PC seeing something on the other end of the USB cord but no matter what I do, no ADB/Fastboot. I've even tried the LGUP tool, that even says no device attached.
I was hoping someone may have some way to restore the device. It boots up the Google logo then reboots Google logo then just shuts itself off. Every once in a while I can get it to boot to the Android boot animation for about 2 seconds before it freezes and shuts itself off. The device is about 11 months old (one year warranty?) and has never been rooted.
Thanks for any info... **I called Project Fi, going to get a replacement**
Sorry, I totally missed the last part before replying.
It could be a hardware failure. Since you're so close to 12 months, I would contact Google (or LG if not from google) and let them try to troubleshoot. That's the best way to get warranty repair. They will run you through any steps that might work. You just don't have much time to troubleshoot.
Sent from my Nexus 9 using Tapatalk
Mine does not appear at all on Windows or any operating system I'm guessing none if the init files should be zero bytes either I have no idea wth happened I check the root system with root browser and got this and my 5x is bootlocked I reset it dozens of times and still no recognition set mtp manually via devel options and nothing
Don't know about these files but re-installing (updating) all drivers seems to work for me. I've had to do this many times in the past 4 months for rooted N5, & N9, not rooted but bl-unlocked N5X, and virgin N5X. Never had to do this before and could use multiple devices interchangeably with Windows 10 which I've had since its beginning. Wugfresh has a driver install/repair section on his NRToolkit that can be helpful.
Sent from my Nexus 9 using Tapatalk
Sorry this is old thread. but I have same issue with nexus 5x. though it recently experienced BLOD and flashed 4cores. did you find a solution to your problem? mine however only recognized in adb on ubuntu. but no where else. no windows 10. and on ubuntu mtp didn't work
are you guys checking your adb device drivers in windows?
So, here's the deal with this phone. It's sat untouched for many many years. The original owner can't remember why she got rid of it (family friend). So I volunteered to take it, and turn it into an emulator device. However, it was made clear as to why she got rid of it. The phone is stuck in a gnarly boot loop. The boot loop is, Sony Ericsson screen lit up, and then goes to an unlit version of the logo. After a while, the phone will restart repeat. The phone will get into flash mode (green light) and will not continue the loop but stays on the unlit version of Sony Ericcson. I've gotten it into fastboot once, maybe twice, but I can't remember exactly how I did it (holding menu doesn't work)
I have installed the drivers for the phone, however, the phone is listed as:
E:\
Device Type: Portal Device
Manufacturer: SEMC
Location: on Volume
The drivers that it is apparently using is wpdfs.inf
Things I have tried to correct this issue.
-The Xperia app (tells me to enter flashmode in its own way and never does anything after)
-Flashing using "FlashTool"
It sees a phone but just says.
"19/025/2018 22:25:46 - INFO - Device connected with USB debugging off
19/025/2018 22:25:46 - INFO - For 2011 devices line, be sure you are not in MTP mode"
I've attempted using a fastboot method but nothing substantial as fastboot rarely happens.
Accessing the device through ADB (ADB shows not devices connected
Accessing the device through FastBoot (FastBoot shows "waiting for devices")
I have crawled through dozens of pages worth of information, similar questions, similar problems and come up short. Any advice would be super helpful.
Will provide images, and further information if requested. Thanks for your time.
I'm not familiar with the at version. Also maybe its already stated in the post and I miss it, did u try flashmode on flashtools and flash stock TFT?this is the first thing you wanna do in case of problems. For fastboot if I remember correctly you have to push search button and not the menu button, but I haven't my xplay with me.
inaroom said:
I'm not familiar with the at version. Also maybe its already stated in the post and I miss it, did u try flashmode on flashtools and flash stock TFT?this is the first thing you wanna do in case of problems. For fastboot if I remember correctly you have to push search button and not the menu button, but I haven't my xplay with me.
Click to expand...
Click to collapse
Hey, I did try flashing the stock firmware, the version is the AT&T version from the US. The problem with attempting to flash is Flashtool doesn't detect the phone. It sees that there's a phone plugged in, but flashing is impossible because it can't find the phone. I figured it must've been a driver issue, so I scoured the web to find drivers but only could find the 800a drivers, so I went ahead and attempted those, but not to no avail.
My next attempt to bring out Windows 7 and attempt to install the drivers on Windows 7, instead of 10. Just been a bit slow, and feeling a bit dejected on the whole project.
Disenfranchised said:
Hey, I did try flashing the stock firmware, the version is the AT&T version from the US. The problem with attempting to flash is Flashtool doesn't detect the phone. It sees that there's a phone plugged in, but flashing is impossible because it can't find the phone. I figured it must've been a driver issue, so I scoured the web to find drivers but only could find the 800a drivers, so I went ahead and attempted those, but not to no avail.
My next attempt to bring out Windows 7 and attempt to install the drivers on Windows 7, instead of 10. Just been a bit slow, and feeling a bit dejected on the whole project.
Click to expand...
Click to collapse
to install flashtools drivers in win 10 you need to disable uac but maybe you already did that. make sure the adb drivers are fully and correctly installe. have you tried flashing a kernel in fastboot mode by pushing the search button? also i would try to install r800i or r800a drivers. then i would suggest to make a little bit of search (i know you already did a lot...) to ensure that you can flash r800i or r800a firmware on your r800at and also try that route. i´m sorry i can´t help you more but i´m in europe and never worked on a r800at..
Hey, dont worry about it. This post is basically a hail mary for a phone that super old. I haven't tried flashing in fast boot because I have only ever gotten in fast boot once or twice. Fast boot is menu key correct? Cause I see conflict information all over the place.
i´m pretty sure it´s the search button for fastboot mode
Do you need a new battery?
Hi Disenfranchised,
I recently got out my old r800i GSM which was regularly being flung across the lounge by my kids, attached a charging cable and I had exactly the same boot loop issues as yours, but only as long as the phone was being charged. I ended up biting the bullet and buying a new battery and the phone started up. I ended up flashing Gin2Kat and it has been working well other than occasionally reverting back to the same behaviour for about an hour if the battery was completely discharged. The funny thing is when i finally manage to boot the phone at the right point during the boot loop cycle, the battery is only at 2%, meaning during the boot loop the battery is charging for maybe only a fraction of the on-off cycle.
It's a bit of an outlay (my battery was about GBP £10 - ebay). I now play SNES games on this every day during my commute. There are a few quibbles - the audio out port doesn't work (bluetooth audio works) and I get a wifi error but I ended up using Gin2Kat's apk installer to install my apps from micro-sd.
Anyway, it's a bit of a risk but see how it goes.
Fuzzy
So I just got this phone yesterday, and tried to update it via the Motorola Smart Assistant.
Clearly something went wrong, cause now the phone will not boot. It will load up AP Fastboot Flash mode, and nothing else can be done.
All I want is it to be on Oreo. I have read lots of guides, but I do not know which is the most simple way of doing this. I don't really want it rooted, just stock android.
Can anyone help?
I have the firmware for oreo, I just don't quite grasp how to get it running on the phone now. My pc does not seem to detect the phone anymore.
First, post, please, photo with error.
Then get latest Motorola drivers installed, and LMSA too. Is connection stable? Genuine cable? Use USB from the motherboard port directly? Other USB devices do work?
After you get phone be visible by PC you can attach diagnostic info that gives "fastboot getvar all". Download Minimal ADB package (see google, or here XDA), launch cmd, then this command.
Rayravage said:
So I just got this phone yesterday, and tried to update it via the Motorola Smart Assistant.
Clearly something went wrong, cause now the phone will not boot. It will load up AP Fastboot Flash mode, and nothing else can be done.
All I want is it to be on Oreo. I have read lots of guides, but I do not know which is the most simple way of doing this. I don't really want it rooted, just stock android.
Can anyone help?
I have the firmware for oreo, I just don't quite grasp how to get it running on the phone now. My pc does not seem to detect the phone anymore.
Click to expand...
Click to collapse
I had the same problem when trying to upgrade from 7.1.1 to Oreo.
I power off and on again with volume button down press and reconnect USB cable to PC
With the same Motorola Smart Assistant software open, click on Rescue tap
At first no action, but after few trials, the software re-flashes the phone and brings it back to Oreo boot screen.
You can also read the procedure from the post#2387 in the link below
https://slickdeals.net/f/12409510-6...at-t-smartphone-100-free-shipping?p=123370042
Good luck.
I just got my Z2 on the 25th. Bought brand new directly from Moto ATT variant. I just used the setting/system/System Updates. The phone came with 7.0 and I used the above to get it to 8.0.0. It actually took 4 times to get to Oreo but never had any problems. I've never trusted those up-date apps. They seem to work fine on some phones and not on others.
I'd do a factory reset and try to update through the Android settings.
I'm not rooted or anything just locked up ATT stock.
Or try this:
https://support.motorola.com/us/en/softwareupgrade
Thanks guys, I just asked for a replacement and got a new one shipped and sent off the messed up one. I'm not even going to bother updating this, as I am selling it anyway.