I just got my Springboard, but I am having problem. When I turn it on, it goes through the logo screens and into the PIN pad. I enter the code, but after the home screen appears, the tablet turns off immediately and starts a loop of booting and turning off. If I do not enter PIN, the tablet turns off and starts rebooting loop.
When I press Power and Volume Up, the following screen appears: Enter into fastboot mode. You can press POWER key for more than 10 seconds to reboot device. It sticks on this screen until power runs out.
When I plug it through USB to computer, nothing gets recognized. I a running Win 7 Pro 64 bit. When I tried to turn it on plugged in through USB it installed Hi Suite and appeared for a while as CD drive until it powered off again.
Any ideas how to make it work?
try to re-flashing ROM. put "dload" folder in microSD then turn on your tablet. but to do this your battery must at least 50%
Just bricked my Tf201 - I cannot get it past the splash screen. I have tried the method of Holding down power and volume down but it does not get me into the recovery menu.
The device is rooted and the last action I did was in goomanager rebooting into recovery mode so I could install TWRP
I have my laptop hooked up to the tablet.
1: When I power button down for 3 seconds nothing happens
2: power down + volume up the tablet vibrates - usb disconnect then usb reconnect sound plays on my laptop. I cannot see the device on my laptop and my ADB devices command returns a blank
3: power button for 10 seconds - USB disconnect sound plays, tablet goes to splash screen and hangs there
4: power button + volume down for 5 seconds the splash screen reappears - no USB sound
5: power button & volume up - same result
6: After a couple cycles of this I notice that the laptop does detect that there is a device attached to the laptop but it cannot install the drivers.
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?