Hello,
Please help!
I own a herotab M10 and I did a reflash with the 9.7.rar which flashed ok and the device booted ok.
When I tried the MG106C flash (whith out giving it much thought and after playing with the system with 9.7.rar as root) it started flashing and halted for about an hour. I reseted the device and know when i press the power button, the light doesn't even go green. What can I do? I can understand the disability of booting the system but disability of powering up? what dowes it mean?
Thanks in advance!!
Related
I have a nexus s i9023, it was running well with 2.3.4 for three months. Got an OTA update for 2.3.6 two days ago, installed it.Im running stock, and the root is locked.
Everything seemed to be running fine on 2.3.6 when last night it just stopped responding and freezing. Taking battery out doesnt help, it again freezes at the colorful x logo or at the unlock screen.
I read on how to do a reset, but pressing volume down and power button gives me only a flash of blacklight (for a millisecond) and then nothing happens. tried it many times. What am I doing wrong?
Pressing volume up and power button gives me a fastboot menu, and recovery mode only gives me an exclamation mark android, then I have to take battery out again. I cannot mount the sd card or do anything else.
Any help or solution is most appreciated guys. Salute.
When you get to recovery, press again power+volume up (i think so), and you'll get some options. You can make factory reset there (as i can remember).
Also, there are many guides here on how to root and flash custom recovery via fastboot.
Check this out: http://forum.xda-developers.com/showthread.php?t=1007782
Just follow it, and when you flash custom recovery, you will be able to mount SD card, flash any ROM etc...
Good luck ...
i have the exacly same problem and i already try full wipe, install other ROM like oxygen and i cant pass the main logo... it's frozing all the time and i need pick up the battery to turn it off... :S
someone can help?
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
with wugfresh nexus root toolkit click on the button "soft-bricked"(flash stock + unroot) or something like that to restore the phone. After that try another time to unlock and root with a custom recovery (for example twrp).
When nexus root toolkit installing the original lollipop rom, look the "dos window" to see if the software shows errors, because sometimes the process ends without a real restore.
If you have other problems, please post a screenshot.
Fenix46 said:
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
Click to expand...
Click to collapse
Yes I was using a custom rom, but I not even reached the step where a was supposed to use the rom, I was steel still cleaning the divece.
Here is a photo from the screen I'm stuck in:
eeee.... I'll find a wint to send the photo to this forum ^^" wait
Hello guys,
some days ago my phone was permantly booting up in the recovery mode nothing else was possible. As I was on road and couldn't access internet anywhere I just tried to do some wipes, which then made my phone not show anything. I guess the reason that it didn't boot up anymore was that the battery was fully drained. When I was finally back home I was able to charge my phone but then the following happend:
I can start my OPO, see the android logo and then it turns black, but it fully boots up. I mean I can even click the touchscreen and hear some touch reactions/sounds. Also I'm able to turn up/down the volume and hear my phone. Furthermore I'm also able to do the "V-gesture" to turn on the flashlight. When I boot up into fastboot mode I also see the message "fastboot mode" + the little cyanogen face.
All in all everything seems to work, aside that I dont see anything else than dark after the logo.
I tried flashing new roms, stock reset, like seriously anything, but I can't get my phone to work probably again.
Does that mean that my phone got some hardware problems, maybe the touchscreen?
Help is appreciated, thanks in advance!
btw: English isn't my first language, so please excuse any mistakes.
You'll have to try flashing completely stock CM11 rom or CM12 rom, img by img in fastboot..modem, boot, system etc. I helped a friend who had this kind of problem. Probably not the cleanest way, but at least it works.
Already did that 3times using different methods. Stock CM11, CM12 and colorOS
I have a similar problem, did you manage to fix it? And if so, how?
Thanks,
Capelare.
I recently tried to install CWM on my LG Power running a stock ROM. but it didin't work. so when I try to factort reset, it turns off, then on and in the top left corner it shows an error message, after a bit it goes away, then the phone starts up normally without resetting. Help would be appreciated Thank you so much.
nomdeamon said:
I recently tried to install CWM on my LG Power running a stock ROM. but it didin't work. so when I try to factort reset, it turns off, then on and in the top left corner it shows an error message, after a bit it goes away, then the phone starts up normally without resetting. Help would be appreciated Thank you so much.
Click to expand...
Click to collapse
Hi
Thank you for using XDA Assist
You can post questions here instead
For sure there are device experts here
http://forum.xda-developers.com/showthread.php?t=2259645
----FIXED----- dunno how to delete posts
---- did specific combination of keys = power+vol_up till the screen turns black, power+vol_down after that, and all keys together till recovery mode boots up. Took me quite a bit of tries, reseted to stock and went on with flashing again from there ----
Hello all,
So I'll start off from the beginning. I was updating my 3.6 Havoc custom OS to the latest 4.2 Havoc custom OS. I started off with making a backup, went on with the data reset, booted into TWRP and flashed the v4.2 img on slot B. And then I booted into the system instead of rebooting into recovery, without Magisk flashed. I feel like not having Magisk flashed is the real culprit here. Please enlighten me on this topic if I'm wrong.
So the problem is that I'm stuck in an endless "bootloader in unlocked", tried out the combinations of pressing P+V_UP and P+V_DOWN, tried out pressing all 3 (P, V_UP, V_DOWN) buttons at the same time, also ADB and fast boot are not detecting the device, so I have no way of entering TWRP again. Please please please help me in fixing this
I have read many articles trying to find a solution to my problem, and none seem to be an closely related to my problem, please guide me to the thread if it already exists. Im on a Mac OSX so MSMtool won't be any help of me.. I would really really apreciate an urgent reply.
Thanks in advance.