Hi,
I'm new here.
I have an issue. My Android phone is bricked. It is an MT6515 phone; model i9270+ (Chinese dual SIM phone).
I had trouble rooting it, so I was half way there following steps in THIS thread.
To see more specs. about this phone check HERE (chrome tells me that this site has malware, but I ignored it...)
On to the issue...
I accidentally flashed my phone with the wrong boot image from fast boot ("fastboot flash boot boot.img"). I had a clockwork mod backup copy of my own boot.img, so I just wanted to reflash it. Fastboot said that the flash failed.
I tried again, and then in the middle of the process my command prompt stalled. Phone was in flashing process for about an hour, so I hit Ctrl+C to stop it... I wanted to do a recovery from the phone itself using clockwork recovery...
When I wanted to boot my phone there was no screen light. The phone just vibrates twice and that's all.
PC won't recognize it, so I can't go back to fastboot mode. Key combination (vol up + power) won't bring fastboot mode...
This phone seems completely bricked...
Is there anything I can do to "revive" it?
I googled my issue, but I couldn't find anything useful. All simple solutions like getting the battery out for an hour, holding some weird key combinations, plugging it in USB on a different port, and such didn't get me any results...
Can anyone help me, please?
Thanks in advance!
More info...
Ok, I've just tested few more things:
When just holding a power button - phone vibrates once, and second time about 4 seconds after
When the battery is out and the phone is on USB - it does nothing
When the battery is in and I plug the USB (without pressing power) - it vibrates once, and second time about 1 second after
When holding Vol Up + Power (on this phone this is entering to fastboot) - does nothing
When holding Vol Up and plugging USB - PC recognized it as "SCI USB2Serial (COM10)" device, and the driver installation failed.
Before I typed this whole post PC recognized my phone as "unknown device", and the driver installation also failed.
Commant "adb devices" or "fastboot devices" does not recognize the phone while being plugged on USB.
When I plug it on electrical charger it vibrates twice just like pressing the power button.
Programs like "MTK Droid Root & Tools" do not recognize it...
Can anyone help me?
How to input in a new software? I have Boot.img, System.img and Recovery.img ...
@Admin -> you can close/delete this thread
I sold my phone... Some dude needed speakers, display and touch digitizer, so I this phone was of some good use for him
Related
Hey Guys, so i never usually post because i can usually solve my own problems, but i think this time i've out done myself.
So last night when installing CM12.1 using TWRP my xperia Z2 everything was looking rosy. Then when I tried to turn the phone on to boot the first time it gave me just a single little vibe but would not turn on.
I've tried ALL combinations of button resets - Nothing
I've tried to re-flash a stock image using flashboot - Nothing - it won't recognise flash or download mode when i plug it into my computer while holding down volume down
I've tried holding the volume up button while plugging it into my computer to try FASTBOOT mode - Nothing - the blue LED on the top comes on, but neither OSX or WIN7 recognises anything has been plugged into the computer and it doesn't register on ./fastboot devices
So have I actually properly ****ed my device? Or am i missing something?
Any help would be so massively appreciated. Like i said, i usually never ask.
Did you try another cable? Blue LED is good, so fastboot mode should work.
When it would be bricked, there would be no blue LED...
Did you look into device manager on WIN7? Any device like "S1boot" or "Sony ADB Interface" there?
Sony logo showing up, when turning the phone on?
Try "fastboot reboot or "fastboot reboot bootloader" even though "fastboot devices" doesn't show up as anything (weird). It should boot back to bootloader and register your device. This happened to me once.
I think it's "fastboot reboot-bootloader" and i think it won't work...
Try
Try holding the power button and volume up button in until it vibrates. Then you should be able to hold power button and volume button to get to download mode. This works on mine when all else fails, lol.
Hello XDA Community,
Sorry I didn't know where to post this...
Two weeks ago I purchased a Lenovo S8-50LC Tablet. It was working fine until last night, I was watching movies on Youtube and chatting with some friends. Then I went to bed and there was still around 50% charge in the battery.
When I woke up, I tired to wake up the device but it didn't respond. I thought it was stuck or something, so I tired to hold the power button for 20 seconds to do a hard reset but still didn't work. After that I plugged it in to a power source with the compatible charger that came with it and the screen light up with no data on it. I tried to power it on then and it showed the Lenovo logo and in a very tiny font underneath the logo it said "Boot Fail, Efi hard drive".
Then it would take me to a screen which says:
"EFI Shell version 2.31 [1.0]
Current running mode 1.1.2
map: Cannot find required map name.
Press ESC in 5 seconds to skip startup.nsh, any other key to continue.
Shell>_"
http://imageshack.com/a/img907/6979/reZJPf.jpg
and that's it!
I don't understand why this screen appears. I mean the tablet was working properly over the night and it had no issues whatsoever, but now it doesn't boot!
Then I tried to power it off and press Volume UP + Volume DOWN + Power Button, it showed a black screen with only one line: "FastBoot Starting...Can't get eMMC Info, revert to default value!"
http://imageshack.com/a/img661/1158/bRg9jj.jpg
That's all what I got...
PS:
1- The tablet does all that only when it's plugged to a power source, but when it's not plugged, it doesn't show anything.
2- When I plug it into the pc via USB, the pc doesn't recognize it.
3- I tried to boot into fastboot mode or recovery mode but it doesn't work either.
Please help me fix my tablet and I hope it's going to be soon. Thank you all in advance!
UPDATE:
1- I left it on the charger for maybe 2 hours and now it's turning on without being plugged in to a power source.
2- When I press Volume UP + Volume DOWN + Power Button, it shows the previous mentioned phrase, but now when I connect it to the pc via USB, windows recognizes it as Lenovo Composite ADB Interface under Android Phone
http://imageshack.com/a/img903/3907/oQdSAB.png
3- Tried to perform some fastboot commands like flash, format and erase, it always fails with the error:
Failed (remote: unknown command)
UPDATE2:
1- When executing ADB commands like adb devices it says "no devices found"
anyone?
Hello. A friend of mine has the same problem. He dropped the device and the screen cracked. After a reboot the tablet is on the same situation. I plugged a keyboard via otg , it stops the countdown in the EFI SHELL, but i can not type anything. I think is an eMMC related problem.
I guess the eMMC is totally fried or something. But, I mean, I didn't leave it on the charger all night or anything, why would it do such a thing!
any solutions or suggestions??
reflash the stock firmware: http://forum.xda-developers.com/showpost.php?p=58934356&postcount=90
mrhamed said:
reflash the stock firmware: http://forum.xda-developers.com/showpost.php?p=58934356&postcount=90
Click to expand...
Click to collapse
Thank you for your reply but it doesn't work .. as I mentioned earlier I don't have a "download mode" because any key combination I try to use just sends me to the shell window .. anymore suggestions would be appreciated!
-unplug usb cable
-turn off
-hold (volum+) and (volume -) towice
-press power button
It should go to fastboot quickly (a black screen with a little text)
Hi all,
I have just recently rooted my 306SH, the rooting process was fine. The problem started when I flashed an incompatible twrp image. Now I can't boot into anything it seems, no recovery, no fastboot and the power button will show only the logo screen. If connected to a power source the red led light will stay on even if unplugged. The device can be completely shut down and the red light off if I hold the down+volume and power down for few seconds.
I can connect it to my computer via usb by holding up+volume and power (green led light) . I installed google usb driver onto the android device and it stays connected for about 30 seconds to 1 minute. I tried using command prompt and SDK by typing "adb reboot recovery" but get an error message "error: device '(null)' not found.
Things I have installed on my computer:
(ADB, fast boot and drivers) https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
SDK Platform-tools
306SH:
Google USB driver
Is there anything I can do from my computer? I was thinking maybe I can flash in an image to replace it. And also my sim card pops out and can't be set back in, is this due to the incorrect flashing?
Any help or input is greatly appreciated, I've been working on this for a while and is getting no where.
Hi!
M4 Aqua, E2303
Brief history, what I did before:
- On a full stock OS, first, I unlocked bootloader with fastboot oem unlock, which went through nicely.
- After that, I followed this thread to install custom recovery (twrp). Went through nicely (fastboot flash recovery recovery.img and fastboot flash boot boot.img).
- I was able to boot into recovery (twrp), and with the Install function, selecting Conceptify .zip it installed, rebooted.
- On the boot, the Conceptify gear logo was stuck spinning for a very long time. Then I just tried going into TWRP again to install Conceptify again, maybe for the second try it installs without the boot issue.
After this, I was no longer able to enter twrp recovery again. Okay, tried to flash the .img's again (boot and recovery), maybe I can at least get into TWRP recovery again, but no luck, despite both flash commands going through (both sending, writing were OKAY), without errors.
Current symptoms at this point:
- I still can get into fastboot (vol Up + usb plug in; LED red, then blue), and my PC can recognize the phone being in fastboot correctly, with serial number (in fastboot devices). It can still perform the flash/erase commands, but whenever I try fastboot reboot or fastboot reboot-bootloader, it doesn't reboot the phone. At this point, fastboot devices gives back a device in fastboot mode, but with a lot of question marks (?) instead of the serial number. On unplugging it, LED stays blue, like it is frozen or somthing. I kill the phone off with the power cutoff switch (next to microsd).
- holding just Power to turn on phone: Sony logo on the white background and is stuck. After a while I kill off with power cutoff.
- holding Power + vol Up, it vibrates once every 2 seconds or so. Nothing on screen, when I stop holding the buttons, stop vibrating. It however stays in a weird state, cause I can't get into fastboot for example (vol down + usb plug in; like I can do when it was powered off completely). I kill off with power cutoff.
- holding Power + vol Down: Sony logo on the white bkg, and stuck. After a while I kill off with power cutoff.
- tried the all-button hold: Power + vol Down + vol Up for 30 seconds, it was just vibrating every 2-seconds.
- flashmode with Flashtool: I downloaded a stock .ftf, loaded into FlashTool, but upon asking to connect the phone while holding vol Down, it can't detect it. The phone however lights red, then green on the LED light. Tried with both a new Flashtool (0.9.32.0, and a recommended older one as well: 0.9.18.6).
Is there something else I could try to get a working TWRP recovery again, and be able to boot into it?
Thanks for your help!
My M4 (E2312) have pretty much the same symptoms: can not boot anything and just stuck on SONY logo, Flashtool does not recognize phone in flashmode (Vol -), just fastboot. And using fastboot to flash system, boot, recovery shows finished processes but phone does nothing new. And phone does not response well to USB, only after a reset then it updates the status.
I have Pexo ROM v3, custom TWRP, SkyMelon 9 I think,Rooted SuperSU and Magisk( has conflicts so when I boot some pop up says X app has stopped working. When I install some more apps to use it was ok, then the pop ups show up more and more and then it decides to boot loop to the stage we are now.
I have tried install 0.9.33 and 0.9.23.1( somehow only 0.9.23.1 can install 3 drivers), Xperia Companion, Emma, ggsetup 3.2.0.1, Driver SONY so0104 (so0113 ADB interface- status show it cannot start),
So either it is the drivers on computer, the computer USB ports, the phone's software or hardware defects lead to software that caused it.
bdnlspam said:
Hi!
M4 Aqua, E2303
Brief history, what I did before:
- On a full stock OS, first, I unlocked bootloader with fastboot oem unlock, which went through nicely.
- After that, I followed this thread to install custom recovery (twrp). Went through nicely (fastboot flash recovery recovery.img and fastboot flash boot boot.img).
- I was able to boot into recovery (twrp), and with the Install function, selecting Conceptify .zip it installed, rebooted.
- On the boot, the Conceptify gear logo was stuck spinning for a very long time. Then I just tried going into TWRP again to install Conceptify again, maybe for the second try it installs without the boot issue.
After this, I was no longer able to enter twrp recovery again. Okay, tried to flash the .img's again (boot and recovery), maybe I can at least get into TWRP recovery again, but no luck, despite both flash commands going through (both sending, writing were OKAY), without errors.
Current symptoms at this point:
- I still can get into fastboot (vol Up + usb plug in; LED red, then blue), and my PC can recognize the phone being in fastboot correctly, with serial number (in fastboot devices). It can still perform the flash/erase commands, but whenever I try fastboot reboot or fastboot reboot-bootloader, it doesn't reboot the phone. At this point, fastboot devices gives back a device in fastboot mode, but with a lot of question marks (?) instead of the serial number. On unplugging it, LED stays blue, like it is frozen or somthing. I kill the phone off with the power cutoff switch (next to microsd).
- holding just Power to turn on phone: Sony logo on the white background and is stuck. After a while I kill off with power cutoff.
- holding Power + vol Up, it vibrates once every 2 seconds or so. Nothing on screen, when I stop holding the buttons, stop vibrating. It however stays in a weird state, cause I can't get into fastboot for example (vol down + usb plug in; like I can do when it was powered off completely). I kill off with power cutoff.
- holding Power + vol Down: Sony logo on the white bkg, and stuck. After a while I kill off with power cutoff.
- tried the all-button hold: Power + vol Down + vol Up for 30 seconds, it was just vibrating every 2-seconds.
- flashmode with Flashtool: I downloaded a stock .ftf, loaded into FlashTool, but upon asking to connect the phone while holding vol Down, it can't detect it. The phone however lights red, then green on the LED light. Tried with both a new Flashtool (0.9.32.0, and a recommended older one as well: 0.9.18.6).
Is there something else I could try to get a working TWRP recovery again, and be able to boot into it?
Thanks for your help!
Click to expand...
Click to collapse
Yes, I also tried installing conceptify but it doesnt work. At this point its better if you stick with the stock rom, remove as much bloatware as possible and consider it a phone because almost none of the ROMs here work stability wise, or they maybe stable but some features like display brightness or speakers dont work. So I recommend you install stock rom via flashtool and then unlock the bootloader via flashtool again and install twrp again. Also if possible try reinstalling the drivers for the phone in flashtool. Hope this works mate.
Not my name said:
Also if possible try reinstalling the drivers for the phone in flashtool.
Click to expand...
Click to collapse
Thanks for your answer!
Unfortunately, I still can't make Flashtool recognize my M4 as booted in flashmode. Tried installing the drivers with \Flashtool\drivers\Flashtool-drivers.exe , but choosing the "Flashmode drivers" option, it failed during the install (I guess cause there wasnt a connected device that supports it), tried both with phone being connected in flashmode (volDown + plug-inUSB), and phone disconnected as well.
bdnlspam said:
Thanks for your answer!
Unfortunately, I still can't make Flashtool recognize my M4 as booted in flashmode. Tried installing the drivers with \Flashtool\drivers\Flashtool-drivers.exe , but choosing the "Flashmode drivers" option, it failed during the install (I guess cause there wasnt a connected device that supports it), tried both with phone being connected in flashmode (volDown + plug-inUSB), and phone disconnected as well.
Click to expand...
Click to collapse
Can you try it on a Linux PC I guess?
I tried to root my phone by magisk.
After flashing a patched boot.img, it's failed to boot into system and I got a message that "the device need factory reset". I clicked yes and everything seems ok,I can boot into system. Then I tried to flash img again. So I boot into bootloader. Unfortunately, this time I got a black screen. The phone doesn't response me anymore.
I tried the software repair in xperia companion but It cannot dected my phone when I hold on volume down and plugged in it. I also tried hold on volume up + power but nothing happened. Hold on power key also no response. The led light always black, only become red when I connect it to my pc.
What should I so now and what's my phone's status? I searched something about 9008 mode and edl but I don't know how to check whether my phone is really turn into that status, my pc cannot dect my phone.
Have the same problem, only with the 5 iii instead. Still looking for a fix.
Try to switch the phone off; then just plug it into your PC without holding the Vol- key. It has happenned a couple of times with me that the phone does not want to boot up, with attempts to get it into FLASH mode by holding the key down throwing more confusion into the mix.
I think there is a low battery protection. Make sure the phone is charged up. Keeps the device from death during a flash.
Red led mean a very low battery. Keep it plugged (not to PC but to power adapter) for 2-3 hours and then try again a force reset.
Never, never try flash or other stuff under 50% battery
Also force restart is keep pressed vol+ and power button (or vol- and power button) till you fell a vibration.
Try this after a good charge
Evil_Sephiroth said:
Red led mean a very low battery. Keep it plugged (not to PC but to power adapter) for 2-3 hours and then try again a force reset.
Never, never try flash or other stuff under 50% battery
Also force restart is keep pressed vol+ and power button (or vol- and power button) till you fell a vibration.
Try this after a good charge
Click to expand...
Click to collapse
It might require experimenting with service modes and different chargers. I had an early Xperia 1 III that bootlooped while charging after setting up the fingerprint reader. It seems that charging is disabled during booting. It has to finish or enter a service/fault mode.
my phone is having this after doing fastboot --slot=b reboot recovery (which actually I had to do fastboot --set-slot=b and then fastboot reboot recovery). the notification light blinks red. have tried vol up + power, vol down + power, and vol up + down + power for like 30 seconds and nothing
tomatoketchup said:
my phone is having this after doing fastboot --slot=b reboot recovery (which actually I had to do fastboot --set-slot=b and then fastboot reboot recovery). the notification light blinks red. have tried vol up + power, vol down + power, and vol up + down + power for like 30 seconds and nothing
Click to expand...
Click to collapse
I feel sorry for you brother...such a nice device...OK let's talk what happened, the state now your device is in is called hardbrick and it had a corrupted bootloader or no boot loader, but your device is still alive, in your PC in device manager it lists as Qs USB mode with some number after it like qsusb9008...now this device can only be brought to life with the help of a blankflash file which can flash your boot loader in snapdragon service mode...actually no snapdragon can be hardbricked permanently now you need appropriate blankflash file for your device.. Please don't open the device if some repairmen suggests to do JTAG nothing is necessary all you need is blankflash file which is shared to only Sony testers groups.... Who tests ROMs before release and they hardbrick so they share those files to them.... Please don't loose hope....it takes time but certainly it can be bought back to life... And dont try any flashing utility as there is no functional boot loader on it now and nothing will work...Sony won't provide that for sure and they will say then can only solve by mother board replacement ,don't believe therm your device is perfect it only needs blankflash file as it entered into final safe mode... I ain't regular on XDA if you need any info contact me via my mail [email protected] g ma I'll .com
Have any of you tried this - https://developer.sony.com/develop/open-devices/get-started/flash-tool/download-flash-tool/
ok in my case it was the charging IC