Database Users

[Q] Problem to start my phone

Hello!
Have problems with my wonderful phone.
Starting with that I'm running custom ROMs, cm-10.1-20130813-NIGHTLY-find5 right now with TWRP recovery.
Now to my problem, if I turn off my phone to switch software, for example, so I start and keep the volume down.
Oppo logo pops up, then nothing happens.
If I shut down and restart my phone, it becomes the same thing, it is stationary on Oppo logo agian.
Waiting 10 minutes, my phone starts without any problem and CM10.1 logon turns up.
I have managed to update my phone and get into recovery.
Have both updated TWRP and CM10.1 to last.
Why does this happen? how do I solve the problem?
Is terrified of running out of battery or update right now.
Grateful for help!

When you reboot the phone don't hold down volume down, if that's what your doing. Download the the latest software for the Find 5 here: http://www.oppoforums.com/index.php?threads/4872/
Reboot to recovery and flash making sure to perform a full wipe. Instructions on how to update are in the OP of the thread linked above.
Sent from my X909 using Tapatalk 4 Beta

probably need another recovery:
http://forum.xda-developers.com/showpost.php?p=44285454&postcount=677

New/Stock Oneplus Two, unable to boot into recovery

Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!

redbay1 said:
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
Click to expand...
Click to collapse
That is the norm for fastboot, it doesn't go past that screen.
It may not make a difference, did you try to boot to recovery via Power+Volume Down buttons?

Greetings Khaos64,
Yes, I've tried booting with Vol-Down+Power but the phone does not start.
With volume-up+power, I get the Fastboot splash screen but the phone does not respond to any input.
I tried selecting "bootloader" from the reboot menu but I get the same thing: Reboots and after a second, the phone reboots again normaly and into OxygenOS.
Is there a way to verify if the bootloader or recovery is corrupt and maybe reflash the stock recovery onto the phone?
Thanks for your input!

You may just want to go straight to oneplus support since everything is stock and only 2 weeks they should be able to get you updated or replace it.
If you'd like to be more hands on... maybe something below can help.
So your phone isn't recognized/no commands acceptred from your computer when booted to fastboot?
Such as unlocking your bootloader and booting into twrp... "fastboot boot yourfilename.img" or maybe flashing it.
Make sure OEM unlocking is selected in Developer options.
If you can't do that then this may not work but is worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
These may also be something to look into:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449

I did try to contact Oneplus for support but I am not the one who purchased the phone. Long story short, it was a gift from my girlfriend that she bought off of someone. The phone was new in box and was a warranty replacement. I would have to contact the seller and go trough him for support unfortunately.
Thanks for the different suggestions!, I will fiddle around with it this afternoon while the kids are having their mid-day nap and I'll get back with the results
Thanks again for the help, it's greatly appreciated!

Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue

Congratulations hope you enjoy the phone
Sent from my ONE A2005 using Tapatalk

redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
Glad one was able to help you do it. :good:

redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
HI there,
I am having the exact same issue with my oneplus 2. Unfortunately i know almost nothing regarding these android thingy. I know it has been almost 2 years, would you mind guide me through the steps? I would appreciate it so much.
Thanks.

I9505 bootlooping & not booting

Galaxy S4 I9505
Phone was second hand to me at the start of this year, though had been well looked after, always in a case etc
I flashed it with the newest stock ROM in January this year
I9505XXUHOJ2_I9505BTUHOJ1_I9505XXUHOJ2
& rooted with CF AutoRoot
It has worked fine until about 2 weeks ago, when it randomly shut down. After restarting, it kept bootlooping.
Left it off & charging overnight, & the next morning it booted ok. Managed to use spotify for a few hours.
Then it started bootlooping again, sometimes getting all the way but then crashing after a few minutes.
Managed to boot into recovery & do a 'wipe cache', that didnt fix it.
'Wipe data' didnt fix it
Have flashed the PIT file & ROM (via odin), no errors in odin, done it twice now
wiped cache & data
still wont boot past the white splash screen, only sometimes boots into recovery
(also, only the menu button lights up, not the back button.)
I've checked the power button (clicks & dosnt stick)
Dont think the batteries the issue (charges fine, dosnt get warm, isnt bulging)
What else could stop it booting?

Have you tried booting into safe mode?
Safe mode, from what I read, can be accessed by holding the menu button while the phone boots.
But you should also do some reading about it, in case I'm wrong.
The other idea would be to try a custom ROM.

GDReaper said:
Have you tried booting into safe mode?
Safe mode, from what I read, can be accessed by holding the menu button while the phone boots.
But you should also do some reading about it, in case I'm wrong.
The other idea would be to try a custom ROM.
Click to expand...
Click to collapse
Can't boot into safe mode
(& having read up on it, it would only not run apps that arn't already in the ROM)
Any suggestions for a custom ROM
& why would it work when the original official one won't?

Well, it's booted far enough to get into android & add a google account, then it bootloops again.
Then after leaving it off for a while, it will boot & let me look at settings etc, then bootloop
however
the menu soft key stays lit all the time after a boot
the top half of the phone, around the camera, gets very warm
Does that indicate it's a hardware issue?
Could it be the battery?

If it's the top half warming up without you doing anything, it's the motherboard.
Boot into recovery and and let it stand by, see if it reboots.

xedge said:
Well, it's booted far enough to get into android & add a google account, then it bootloops again.
Then after leaving it off for a while, it will boot & let me look at settings etc, then bootloop
however
the menu soft key stays lit all the time after a boot
the top half of the phone, around the camera, gets very warm
Does that indicate it's a hardware issue?
Could it be the battery?
Click to expand...
Click to collapse
The battery can't prevent the ROM from booting. It would have to turn off during the boot, which it doesn't. So, by my logic, it isn't the battery.
Try official CM.

GDReaper said:
The battery can't prevent the ROM from booting. It would have to turn off during the boot, which it doesn't. So, by my logic, it isn't the battery.
Try official CM.
Click to expand...
Click to collapse
Hello Reaper, I have exactly same problem. Please help. In my case leds are working fine, rest is exactly the same problem. And It all happened suddenly on its stock rom. I never rooted my phone before.

kingpin090 said:
Hello Reaper, I have exactly same problem. Please help. In my case leds are working fine, rest is exactly the same problem. And It all happened suddenly on its stock rom. I never rooted my phone before.
Click to expand...
Click to collapse
Try this.

GDReaper said:
Try this.
Click to expand...
Click to collapse
I am not able to go into recovery after firmware flash. The recovery bot appears and when the blue loading bar goes to half, the phone reboots and then again boot loop. I just noticed this always happened when i flashed a rom. I was never able to enter recovery on first boot.

kingpin090 said:
I am not able to go into recovery after firmware flash. The recovery bot appears and when the blue loading bar goes to half, the phone reboots and then again boot loop. I just noticed this always happened when i flashed a rom. I was never able to enter recovery on first boot.
Click to expand...
Click to collapse
Does phone go into download mode ?

gosha98_ said:
Does phone go into download mode ?
Click to expand...
Click to collapse
Yes it goes normally into download mode. Firmware always flashed without any error. But i noticed I can't enter recovery on first boot to do factory wipe.
Sent from my GT-I9300 using XDA-Developers mobile app

kingpin090 said:
Yes it goes normally into download mode. Firmware always flashed without any error. But i noticed I can't enter recovery on first boot to do factory wipe.
Click to expand...
Click to collapse
Why do you want to do factory wipe after one boot?

Its the only thing i didn't tried till now, my phone crashes and reboots everytime during boot.
Sent from my GT-I9300 using XDA-Developers mobile app

Galaxy A5 A500f Boot Loop Problem

I've spent all day fighting with the boot loop on my A500f.
I had the phone running really well with Ahmed's Resurrection Remix ROM on this post:
https://forum.xda-developers.com/sa...om-resurrection-remix-5-8-2-sm-a500h-t3572062
He doesn't detail TWRP installation, so I used DeadSquirrel's 3.1.0 post here:
https://forum.xda-developers.com/sa...overy-twrp-3-0-2-0-samsung-galaxy-a5-t3439233
I hadn't seen that TWRP can be installed without root, so I rooted with Chainfire first. I'm not sure, but I think I got the Chainfire file from this post:
https://forum.xda-developers.com/sa...-to-root-galaxy-a5-a500fu-lollipop-5-t3137613
The file I downloaded for the A500f is "CF-Auto-Root-a5lte-a5ltexx-sma500f.zip" (contains tar.md5)
The post says it is for Lollipop, but the instructions say this is a Chainfire root zip for Android 4.4.4. One post suggested this might be the cause of my boot loop.
The instructions say that this Chainfire Auto Root solution also contains a recovery file, but I was never able to boot into this recovery, so I went directly to installing DeadSquirrel's TWRP. I was able to boot into this recovery. From there I installed the Resurrection Remix ROM. WIthin the ROM, I installed SuperSU from the Play Store, but SuperSU informed me the phone was not rooted, so I flashed the SuperSU root zip from their website, which I believe was the file, A500FXXS1CQC2_A500FOJV1CPH3_XFE.zip
SuperSU now reported root was present, so I installed WiFi Connection Manager from the Play Store, granted it root access in SuperSU, and used the Fix Problems menu item to repair the wifi shutting off the phone problem that I was originally working on. That fix worked well, so I left the wifi on and ran YouTube on Autoplay for about 4 hours. Deciding the problem was solved, I gave the phone back to my son, and he brought it back to me dead 5 minutes later. I'm not sure if it already that the boot loop problem at that point.
The phone would no longer boot. I noticed a seandroid enforcing notification, and thought it might be a security issue preventing boot. I found a thread that said I needed that flashing back to a Samsung ROM would remove the seandroid notice and that I needed to update to Android 6.0.1 before installing TWRP to solve the boot loop issue. I went to Sammobile and found the newest ROM for my A500f was the A500FXXS1CQC2_A500FOJV1CPH3_A500FXXU1CPH2_HOME.
I installed this in Odin, and the phone has never come back to me since then. I've made endless retries throughout the day, trying different combinations of the Chainfire root, different versions of TWRP, and different root methods, but all to no avail. One post even suggested that if you flash factory ROM from Odin just once, it will create a boot loop, but if you flash twice, it solves it, but it didn't work for me. It's also gotten increasingly difficult to get into recovery. Whether in stock ROM or TWRP, I was only able to get in about 10% of the time. Boot loop behavior has varied between boot logo - vibration - black screen and battery charge logo - vibration - black screen.
I found this thread that is supposed to address the boot loop problem, and I tried these versions of root and TWRP, but it didn't help:
https://forum.xda-developers.com/sa...overy-samsung-galaxy-a52015-sm-a500f-t3360802
At the moment, I'm on stock ROM. On power up, you get the Galaxy A5 screen, then it vibrates and goes black, then the lightening battery logo comes up, it vibrates, and goes black, and then the green battery status logo comes up, and then the phone goes black. It's also booting into stock recovery okay, and I can do the recovery functions. I just can't boot the phone.
So now, I try the instructions again in ashyx's TWRP post. Now I can get into TWRP. I power up and the phone sticks on the Galaxy A5 boot screen for a long time. Then it vibrates and repeats. It's basically the same as above, but there is a long delay before rebooting instead of instantly as before. Now I go back into TWRP and flash the Resurrection Remix ROM and the behavior is the same. Power up and get the Galaxy A5 boot screen for 8 seconds (this time sporting a warranty bit: kernal notice), 2 seconds of black screen, vibration, battery/lightening logo blinks on, then off, vibration, battery/lightening logo blinks on then off. Black screen, then standard battery charging percent indicator. I did that three or four times to make note of the behavior. Then the power switch wouldn't work, so I used the technique to press the volume up and down key together with the power key to turn it back on. Now it is in a non-stop 5 second cycle of vibrate - flash the icon - black screen that won't quit. Throughout the day I've been stuck with this in both stock and custom ROM. Only once during the day did I see the custom ROM boot all the way through. The stock ROM has never booted.
Now the recovery key combination won't boot TWRP either. The key combination just makes the Galaxy A5 screen flash instead of the battery icon. But I can get into TWRP by rebooting with the recovery key combination on leaving Download mode.
If anyone understands what's wrong here, I'd appreciate it.
Thanks

If I were you, I'd flash an older version of stock ROM with Odin, reboot with factory reset then I will let Samsung Smart Switch to upgrade my phone. After that I will notice the CORRECT version of ROM...

MoshPuiu said:
If I were you, I'd flash an older version of stock ROM with Odin, reboot with factory reset then I will let Samsung Smart Switch to upgrade my phone. After that I will notice the CORRECT version of ROM...
Click to expand...
Click to collapse
Thank you. That did the trick. Going back to the original factory ROM of Android 5.0.1 brought the phone back to being bootable again. I wish I understood what is going on on the low level to cause these things!

MoshPuiu said:
If I were you, I'd flash an older version of stock ROM with Odin, reboot with factory reset then I will let Samsung Smart Switch to upgrade my phone. After that I will notice the CORRECT version of ROM...
Click to expand...
Click to collapse
Samsung Smart Switch what is it?

Faraz_74 said:
Samsung Smart Switch what is it?
Click to expand...
Click to collapse
Samsung app:
http://www.samsung.com/us/smart-switch/

Same Issue
Hello PJK2011 . I'm having the same problem can you please help me to find the link of the Stock ROM you installed?

xoein said:
Hello PJK2011 . I'm having the same problem can you please help me to find the link of the Stock ROM you installed?
Click to expand...
Click to collapse
I believe Sammobile is the standard location to download stock Samsung ROMS:
https://www.sammobile.com/firmwares/galaxy-a5/SM-A500F/

xoein said:
Hello PJK2011 . I'm having the same problem can you please help me to find the link of the Stock ROM you installed?
Click to expand...
Click to collapse
you can download in here also updato.com
Sent from my SM-A500F using xda premium

S5e won't boot

I am at a loss here. After almost 2 years of working flawlessly, my s5e won't boot.
The screen got frozen while using anydesk, and had to force a restart (power button + up and fown volume buttons).
I can see the Samsung logo for less than a second, and then it switches off. Without touching anything, after some seconds the same thing happens.
I tried charching it and similar behaviour: i see charging circle for less than a second, and off again.
I AM AT A LOSS.
I managed to boot it pressing power+volume_up buttons and this is what i see (attached). It can stay like that for a long time so I guess battery and it's connection to the tablet are fine.
PLEASE ANY HELP WOULD BE VERY WELCOME
UPDATE:
I have tried MANY things in the 6 hours since I wrote this post. I am able to put the tablet in download mode and ODIN (and my PC) recognizes it. I am able to flash VBMETA but now TWRP (fail).
At some point the tablet rebooted in normal mode (why?) but got frozen again and had to reboot it.
Anyone can point me to how to recover it? I don't mind right now to loose what is in the internal memory.

Did you try to hard reboot (power_button + volume_down ) for more than 9 seconds.
If did not work then you may have to charge the phone? If its fully charged try to flash stock rom using Odin. When your device does not boot that means the stock firmware is corrupted and needs to be flashed again. That happened to me before and now my phone is working fine. Wanna know how to flash it? Look it up online!

Abd El-Rahman El-Batal said:
Did you try to hard reboot (power_button + volume_down ) for more than 9 seconds.
If did not work then you may have to charge the phone? If its fully charged try to flash stock rom using Odin. When your device does not boot that means the stock firmware is corrupted and needs to be flashed again. That happened to me before and now my phone is working fine. Wanna know how to flash it? Look it up online!
Click to expand...
Click to collapse
I did try a hard reboot. Same result. I already rooted and installed a custom rom on it (first thing i did).
Twrp is installed but I'm unable to boot to it.
Any more ideas?

iruiz2 said:
I did try a hard reboot. Same result. I already rooted and installed a custom rom on it (first thing i did).
Twrp is installed but I'm unable to boot to it.
Any more ideas?
Click to expand...
Click to collapse
Listen up carefully. There is a truck to boot into recovery. When you hard reboot screen will turn black then show logo. While screen is
Black quick hold vol up button and power.
Worked on my galaxy a10. Tell meh the results bro

Abd El-Rahman El-Batal said:
Listen up carefully. There is a truck to boot into recovery. When you hard reboot screen will turn black then show logo. While screen is
Black quick hold vol up button and power.
Worked on my galaxy a10. Tell meh the results bro
Click to expand...
Click to collapse
It just loads the screen attached in my first post.

Try flash via Odin, it still in download mode with this warning.

The tablet was still covered by warranty so I called the seller and they took it to a Samsung repair store. They replaced the motherboard, so I guess it was not recoverable.
The bad news is that they updated to android 11, I was quite happy with old 9.0 because I had TWRP and Magisk working.
Thank you for all that tried to help.