Related
hello!
Can anyone help me with this:
after 5 or 10 minutes, or even at the splash screen, my device automatically restarts and does it for several times.
When i try to put it into bootloader mode i see usb,..... but only for a minute. after that it goes out of bootloader mode and starts the OS again...
So i'm a bit worried that when i flash it, the bootloader mode will go out and the device will try to restart.
Any known sollutions to this problem? Any help would be appreciated!!
ps: no answers in the wiki nor in the forum.
thanks in advance to your replies!!!!!
xmrjx said:
hello!
Can anyone help me with this:
after 5 or 10 minutes, or even at the splash screen, my device automatically restarts and does it for several times.
When i try to put it into bootloader mode i see usb,..... but only for a minute. after that it goes out of bootloader mode and starts the OS again...
So i'm a bit worried that when i flash it, the bootloader mode will go out and the device will try to restart.
Any known sollutions to this problem? Any help would be appreciated!!
ps: no answers in the wiki nor in the forum.
thanks in advance to your replies!!!!!
Click to expand...
Click to collapse
wrong forum, but ok.
does it happen when you plug in the wall charger (not a computer)?
shlomki said:
wrong forum, but ok.
does it happen when you plug in the wall charger (not a computer)?
Click to expand...
Click to collapse
Yes... sometimes it sticks 20 min before restarting, somtimes it restarts 10 times before getting on today screen....
Would you know how to fix this? and better: what caused this ?
xmrjx said:
Yes... sometimes it sticks 20 min before restarting, somtimes it restarts 10 times before getting on today screen....
Would you know how to fix this? and better: what caused this ?
Click to expand...
Click to collapse
Can you try a different battery ?
or at least take it out, clean the contacts and try again.
greetings,
Wout
wout said:
Can you try a different battery ?
or at least take it out, clean the contacts and try again.
greetings,
Wout
Click to expand...
Click to collapse
didn't work.....
i'm almost sure it is a software issue... I just got it back 2 weeks ago from the repair centre and i got all new hardware....
I started flashing it because the bastards repaired it and putted on a French ROM and an AZERTY keyboard.... i can send it back but i don't want to miss my precious phone another 6 weeks
if i get it fixed now, i stop "messing" with it ;-)
Hehe...
I sent it back to the repair shop. They can fix it since bootloader mode also restarts it must be a hardware problem...
Last time they sent it back with AZERTY and French ROM so they can fix that to!!
Thx anyway for replying!
I think i bricked my sensation cus i turned it off and it dont turn back on it wasnt dead when i was flashing a rom??
It dont want to do anything not even go into recovery at all what do i do?
LOL WHOA...
stop freaking out lol do your self a favor
what had you done before you turned it off? (flash a rom? flash a mod? flash anything? drop it in water lol?)
give some info lets see if we can help. you probably just need to boot into recovery and reboot
bord1er said:
I think i bricked my sensation cus i turned it off and it dont turn back on it wasnt dead when i was flashing a rom??
It dont want to do anything not even go into recovery at all what do i do?
Click to expand...
Click to collapse
Battery Dead ? Plug It In
Did you Pull That Battery ? Wait A Few Minutes And Then Try to turn it on ?
rddocke said:
LOL WHOA...
stop freaking out lol do your self a favor
what had you done before you turned it off? (flash a rom? flash a mod? flash anything? drop it in water lol?)
give some info lets see if we can help. you probably just need to boot into recovery and reboot
Click to expand...
Click to collapse
check it out i flashed a rom right and it didnt want to boot into recovery so i took the battery out and it never turned on again????
Plug it in let it charge a bit. If the orange light blinks four times and turns off, then you need to do a battery swap.
If it charges then let it charge boot unto recovery and restore your backup. I hope you made a backup.
Which Rom were you flashing?
rddocke said:
Plug it in let it charge a bit. If the orange light blinks four times and turns off, then you need to do a battery swap.
If it charges then let it charge boot unto recovery and restore your backup. I hope you made a backup.
Which Rom were you flashing?
Click to expand...
Click to collapse
nothing comes on
Mate, you're really not helping yourself here. Can you please give a step-by-step of what you were trying to do and a bit more information as to what happened when it didn't go to plan?
e.g. I was trying to flash a new ROM. The ROM update completed successfully but upon rebooting it wouldn't turn on.
The above example gives a bit more insight as to the situation
EddyOS said:
Mate, you're really not helping yourself here. Can you please give a step-by-step of what you were trying to do and a bit more information as to what happened when it didn't go to plan?
e.g. I was trying to flash a new ROM. The ROM update completed successfully but upon rebooting it wouldn't turn on.
The above example gives a bit more insight as to the situation
Click to expand...
Click to collapse
this is what i happend i flash a 3.5 sense rom on my sensation it didnt get any signal so i tryed to go into recovery threw rom manager and it didnt want to so i took the battery out and put it back in and it never turned on from their nothing turns on not the charging light or anything
and no it wasnt dead when i tryed so its not the battery
bord1er said:
this is what i happend i flash a 3.5 sense rom on my sensation it didnt get any signal so i tryed to go into recovery threw rom manager and it didnt want to so i took the battery out and put it back in and it never turned on from their nothing turns on not the charging light or anything
and no it wasnt dead when i tryed so its not the battery
Click to expand...
Click to collapse
Pop the battery out for about 10 minutes then put it back in and try charging the battery. Also try charging from a different power source like an AC adapter or via your computers USB port. If the battery light doesn't come on then your battery is most likely dead and you may need to find a replacement.
bord1er said:
this is what i happend i flash a 3.5 sense rom on my sensation it didnt get any signal so i tryed to go into recovery threw rom manager and it didnt want to so i took the battery out and put it back in and it never turned on from their nothing turns on not the charging light or anything
and no it wasnt dead when i tryed so its not the battery
Click to expand...
Click to collapse
you said you didnt get any signal. dude you prolly didnt flashed the correct radios. some roms tells you witch radio you need before flashing the rom. not all the roms have the correct radios due of a lot of sensation worldwide. had you tried to go into fastboot at all by holding power and vol down at the same time.
Aegishua said:
Pop the battery out for about 10 minutes then put it back in and try charging the battery. Also try charging from a different power source like an AC adapter or via your computers USB port. If the battery light doesn't come on then your battery is most likely dead and you may need to find a replacement.
Click to expand...
Click to collapse
Yes battery swap as I mentioned.
On a side note
Can anyone tell me why that is the only solution to the problem when the phone dies down like this
Thisy wife let's her phone die alllll the time and I constantly have to swap mine and her battery.
I flashed the JB ROM on my Tab 7 Plus. After the "succeess" of the flashing as said by Odin v1.85, I tried to turn on the device, but it didn't. I tried to access download mode or recovery mode but it didn't work either. I tried to hold the volume down button and connect the cable to the tablet. That opened the download mode but the screen was "flashing". The rate at which the screen "flashes" keeps increasing until it becomes very fast and the device turns off. I tried to flash a ROM, but Unfortunately it turns off fast that there will be no time for the flashing process to continue.
Any idea what should I do?
what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....
Reply
chrisrotolo said:
what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....
Click to expand...
Click to collapse
My Device is GT-P6200 and I got the GT-P6200 JB ROM for it.
______________
I left my device to charge all night. When I woke up I tried to see if the 'flashing' of the screen still occurs, but it didn't happen. I think I can flash a ROM now
I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?
yes, also a faulty or non-OEM cable would be the culprit.
SudoHalt said:
I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?
Click to expand...
Click to collapse
yess. flashing(blinking) screen is how download mode tells you that your battery is low. probably less than 10% since it even turned off by itself.
This Happend To me and I got it BACK
Hello... I totally understand your frustration... This exact same thing happened to me after my battery went dead just after I installed JB...
well here is the kick and it's kind of tricky...
If you want you can call me and I can tell you the instructions, it's complicated but if you follow the steps it will work...
I can also take the time to write it down, but i'm bad a typing.
let me know if you are interested...
Sorry for the late reply. It was fixed after less than a day from starting this thread.
Sent from my GT-I9001 using xda app-developers app
Hi, i have been looking for answers on the forum, and i learn new things but not how to fix this or what is causing it.
I have buyed i997 from a reseller. He sayd it doesnt work because it have bootloop, but i thinks that is not too much problem getting it working again, so i started searching for the pc drivers n software, then i find here in the forum the stock rom with and without root, i tested them both with odin and the bootloop stills present. I wipe cache and do a factory reset but it keep bootlooping, then think maybe if i update to latest AT&T rom, but no luck.Sometimes the phone just start and theres no bootloop but its very rare and most of the time when i get to the lock screen or setup manager suddently a gapps or something crash and my phome freezes and reboot. I flashed the carbon-jb-v1.6 and suddently it worked fine, no more bootloop and everything smooth,no crashes etc.. then i installed Facebook app and when i was ttyping a message the phone froze up and then restarts, and the bootloop came again, and im stuck on it, and when i pass it, which is very rare, i start typing info in the startup manager and the phone freezes and reboot.. I wipe/format cache, dalvik, factory reset, formated system and data before and after flashing the carbon rom again and it keeps bootlooping. Somebody have similar problems or know how to fix it?
Thanks
P.d. sorry for my bad english.
jakov.90 said:
Hi, i have been looking for answers on the forum, and i learn new things but not how to fix this or what is causing it.
I have buyed i997 from a reseller. He sayd it doesnt work because it have bootloop, but i thinks that is not too much problem getting it working again, so i started searching for the pc drivers n software, then i find here in the forum the stock rom with and without root, i tested them both with odin and the bootloop stills present. I wipe cache and do a factory reset but it keep bootlooping, then think maybe if i update to latest AT&T rom, but no luck.Sometimes the phone just start and theres no bootloop but its very rare and most of the time when i get to the lock screen or setup manager suddently a gapps or something crash and my phome freezes and reboot. I flashed the carbon-jb-v1.6 and suddently it worked fine, no more bootloop and everything smooth,no crashes etc.. then i installed Facebook app and when i was ttyping a message the phone froze up and then restarts, and the bootloop came again, and im stuck on it, and when i pass it, which is very rare, i start typing info in the startup manager and the phone freezes and reboot.. I wipe/format cache, dalvik, factory reset, formated system and data before and after flashing the carbon rom again and it keeps bootlooping. Somebody have similar problems or know how to fix it?
Thanks
P.d. sorry for my bad english.
Click to expand...
Click to collapse
the most inexpensive solution:
http://forum.xda-developers.com/showthread.php?t=1912599
qkster said:
the most inexpensive solution:
http://forum.xda-developers.com/showthread.php?t=1912599
Click to expand...
Click to collapse
Thanks man, but you think it can be the power button? When i unplug the battery and put it again the phone doesnt turn on or something, and when it boot up when i lock the screen with the power button it works fine. I set the cpu governor to conservative and since yesterday i didnt have any problem, but sometimes the phone reboots when typing, i think its someting with the processor or when the phone have little ram or something.
Thanks.
jakov.90 said:
Thanks man, but you think it can be the power button? When i unplug the battery and put it again the phone doesnt turn on or something, and when it boot up when i lock the screen with the power button it works fine. I set the cpu governor to conservative and since yesterday i didnt have any problem, but sometimes the phone reboots when typing, i think its someting with the processor or when the phone have little ram or something.
Thanks.
Click to expand...
Click to collapse
If you ran the phone on complete stock GB or FROYO and you are getting boot loops, it may be a hardware issue.
One of the few things that will give you boot loop with the samsung logo while using the phone is the power button.
Either way, it's no big deal to open it and clean it up to see if the problem goes away.
qkster said:
If you ran the phone on complete stock GB or FROYO and you are getting boot loops, it may be a hardware issue.
One of the few things that will give you boot loop with the samsung logo while using the phone is the power button.
Either way, it's no big deal to open it and clean it up to see if the problem goes away.
Click to expand...
Click to collapse
Thanks bud, I will try cleaning the button. Also I want to ask, is there something to log everything when the phone start? Or something to test the hardware functionality?
Thank you for your time
post number #112
http://forum.xda-developers.com/showthread.php?t=1437548&page=13
qkster said:
post number #112
http://forum.xda-developers.com/showthread.php?t=1437548&page=13
Click to expand...
Click to collapse
Thank you, the post its the number #122
jakov.90 said:
Thanks bud, I will try cleaning the button. Also I want to ask, is there something to log everything when the phone start? Or something to test the hardware functionality?
Thank you for your time
Click to expand...
Click to collapse
Bootlog Uptime will keep a record of all boots from an Android OS perspective ... It will also track crashes... It won't track events outside of a complete restart (i.e. power button bootloops.. But those are pretty obvious when they occur)
For hardware testing, try Z Device Test... That won't tell you about the buttons though... If your screen turns on without pressing power button or from any other standard event (like receiving a text or a phone call), or the phone restarts by itself, time to get cleaning..
Sent from my SAMSUNG-SGH-I997 using xda premium
Zen Arcade said:
Bootlog Uptime will keep a record of all boots from an Android OS perspective ... It will also track crashes... It won't track events outside of a complete restart (i.e. power button bootloops.. But those are pretty obvious when they occur)
For hardware testing, try Z Device Test... That won't tell you about the buttons though... If your screen turns on without pressing power button or from any other standard event (like receiving a text or a phone call), or the phone restarts by itself, time to get cleaning..
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Hey thanks, that was very useful.. i risky miself to do a stock flrom flashing with pit checking the Nand erase all option in Odin 3.07, and the random reboots are gone :laugh:. Now i have one question, Do i need an special kernel for JB 4.2.2? i plan to flash the Carbon-jb-v1.6 rom but i dont know if i need another kernel
I'm glad to hear you solved your issue.
For JB, use the kernel provided with the rom.
Sent from my SAMSUNG-SGH-I997 using xda premium
Hi,
I own a Motorola Moto E XT1022 (1st gen), which I bought from Flipkart India.
It came with KitKat 4.4.4, and I had put a soak test version of android L 5.0.2 , officially released by Motorola in May or something.
It worked fine until December 2015- then it started having issues. It would lock its screen automatically. When pressed the power button, it will show the screen that was on before locking. When touched, it will make me type the password. After typing it, it would work fine. Same thing would happen after 30 min. But that was not a big issue.
3-4 days after facing this issue, it restarted automatically. And it stuck on the Motorola M logo.
I shut it down, tried starting it again. No luck. One time, it started. I immediately performed a factory reset by going in settings. At that time, the soft keys (back, home and recent apps) didnt appear on the screen. That was strange. After factory reset, it restarted itself. Started working normally, all clean phone. (Still on 5.0.2 soak test obviously) But it didnt show the soft keys as I said before.
Then it restarted, again. And since then it is stuck in boot loops. I stormed the internet, and found how to factory reset using recovery, wipe data, even flash stock OS 4.4.4 from official Motorola website. I have done all that. I have-
1) Factory reseted using hard reset method
2) Wiped Cache partition
3) Flashed stock firmware from official website (KitKat 4.4.4)
It is still stuck in boot loops. It shows the M logo at startup, and stays like that forever. Only shuts down when all battery is drained. Now it is not charging either. It is stuck at 0%. But I think charging issue will be fixed by charging it for some hours.
Now, the phone is running stock OS, is completely cleaned, and is stuck in boot loops.
I cannot afford to buy another phone. When I asked Motorola for help using the Chat function of the Help app, they suggested me showing it to the closest service centre. I showed it to them but they were giving excuses that they will see if they can do...and didnt do anything. (PS I'm from India, and it is like this for most of the service centres here.)
So please, can anyone, please please please help me?
All the help is appreciated. Thank you!
PS. I have tried hard reset and wiping cache partition over 8 times now. It's still not working. Please suggest some other method if possible.
I guess it is because of the faulty soak test ROM.. Would you be interested in rooting? I guess flashing a different stable ROM would help.. Even a factory image..
WickedCool19 said:
I guess it is because of the faulty soak test ROM.. Would you be interested in rooting? I guess flashing a different stable ROM would help.. Even a factory image..
Click to expand...
Click to collapse
Sir,
I am ready to do anything to make it work. If rooting is the solution, or maybe flashing a different OS, or both, I am ready to do anything.
Please tell me what should I do next.
Thank you for your valuable reply!
Alright .. First of all, can you access your phone right now? I mean, does it actually boot up?
Hit thanks if I helped!
WickedCool19 said:
Alright .. First of all, can you access your phone right now? I mean, does it actually boot up?
Click to expand...
Click to collapse
Here is the current state of my phone-
It is completely out of charge.
When I charge it, after about ten minutes or so, it shows a symbol of pulling the wire out of the socket.
First time when I saw this, I switched off charging and pulled it off. Then the phone shut down as it had no charge.
Second time when I saw this symbol, I kept it charging. After 30 minutes, it showed the battery charging symbol, with 0%.
And I forgot to mention one thing. When I plugged in the charger and started charging the phone, the LED notification light glowed and it stayed on. No idea why. After some time, it stopped glowing. Battery showed 0% even after charging for about an hour. ( Note- LED notification light glowed up and went out randomly.)
( Then I got depressed and stopped charging the phone. Then it switched off as it didnt have any charge.)
Now, I think charging it for a long time will make it start again.
But I think I will get into boot loops after I start the phone. And it will stay like that until the battery is drained out completely.
Thank you!
PS. Should I start charging it right now? Its 12 midnight here, maybe I should keep it overnight. (Is it safe? The battery won't explode or anything right? Sorry I'm a little paranoid, since my uncle's micromax phone burst while charging.)
Same time zone
Now look this happens in my moto e too.. There was an issue with my power button, it restarted when ever i unlocked or locked my device.. I rooted, flashed a kernel which supports gesture wake and now i use the button rarely..
Now coming to ur problem, don't charge it overnight, might harm the battery at the most.. Charge it for an hour.. And try to boot the device up.. Only then, can i help you out..
WickedCool19 said:
Alright .. First of all, can you access your phone right now? I mean, does it actually boot up?
Hit thanks if I helped!
Click to expand...
Click to collapse
Its midnight. I have to sleep. But I will reply to your posts as soon as I wake up.
(Just telling this in case if you wonder why am I not replying. I actually have to log off now. I will reply tomorrow. Please do not close this thread. Thanks and sorry too. Good night from India! I appreciate your help!)
WickedCool19 said:
Same time zone
Now look this happens in my moto e too.. There was an issue with my power button, it restarted when ever i unlocked or locked my device.. I rooted, flashed a kernel which supports gesture wake and now i use the button rarely..
Now coming to ur problem, don't charge it overnight, might harm the battery at the most.. Charge it for an hour.. And try to boot the device up.. Only then, can i help you out..
Click to expand...
Click to collapse
Ok, I will charge it when I wake up tomorrow. It might not get enough charge in 1 hour, so I may have to charge it for 2-4 hours to start it. Thank you for your kind help! We will talk tomorrow. Good night!
PhantomCode31 said:
Ok, I will charge it when I wake up tomorrow. It might not get enough charge in 1 hour, so I may have to charge it for 2-4 hours to start it. Thank you for your kind help! We will talk tomorrow. Good night!
Click to expand...
Click to collapse
Charge it.. One hour just might do it..
What ever you do.. Just try to boot it up or else i might not be able to help you..
Cheers..
How can root
WickedCool19 said:
Charge it.. One hour just might do it..
What ever you do.. Just try to boot it up or else i might not be able to help you..
Cheers..
Click to expand...
Click to collapse
Hi.
I have started charging the phone just now. Let's see how much it charges after an hour.
Right now its LED Notification light is blinking randomly, and battery charging 0% symbol is showing up on start screen.
The screen wakes up and sleeps randomly. Lets see what happens.
WickedCool19 said:
Charge it.. One hour just might do it..
What ever you do.. Just try to boot it up or else i might not be able to help you..
Cheers..
Click to expand...
Click to collapse
Hi,
I have charged the phone for about an hour. Its still charging.
It now shows the recovery menu, giving me options such as
Normal Powerup
Recovery
Factory etc.
And under all the options, this is what I see-
hab check failed to boot
failed to validate boot image
Fastboot Reason: Fall-through from not-charger boot
ode
What do I do now? I tried Normal Powerup, it showed M logo and showed the above screen again.
PLEASE REPLY URGENTLY. Thanks
<<UPDATE>>
Phone is charging. About 28% battery right now and still charging normally.
Now should I try starting it? Please reply.
Yes.. Try starting it. Or else nothing can be done..
WickedCool19 said:
Yes.. Try starting it. Or else nothing can be done..
Click to expand...
Click to collapse
When I start it, its no longer in a boot loop.
It shows Motorola M logo for a second and automatically opens recovery mode.
there I get this message at the bottom (in pink or some color like that)
hab check failed for boot
failed to validate boot image
(in yellow/green color) Fastboot Reason: Fall-through from normal boot mode
A question.. Had u enabled usb debugging from dev settings by any chance?
WickedCool19 said:
A question.. Had u enabled usb debugging from dev settings by any chance?
Click to expand...
Click to collapse
When this issue started, I had soak test android L 5.0.2, and yes I had enabled USB Debugging from it.
But, after the issue, I flashed stock rom 4.4.4 on it. But I havent been able to access the phone normally since that. So I had it enabled in 5.0.2, but now it has 4.4.4, which I never operated.
Hope I didnt confuse.
PhantomCode31 said:
When this issue started, I had soak test android L 5.0.2, and yes I had enabled USB Debugging from it.
But, after the issue, I flashed stock rom 4.4.4 on it. But I havent been able to access the phone normally since that. So I had it enabled in 5.0.2, but now it has 4.4.4, which I never operated.
Hope I didnt confuse.
Click to expand...
Click to collapse
How did u flash? Using recovery?
WickedCool19 said:
How did u flash? Using recovery?
Click to expand...
Click to collapse
I shut down the phone.
Connected to laptop.
Hold down the power and volume key.
Factory Reseted using recovery menu.
I had official kitkat 4.4.4 ROM in laptop.
I flashed it using command prompt.
Now im sure it has kitkat, the word "Android" at boot animation has changed, like it did on kitkat.
So I'm sure it has KitKat.
<<UPDATE>>
Phone is not stuck in boot loops anymore.
It switches off, I can stop the draining of the battery.
When I turn it on, it shows motorola M logo for 1 second.
Then it takes me automatically to recovery mode. And gives the hab error as I mentioned above.
So you do know how to flash using ADB...
---------- Post added at 03:52 PM ---------- Previous post was at 03:45 PM ----------
Then just get on with it..
Here's a link of cm 12.1.. Download a zip and flash using ADB (as you did from Command prompt for kitkat)
---------- Post added at 03:55 PM ---------- Previous post was at 03:52 PM ----------
http://download.cyanogenmod.org/?device=condor