Related
Hello guys,
I've got a big problem with my I9300 and therefore I would like to ask here for any help. (If I'm in the wrong section, please move the thread to a correct one)
I had installed the Resurrection Remix ROM, v5.2.6. from 30.12.2014 and Googy-Max 2 recovery (CWM based) on my phone. I was using it for days and all worked fine.
One day I turned the phone off and I wanted to restart it. But it never restarted again; it ends up in a boot loop. It shows me the white Samsung Boot-Logo for some seconds, then a total black screen and the same thing repeats in a loop.
So I wanted to get into the recovery for wiping etc. but I couldn’t access the recovery. Nothing happens by pressing the relevant buttons. The device is still hanging in the boot loop. So I wanted to flash via Odin, but this isn't possible. I also can't go into the download mode. After pressing the relevant buttons, the green warning screen appears, which asks me if I really want to go to the download mode. But when I press volume up for "continue" or even if I don't press anything, the phone turns off and the boot loop with the white Samsung Logo starts again.
Therefore I ordered a USB JIG for forcing the device to go into download mode. When I plug the USB JIG in, the device actually goes into download mode but this status holds on only for a few seconds. After accessing download mode through the JIG, after a few seconds the phone turns off, restarts, (and because the JIG is still plugged in) the download mode appears again and it ends in a loop.
At first I thought maybe the power button is sticking and therefore the device turns on and off autonomous. But definitively I can negate it, because I opened the phone and removed the power button and nothing changed. Also by pressing the power button on the mainboard I can clearly hear the "click".
So I started a new attempt. Although the time, in which the device stays in download mode before turning off, is very short (only a few seconds), I tried flashing an other recovery, namely TWRP v2.8.3.0. So I prepared ODIN, plugged the JIG into the device, by appearing the download mode I switched cables and an other person clicked start at ODIN and it worked. So now TWRP is installed. Now I also can't get into recovery but after flashing TWRP there exist two little differences. First, after pressing the relevant buttons, TWRP appears for less than 1 second until the phone turns off. Secondly, when I plug the device in for charging, the Samsung charging logo appears for some seconds, then for less than 1 second appears a charging logo from Lollipop and the device ends up in a loop by displaying alternately the two different charging logos. Before flashing TWRP, the device booted in a boot loop (as I wrote above) by plugging it in for charging.
So the main question: how can I get my device work again
I tried telling you all details so that you have a better view of the problem.
Maybe I should flash a fully (stock) rom, but as I told you the download mode appears only for a few seconds. Flashing a recovery was possible, because the recovery file is very small - 7 MB. A full rom is much bigger and I think by flashing a complete rom, the device would turn off while Odin is flashing, therefore I ask first here for any assistance.
Thank you very much in advance!
beginnerteur said:
Hello guys,
I've got a big problem with my I9300 and therefore I would like to ask here for any help. (If I'm in the wrong section, please move the thread to a correct one)
I had installed the Resurrection Remix ROM, v5.2.6. from 30.12.2014 and Googy-Max 2 recovery (CWM based) on my phone. I was using it for days and all worked fine.
One day I turned the phone off and I wanted to restart it. But it never restarted again; it ends up in a boot loop. It shows me the white Samsung Boot-Logo for some seconds, then a total black screen and the same thing repeats in a loop.
So I wanted to get into the recovery for wiping etc. but I couldn’t access the recovery. Nothing happens by pressing the relevant buttons. The device is still hanging in the boot loop. So I wanted to flash via Odin, but this isn't possible. I also can't go into the download mode. After pressing the relevant buttons, the green warning screen appears, which asks me if I really want to go to the download mode. But when I press volume up for "continue" or even if I don't press anything, the phone turns off and the boot loop with the white Samsung Logo starts again.
Therefore I ordered a USB JIG for forcing the device to go into download mode. When I plug the USB JIG in, the device actually goes into download mode but this status holds on only for a few seconds. After accessing download mode through the JIG, after a few seconds the phone turns off, restarts, (and because the JIG is still plugged in) the download mode appears again and it ends in a loop.
At first I thought maybe the power button is sticking and therefore the device turns on and off autonomous. But definitively I can negate it, because I opened the phone and removed the power button and nothing changed. Also by pressing the power button on the mainboard I can clearly hear the "click".
So I started a new attempt. Although the time, in which the device stays in download mode before turning off, is very short (only a few seconds), I tried flashing an other recovery, namely TWRP v2.8.3.0. So I prepared ODIN, plugged the JIG into the device, by appearing the download mode I switched cables and an other person clicked start at ODIN and it worked. So now TWRP is installed. Now I also can't get into recovery but after flashing TWRP there exist two little differences. First, after pressing the relevant buttons, TWRP appears for less than 1 second until the phone turns off. Secondly, when I plug the device in for charging, the Samsung charging logo appears for some seconds, then for less than 1 second appears a charging logo from Lollipop and the device ends up in a loop by displaying alternately the two different charging logos. Before flashing TWRP, the device booted in a boot loop (as I wrote above) by plugging it in for charging.
So the main question: how can I get my device work again
I tried telling you all details so that you have a better view of the problem.
Maybe I should flash a fully (stock) rom, but as I told you the download mode appears only for a few seconds. Flashing a recovery was possible, because the recovery file is very small - 7 MB. A full rom is much bigger and I think by flashing a complete rom, the device would turn off while Odin is flashing, therefore I ask first here for any assistance.
Thank you very much in advance!
Click to expand...
Click to collapse
Check and make sure that your volume buttons and home button are not stuck also. If they are not, I would suggest a visit to a repair shop as your EMMC chip might be weak already.
beginnerteur said:
Hello guys,
I've got a big problem with my I9300 and therefore I would like to ask here for any help. (If I'm in the wrong section, please move the thread to a correct one)
I had installed the Resurrection Remix ROM, v5.2.6. from 30.12.2014 and Googy-Max 2 recovery (CWM based) on my phone. I was using it for days and all worked fine.
One day I turned the phone off and I wanted to restart it. But it never restarted again; it ends up in a boot loop. It shows me the white Samsung Boot-Logo for some seconds, then a total black screen and the same thing repeats in a loop.
So I wanted to get into the recovery for wiping etc. but I couldn’t access the recovery. Nothing happens by pressing the relevant buttons. The device is still hanging in the boot loop. So I wanted to flash via Odin, but this isn't possible. I also can't go into the download mode. After pressing the relevant buttons, the green warning screen appears, which asks me if I really want to go to the download mode. But when I press volume up for "continue" or even if I don't press anything, the phone turns off and the boot loop with the white Samsung Logo starts again.
Therefore I ordered a USB JIG for forcing the device to go into download mode. When I plug the USB JIG in, the device actually goes into download mode but this status holds on only for a few seconds. After accessing download mode through the JIG, after a few seconds the phone turns off, restarts, (and because the JIG is still plugged in) the download mode appears again and it ends in a loop.
At first I thought maybe the power button is sticking and therefore the device turns on and off autonomous. But definitively I can negate it, because I opened the phone and removed the power button and nothing changed. Also by pressing the power button on the mainboard I can clearly hear the "click".
So I started a new attempt. Although the time, in which the device stays in download mode before turning off, is very short (only a few seconds), I tried flashing an other recovery, namely TWRP v2.8.3.0. So I prepared ODIN, plugged the JIG into the device, by appearing the download mode I switched cables and an other person clicked start at ODIN and it worked. So now TWRP is installed. Now I also can't get into recovery but after flashing TWRP there exist two little differences. First, after pressing the relevant buttons, TWRP appears for less than 1 second until the phone turns off. Secondly, when I plug the device in for charging, the Samsung charging logo appears for some seconds, then for less than 1 second appears a charging logo from Lollipop and the device ends up in a loop by displaying alternately the two different charging logos. Before flashing TWRP, the device booted in a boot loop (as I wrote above) by plugging it in for charging.
So the main question: how can I get my device work again
I tried telling you all details so that you have a better view of the problem.
Maybe I should flash a fully (stock) rom, but as I told you the download mode appears only for a few seconds. Flashing a recovery was possible, because the recovery file is very small - 7 MB. A full rom is much bigger and I think by flashing a complete rom, the device would turn off while Odin is flashing, therefore I ask first here for any assistance.
Thank you very much in advance!
Click to expand...
Click to collapse
Your power button is failing, stuck in 'pressed' position. Try pressing repeatedly power button for several seconds, then release it completely. It shall bring it back to life. Visit your local service, or prepare tin, heat gun and soldering pistol. One button cost $0.2, they are selling them on eBay in sets of three (and 10, and 100....).
Happened to me some time ago, and video on youtube helped me to dismantle my phone, pull broken button out of it, and change it for new.
My phone was cycling like yours.
beginnerteur said:
Hello guys,
I've got a big problem with my I9300 and therefore I would like to ask here for any help. (If I'm in the wrong section, please move the thread to a correct one)
I had installed the Resurrection Remix ROM, v5.2.6. from 30.12.2014 and Googy-Max 2 recovery (CWM based) on my phone. I was using it for days and all worked fine.
One day I turned the phone off and I wanted to restart it. But it never restarted again; it ends up in a boot loop. It shows me the white Samsung Boot-Logo for some seconds, then a total black screen and the same thing repeats in a loop.
So I wanted to get into the recovery for wiping etc. but I couldn’t access the recovery. Nothing happens by pressing the relevant buttons. The device is still hanging in the boot loop. So I wanted to flash via Odin, but this isn't possible. I also can't go into the download mode. After pressing the relevant buttons, the green warning screen appears, which asks me if I really want to go to the download mode. But when I press volume up for "continue" or even if I don't press anything, the phone turns off and the boot loop with the white Samsung Logo starts again.
Therefore I ordered a USB JIG for forcing the device to go into download mode. When I plug the USB JIG in, the device actually goes into download mode but this status holds on only for a few seconds. After accessing download mode through the JIG, after a few seconds the phone turns off, restarts, (and because the JIG is still plugged in) the download mode appears again and it ends in a loop.
At first I thought maybe the power button is sticking and therefore the device turns on and off autonomous. But definitively I can negate it, because I opened the phone and removed the power button and nothing changed. Also by pressing the power button on the mainboard I can clearly hear the "click".
So I started a new attempt. Although the time, in which the device stays in download mode before turning off, is very short (only a few seconds), I tried flashing an other recovery, namely TWRP v2.8.3.0. So I prepared ODIN, plugged the JIG into the device, by appearing the download mode I switched cables and an other person clicked start at ODIN and it worked. So now TWRP is installed. Now I also can't get into recovery but after flashing TWRP there exist two little differences. First, after pressing the relevant buttons, TWRP appears for less than 1 second until the phone turns off. Secondly, when I plug the device in for charging, the Samsung charging logo appears for some seconds, then for less than 1 second appears a charging logo from Lollipop and the device ends up in a loop by displaying alternately the two different charging logos. Before flashing TWRP, the device booted in a boot loop (as I wrote above) by plugging it in for charging.
So the main question: how can I get my device work again
I tried telling you all details so that you have a better view of the problem.
Maybe I should flash a fully (stock) rom, but as I told you the download mode appears only for a few seconds. Flashing a recovery was possible, because the recovery file is very small - 7 MB. A full rom is much bigger and I think by flashing a complete rom, the device would turn off while Odin is flashing, therefore I ask first here for any assistance.
Thank you very much in advance!
Click to expand...
Click to collapse
As said your emmc chip maybe failing.
The dead boot thread maybe of interest to you.
Virnik0 said:
Your power button is failing, stuck in 'pressed' position. Try pressing repeatedly power button for several seconds, then release it completely. It shall bring it back to life. Visit your local service, or prepare tin, heat gun and soldering pistol. One button cost $0.2, they are selling them on eBay in sets of three (and 10, and 100....).
Happened to me some time ago, and video on youtube helped me to dismantle my phone, pull broken button out of it, and change it for new.
My phone was cycling like yours.
Click to expand...
Click to collapse
He said he has tested this and can also hear the micro-switch clicking.
scorpionhd2 said:
Check and make sure that your volume buttons and home button are not stuck also. If they are not, I would suggest a visit to a repair shop as your EMMC chip might be weak already.
Click to expand...
Click to collapse
Virnik0 said:
Your power button is failing, stuck in 'pressed' position. Try pressing repeatedly power button for several seconds, then release it completely. It shall bring it back to life. Visit your local service, or prepare tin, heat gun and soldering pistol. One button cost $0.2, they are selling them on eBay in sets of three (and 10, and 100....).
Happened to me some time ago, and video on youtube helped me to dismantle my phone, pull broken button out of it, and change it for new.
My phone was cycling like yours.
Click to expand...
Click to collapse
Darke5tShad0w said:
As said your emmc chip maybe failing.
The dead boot thread maybe of interest to you.
He said he has tested this and can also hear the micro-switch clicking.
Click to expand...
Click to collapse
Thank you very much for helping! :good:
So the question is, whether it's the power button's or emmc's fault...
I did a little searching and found this video. I've got exactly the same problem like the guy. At 1:06 following the boot loop, at 1:34 following the problem with downlod mode.
Although he thinks it's caused to the sudden death problem, but at least in my case I think it's wrong because months ago I did the eMMC Brickbug Check.
Also I noticed a probably important detail. When I put the battery in the phone, it automatically turns on without pressing the power button like in 1:04-1:09 in the video. Which normal working phone turns itself on by simply putting in the battery...?
So it must get a command for turning on - (possibly through a defect power button?)
@Virnik0, do you remember, if you could hear the micro-switch clicking on your phone before replacing the button on the mainboard?
beginnerteur said:
Also I noticed a probably important detail. When I put the battery in the phone, it automatically turns on without pressing the power button
Click to expand...
Click to collapse
Your power button is faulty, replace it before you try fixing anything else.
Thank you very, very much for helping! :good: :good: :good:
Truly the power button was fault although you could hear clearly the "click".
I unsoldered and removed the power module and (by startig with JIG and rebooting via ADB) the phone works as it should. :victory:
Now I'm trying to solder a new power button......it's a bit tricky
Again, thank you very much guys!
I had the same problem, pressed the button many times, and it helped. Thank you for your suggestions
Hello everybody,
I bought the Nabi 2, as refurbished, for my little child and from the beginning I am having problems to turn it on or wake it up from sleep. It is not rooted, has everything stock and I have also applied all available official updates (OTA).
The problem is to turn it on, both from sleep or from powered down state. For example, being in sleep mode (display off) for a few hours, to wake it up I have first to press the power button for about 10 seconds, than release it and press again until... the start up Logo appears, as it was completely shut down! Maybe through pushing the power button first time I turn it off unintentional, so the second time it has to power up and load the OS? But just pushing the power button shortly will not wake it up at all from sleep mode... Is this a known problem and is there a solution for it?
Thanks in advance for each advice!
Conrad
Conrad-007 said:
Hello everybody,
I bought the Nabi 2, as refurbished, for my little child and from the beginning I am having problems to turn it on or wake it up from sleep. It is not rooted, has everything stock and I have also applied all available official updates (OTA).
The problem is to turn it on, both from sleep or from powered down state. For example, being in sleep mode (display off) for a few hours, to wake it up I have first to press the power button for about 10 seconds, than release it and press again until... the start up Logo appears, as it was completely shut down! Maybe through pushing the power button first time I turn it off unintentional, so the second time it has to power up and load the OS? But just pushing the power button shortly will not wake it up at all from sleep mode... Is this a known problem and is there a solution for it?
Thanks in advance for each advice!
Conrad
Click to expand...
Click to collapse
The only semi known issue I have seen is when you put the tablet to sleep and it's charging. In some instances the tablet will lock up at some point after going to sleep. When you try to wake in up via power button it is locked up. When you hold the power button for 10sec you are hard powering it off and then it reboots. If yours wasn't charging then I haven't read much about anyone having a similar problem.
aicjofs said:
The only semi known issue I have seen is when you put the tablet to sleep and it's charging. In some instances the tablet will lock up at some point after going to sleep. When you try to wake in up via power button it is locked up. When you hold the power button for 10sec you are hard powering it off and then it reboots. If yours wasn't charging then I haven't read much about anyone having a similar problem.
Click to expand...
Click to collapse
Thanks for your reply, aicjofs.
In my case it happens always, no matter if charging or not... and it's annoying.
Would rooting and installing a custom ROM solve the problem? If yes, is there a custom ROM dedicated to kids, similar with the stock one?
Conrad
Wrong Section Buddy !!!
StariX37 said:
Wrong Section Buddy !!!
Click to expand...
Click to collapse
and why ???
StariX37 said:
Wrong Section Buddy !!!
Click to expand...
Click to collapse
:thumbdown:
Ignore this guy. I have a friend with the same power on issue with her Nabi 2, and I'm interested to read the solution here.
...no other hints concerning my problem ?
Please, if somebody has an idea, just reply here.
Conrad-007 said:
...no other hints concerning my problem ?
Please, if somebody has an idea, just reply here.
Click to expand...
Click to collapse
I'm still struggling with the random problems on my Nabi...
Is it possible to check the integrity and/or health of internal memory, find and mark bad blocks, etc. using a computer (Windows or Linux) connected through USB? If yes, how? Do I need to flash TWRP or something else on the Nabi before?
Thanks in advance for your help.
Conrad
Conrad-007 said:
I'm still struggling with the random problems on my Nabi...
Is it possible to check the integrity and/or health of internal memory, find and mark bad blocks, etc. using a computer (Windows or Linux) connected through USB? If yes, how? Do I need to flash TWRP or something else on the Nabi before?
Thanks in advance for your help.
Conrad
Click to expand...
Click to collapse
The latest TWRP should have a section under the wipe menu where you can repair the file system which is probably easiest, although you need to be careful what you are doing in there as it is called the "wipe" tab for a reason. Should be able to go to wipe menu, select data partition checkbox, select change or repair filesystem(don't swipe to wipe, click the words check/repair etc) and select check in the next screen.
To do a filesystem check the partition can not be mounted so you do it from recovery not in Android. Since stock recovery you can't use ADB you pretty much need TWRP one way or another.
If you don't want to use the graphical interface in TWRP you can do it over USB with ADB and use e2fsck on the partitions after unmounting them, but it's going to be doing the same thing you will just see a more verbose version if you do it over adb.
Thanks a lot, aicjofs.
I will try to root and install first TWRP, as my Nabi is still untouched.
One thing I remarked: at the moment, when I go in the (stock) recovery and want to do a "Wipe data/factory reset", 2 lines are displayed before "-- Wipping data...": "E: missing bitmap stage_empty (Code -l)" and "E:missing bitmap stage_fill (Code -l)". After that, the wiping process seems to run normal, as I get the message "Data wipe complete." at the end.
Do you know what that lines are meaning? Could those lines help to debug the main problem ?
Update: NO WAY to get TWRP on my Nabi, regardless how hard I try...
NabiLab 2015 recognize the Nabi without problems, but as soon as I select "Recovery installer", Nabi should reboot-bootloader (I suppose), but hangs at Nabi Logo (the small icon in the middel of screen) forever. Also in Control Panel, the device is shown as ""Fastboot" with the error symbol and the indication that the driver should be installed again (but of course, when I try to do it, Windows tells me that the newest drivers for that device are already installed).
I also tried with using directly adb in a cmd window, with the same result, as soon as I type "adb reboot-bootloader" and press enter.
I am really out of ideas...
Conrad-007 said:
Update: NO WAY to get TWRP on my Nabi, regardless how hard I try...
NabiLab 2015 recognize the Nabi without problems, but as soon as I select "Recovery installer", Nabi should reboot-bootloader (I suppose), but hangs at Nabi Logo (the small icon in the middel of screen) forever. Also in Control Panel, the device is shown as ""Fastboot" with the error symbol and the indication that the driver should be installed again (but of course, when I try to do it, Windows tells me that the newest drivers for that device are already installed).
I also tried with using directly adb in a cmd window, with the same result, as soon as I type "adb reboot-bootloader" and press enter.
I am really out of ideas...
Click to expand...
Click to collapse
The hang with Nabi logo is because the fastboot driver is somehow broke. You will likely have to install it manually. Which driver are you using?
I gave most of the driver options here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
aicjofs said:
The hang with Nabi logo is because the fastboot driver is somehow broke. You will likely have to install it manually. Which driver are you using?
I gave most of the driver options here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Click to expand...
Click to collapse
You were right! I've installed the "nacked" driver on a fresh windows 7 and now I have TWRP on my Nabi 2!!! Thanks a lot!!!
Now is there a way to get rid of the freezing problem when I attach the charger while Nabi is on? Right now, if I attach the charger this way, Nabi 2 will freeze completely and only a reboot can get the normal functionality back!?!
Charging the Nabi in "off" state works however...
Conrad-007 said:
You were right! I've installed the "nacked" driver on a fresh windows 7 and now I have TWRP on my Nabi 2!!! Thanks a lot!!!
Now is there a way to get rid of the freezing problem when I attach the charger while Nabi is on? Right now, if I attach the charger this way, Nabi 2 will freeze completely and only a reboot can get the normal functionality back!?!
Charging the Nabi in "off" state works however...
Click to expand...
Click to collapse
I dont have Nabi2's anymore but both my kids tablets did the same thing. I never really found a solution. I did buy a cable from Nabi store that has the orange braid covering. It seemed to make a difference, but it still happened from time to time.
Happy New Year!
As I mentioned, I was finally able to install TWRP and did all wiping, cleaning, repairing tasks that were available
After that I flashed the "Nabixus 0.1beta for Nabi 2" ROM which worked very nice.
But... I still have the same problems starting up the Nabi!
When I finally succeed to start it (after many trials), it works well, but if I let it go in standby and wait more that a few minutes, I am not able to wake it up again and I have to do a restart (about 10 sec. hold the Power button down).
What I`m not getting at all: is this a software or a hardware problem? Can my Nabi 2 be repaired after all, or I just have to scrap it?
The last thing I could still think to try would be to repair the partition table through TWRP / Adb / Adb shell. Should I try it? Where can I get a good partition table for my NV7A and, after having it, which commands are required?
... aicjofs, please... help
Conrad-007 said:
Happy New Year!
As I mentioned, I was finally able to install TWRP and did all wiping, cleaning, repairing tasks that were available
After that I flashed the "Nabixus 0.1beta for Nabi 2" ROM which worked very nice.
But... I still have the same problems starting up the Nabi!
When I finally succeed to start it (after many trials), it works well, but if I let it go in standby and wait more that a few minutes, I am not able to wake it up again and I have to do a restart (about 10 sec. hold the Power button down).
What I`m not getting at all: is this a software or a hardware problem? Can my Nabi 2 be repaired after all, or I just have to scrap it?
The last thing I could still think to try would be to repair the partition table through TWRP / Adb / Adb shell. Should I try it? Where can I get a good partition table for my NV7A and, after having it, which commands are required?
Click to expand...
Click to collapse
You can't repair the partition table from adb/TWRP. It's read only. You could through nvflash but I don't think the partition table could possibly cause the issue. I think you are meaning fix super blocks and inodes of the filesystem? Even that is a stretch if it's happening how you describe it but with a try. Did you try repair filesystem like we talked about earlier? If not backup all the data and try a wipe data. That will make sure to blow away and reformat the data partition.
It could be hardware. I know for sure the charging system causes it when plugged in but not about the first boot stuff or when it's not charging.
Thank you aicjofs for your answer,
yes, I did attempt to repair the system, data, cache and it was successfully. I did it several times. I also wiped everything a few times and installed the Nabixus ROM afterwards. Nothing helped. It's like the operating system needs to "get warm" somehow, because I have to try to power on the system many times, until I get it work... but after that, if the Nabi goes in standby, I have to start the whole thing over
How can I check for damaged blocks, etc.? If I can do it and find some, could they be marked as "bad" and isolated? Would it make sense?
Dear Sir/Mdm,
This is Linn Myanmar and I am from Myanmar, Stayed in Singapore, working as an engineer.
I just bought my phone (Elephone S8) one week before and I tired rooting with tutorials from XDA forum (using flash tool, driver).
Yes, the phone has been rooted properly as root checker said and I tried installing Updated SuperSU from setting>About Phone>System Update>Local Updates>Updated SuperSU.zip.
After that the phone has rebooting with logo and never show any result and the phone just happened the screen on and off repeatedly until now.
So that please help me how to solve this and get back to its normal operation. I've tried long pressing on power button, long pressing on power button+volume up button, long pressing on power button+volume up button+volume down button quite many time, but those doesn't work and the phone hasn't come back it's normal operation.
Help me please.
With Best Regards,
Linn Myanmar
Linn Myanmar said:
Dear Sir/Mdm,
This is Linn Myanmar and I am from Myanmar, Stayed in Singapore, working as an engineer.
I just bought my phone (Elephone S8) one week before and I tired rooting with tutorials from XDA forum (using flash tool, driver).
Yes, the phone has been rooted properly as root checker said and I tried installing Updated SuperSU from setting>About Phone>System Update>Local Updates>Updated SuperSU.zip.
After that the phone has rebooting with logo and never show any result and the phone just happened the screen on and off repeatedly until now.
So that please help me how to solve this and get back to its normal operation. I've tried long pressing on power button, long pressing on power button+volume up button, long pressing on power button+volume up button+volume down button quite many time, but those doesn't work and the phone hasn't come back it's normal operation.
Help me please.
With Best Regards,
Linn Myanmar
Click to expand...
Click to collapse
Hi Linn
How did you solve your problem?
Hi have exactly the same problem at this moment and, as you, I tried everything (except the hammer but it was close...)
Really need a solution for this!
I like the phone but this way I have to buy another one and other brand for sure...
Thanks (from Portugal)
I suppose you both solved this, one war or other, but maybe someone else looks for a solution to this.
As the S8 is a MTK-phone, it's never really "dead" until it's defective. You can always revive it. So stay cool.
All you need is a Windows-PC with working VCOM-drivers, the SP-Flash-Tool and a ROM. You can get all that on www.elephone.hk/downloads (at least until today... if it's no longer there, you need to google for all that).
The problem is to shut the phone off.
Of course you can just let it boot-loop until the battery is empty, if you can take the time.
Otherwise there's no simple and foolproof way to shut it off if it's in loop.
Try everything you can imagine with the three buttons. Especially pressing the power-button for "ages". Try pressing any volume-button simultaneously, too. I had my S8 bricked to bootloop several times yesterday and today, while fiddling around with all ROMs I could find.
Sooner or later I got the phone to shut off. I somehow got it into the testing-menu, too, which is yellow and chinese and which won't help you.
I even somehow managed to boot into recovery several times, which offers "shutdown"-option. I have the impression that the S8 enters recovery eventually when it fails to boot often enough, but that's just a guess.
Anyway, once the phone is off, you have won.
Start the SP-Flash-Tool, load the scatter-file from your desired ROM (which is probably 20171018), unplug the phone, press "download", and then plug the phone to USB. You might have to press vol+ oder vol- while plugging it in, but if it's recognized, the SP Flash Tool will start flashing the ROM and your phone is up and running again.
Problem solved
I think this is too complex anyway.
The battery was empty after some days.
It was too bad lose so many information but I had to live with that.
So, finally the hammer solve the problem in less then a second...
Thank you very much. Is nice to know there are people helping to solve some problems.
Amorinix
Please also find all required files for rooting the Elephone S8 at:
https://www.mediafire.com/file/k1ldc..._root.rar/file
I hope this helps.
To turn phone off, hold all 3 buttons for about 15 seconds the phone will look like it's powering down but then restart after about 2 seconds just KEEP holding all 3 buttons and it will power off properly. In other words hold all 3 buttons for about 45 secs to power down if in a boot loop. Once powered down hold volume down whilst plugging into USB to flash.
Noticed quite a few threads re this, have had the prob myself.
Found a simple fix, while trying different things...
Hold ALL buttons down at once (vol dn + vol up + pwr button). Keep them held down for about a min or two. Phone will respond and you'll be able to shut it off. It takes a while to respond.
Cheers
Thank you!
I've added this to the US998 Pie KDZ thread. That KDZ is very wonky. It's the only Pie people have problems flashing. Probably because LG has not yet released Open Market US998 and the one we are using is technically for U.S. Cellular US998.
I had no trouble flashing it myself -- on my backup V30+(former LS998) going straight from Nougat (never updated, it was my backup phone) to Pie through Dev Patched LGUP Refurbish mode. But lots of other people seem to have problems.
On my daily phone, I'm still on rooted stock Oreo with Magisk and Xposed mods.
AsItLies said:
Noticed quite a few threads re this, have had the prob myself.
Found a simple fix, while trying different things...
Hold ALL buttons down at once (vol dn + vol up + pwr button). Keep them held down for about a min or two. Phone will respond and you'll be able to shut it off. It takes a while to respond.
Cheers
Click to expand...
Click to collapse
Hi, @AsItLies, I have tried but my phone still keeps bootloop, so could you please describe it more detailed? Can you enter fastboot or rec then? If possible, please come to see this: Help! bootloop per 5 sec, cannot enter rec, download or fastboot
zacox123 said:
Hi, @AsItLies, I have tried but my phone still keeps bootloop, so could you please describe it more detailed? Can you enter fastboot or rec then? If possible, please come to see this: Help! bootloop per 5 sec, cannot enter rec, download or fastboot
Click to expand...
Click to collapse
I think it's pretty clear, what I did and it worked in my situation(s):
There are 3 buttons right? Vol up, Vol dwn, and pwr.
Press all 3, at the same time, keep them pressed until the phone responds. It can take quite a while.
The last time I used this was after flashing LOS17, but then flashed a 19.x version of Magisk... (that's the wrong version of Magisk for Q Roms btw), resulting in phone stuck on boot logo, wouldn't budge.
I honestly have never tested exactly 'how long' it takes to respond, just that it does eventually respond and are then able to get to recovery etc. I can say time wise, if you hold them down and no response after a few minutes, then it's probably not going to work in your situation.
good luck
AsItLies said:
I think it's pretty clear, what I did and it worked in my situation(s):
There are 3 buttons right? Vol up, Vol dwn, and pwr.
Press all 3, at the same time, keep them pressed until the phone responds. It can take quite a while.
The last time I used this was after flashing LOS17, but then flashed a 19.x version of Magisk... (that's the wrong version of Magisk for Q Roms btw), resulting in phone stuck on boot logo, wouldn't budge.
I honestly have never tested exactly 'how long' it takes to respond, just that it does eventually respond and are then able to get to recovery etc. I can say time wise, if you hold them down and no response after a few minutes, then it's probably not going to work in your situation.
good luck
Click to expand...
Click to collapse
Oh, I'm just a little confused if you are talking about powering off/shutting down the phone entirely or instead changing the status of logo sticking and then shutting off with extra operation. My phone was suffering automatic reboot per 5 second, so I cannot recognize any other response than that. Thanks for your patience, but I just want to know something more to see if this method works when the phone is almost bricked. It seems you could enter rec or at least download mode, so maybe you had performed force reboot.
Hope further confirmation.
zacox123 said:
Oh, I'm just a little confused if you are talking about powering off/shutting down the phone entirely or instead changing the status of logo sticking and then shutting off with extra operation. My phone was suffering automatic reboot per 5 second, so I cannot recognize any other response than that. Thanks for your patience, but I just want to know something more to see if this method works when the phone is almost bricked. It seems you could enter rec or at least download mode, so maybe you had performed force reboot.
Hope further confirmation.
Click to expand...
Click to collapse
Hmmm I think you may be over thinking this a bit. All that happens (for me) is the phone responds (it gets out of the loop). Then, do whatever you want (shut down, recovery, etc etc).
I wouldn't suggest trying to reboot system again, as you already know that won't work...
All I can say is, if you tried the above and held the buttons, and nothing happened, then I don't know what else you can do. Sorry. Hopefully you can find a way.
Just in case someone is having problems entering download mode while in this bootloop, I'll explain how I applied AsltLies method:
First I held all buttons at the same time, no matter how many times the phone restarted, I still held them
After a while, a white screen with the MEID or IMEI info showed up, this is when the phone stopped bootlooping and I released the buttons.
Then, I CONNECTED the phone to the pc, after that I held VOL UP+POWER BUTTON, this would make the screen go black eventually, and when that happened, I inmediately released the power button but not the VOL UP button, and the phone entered into fully working download mode.
I hope this helps someone.
Dr_Roo said:
Just in case someone is having problems entering download mode while in this bootloop, I'll explain how I applied AsltLies method:
First I held all buttons at the same time, no matter how many times the phone restarted, I still held them
After a while, a white screen with the MEID or IMEI info showed up, this is when the phone stopped bootlooping and I released the buttons.
Then, I CONNECTED the phone to the pc, after that I held VOL UP+POWER BUTTON, this would make the screen go black eventually, and when that happened, I inmediately released the power button but not the VOL UP button, and the phone entered into fully working download mode.
I hope this helps someone.
Click to expand...
Click to collapse
Thanks. Added your notes to the Recovery Post in US998 Pie KDZ thread.
https://forum.xda-developers.com/showpost.php?p=81728547&postcount=641
dr_roo said:
just in case someone is having problems entering download mode while in this bootloop, i'll explain how i applied asltlies method:
First i held all buttons at the same time, no matter how many times the phone restarted, i still held them
after a while, a white screen with the meid or imei info showed up, this is when the phone stopped bootlooping and i released the buttons.
Then, i connected the phone to the pc, after that i held vol up+power button, this would make the screen go black eventually, and when that happened, i inmediately released the power button but not the vol up button, and the phone entered into fully working download mode.
I hope this helps someone.
Click to expand...
Click to collapse
thank you so much omg lifesafer
Facts:
- Pocophone F1 is in an endless boot loop. Every 8 seconds it reboots itself.
- Recovery mode and Fastboot are reachable, but this doesn't stop the boot loop.
- I have never used a custom rom
- The bootloader is unlocked (ADB confirms this), USB debugging is enabled, but OEM unlocking is NOT enabled.
History:
The problems started after a regular update (I had never put a custom rom on the phone). The phone became unstable, constantly restarting itself. Sometimes restarting quickly, sometimes after a few minutes (reaching Android). I tried to unlock the bootloader, by tapping 7 times on MIUI Version, enabling USB Debugging [I did not enable OEM unlocking unfortunately...] and run the flashtool. The flashtool reported that the phone was unlocked. And after restarting, the phone reports to be unlocked. ADB confirms this too. But after unlocking the phone, it never ever again reached to Android, restarting itself always after exactly 8-9 seconds. I can get into recovery mode and fastboot, but it will still restart. In Fastboot, my pc recognizes the phone as an Android Phone. Is there a magical way to get out of this loop?
Similar thing happened to twice. My power button was kinda stuck (not noticeable to eyes thoughts). Flicking onto the power button real hard solved the issue.
lockhrt999 said:
Similar thing happened to twice. My power button was kinda stuck (not noticeable to eyes thoughts). Flicking onto the power button real hard solved the issue.
Click to expand...
Click to collapse
The problem persist when I completely remove the connector of the power/ volume button... When I push the power button I feel that the button moves and I hear a click-sound. Something else must be the cause of the problem. But still thanks for your help.
i have the same issue, did you find any solution to the problem?
Have the same problem is there any solution?
I don't have the phone so I cannot say this will solve the issue, however this sounds like a problem with the battery, something similar happened to my Redmi Go. The voltage should be low enough that the system boots, but just as it starts up the voltage drops to the point it reboots.
Solved it!!
I have Played with the power button and press it several times and it help.
I think the button was stuck or something close to that.
Thanks for you help guys!
ozer86 said:
Facts:
- Pocophone F1 is in an endless boot loop. Every 8 seconds it reboots itself.
- Recovery mode and Fastboot are reachable, but this doesn't stop the boot loop.
- I have never used a custom rom
- The bootloader is unlocked (ADB confirms this), USB debugging is enabled, but OEM unlocking is NOT enabled.
History:
The problems started after a regular update (I had never put a custom rom on the phone). The phone became unstable, constantly restarting itself. Sometimes restarting quickly, sometimes after a few minutes (reaching Android). I tried to unlock the bootloader, by tapping 7 times on MIUI Version, enabling USB Debugging [I did not enable OEM unlocking unfortunately...] and run the flashtool. The flashtool reported that the phone was unlocked. And after restarting, the phone reports to be unlocked. ADB confirms this too. But after unlocking the phone, it never ever again reached to Android, restarting itself always after exactly 8-9 seconds. I can get into recovery mode and fastboot, but it will still restart. In Fastboot, my pc recognizes the phone as an Android Phone. Is there a magical way to get out of this loop?
Click to expand...
Click to collapse
Chance 1: Power button bug
Chance 2: EMMC failed and your phone is long gone.
lockhrt999 said:
Similar thing happened to twice. My power button was kinda stuck (not noticeable to eyes thoughts). Flicking onto the power button real hard solved the issue.
Click to expand...
Click to collapse
Thank you! This was the issue. There is no way to tell that the power button is stuck. But it is and was causing my Poco F1 to bootloop even in fastboot or recovery mode. A symptom to look out for: your phone randomly locking once in a while due to this.
mateuxi said:
I don't have the phone so I cannot say this will solve the issue, however this sounds like a problem with the battery, something similar happened to my Redmi Go. The voltage should be low enough that the system boots, but just as it starts up the voltage drops to the point it reboots.
Click to expand...
Click to collapse
i booted in TWRP for 8-9 minutes with full brightness & no timeout but then mine didn't go into bootloop... recovery's getting powered but OS isnt?
Same thing happened to my F1, I press and flicked my power button hard and it worked. My problem happened maybe because the hard cover pushing the button too tight because it sometimes lock it self. Thank you for the tips! Just made account to reply to this thread.