Database Info

[Q] Stuck at Boot/Starting Apps

Hey folks!
Again a problem with my little phone.
Today I got similar reboots, after about 5 it got stuck at the bootscreen.
Tried to wipe cache+dalvik, booting it up again, but after it prepared all apps it stucks at the "Starting Apps" window..
Also flashed another kernel and recovery. Nothing worked so far..
Any help, because I don't want to wipe data because I made some important photos today and I don't wanna miss then..
Thanks in advance,
RS

RestlessScreams said:
Hey folks!
Again a problem with my little phone.
Today I got similar reboots, after about 5 it got stuck at the bootscreen.
Tried to wipe cache+dalvik, booting it up again, but after it prepared all apps it stucks at the "Starting Apps" window..
Also flashed another kernel and recovery. Nothing worked so far..
Any help, because I don't want to wipe data because I made some important photos today and I don't wanna miss then..
Thanks in advance,
RS
Click to expand...
Click to collapse
First of all you connect your phone to PC and try to copy all the content of /sdcard to your PC. If it doesn't work reboot your phone to fastboot and connect it to your PC with CMD (in fastboot folder) running and enter the command "adb pull /sdcard C:/" without quotes, Also you can replace C:/ to any address where you would like to copy all your SD data.
After that you can flash any ROM to get your device in working condition.
If you have any query do ask or you may end up losing all your data.

forgotter said:
First of all you connect your phone to PC and try to copy all the content of /sdcard to your PC. If it doesn't work reboot your phone to fastboot and connect it to your PC with CMD (in fastboot folder) running and enter the command "adb pull /sdcard C:/" without quotes, Also you can replace C:/ to any address where you would like to copy all your SD data.
After that you can flash any ROM to get your device in working condition.
If you have any query do ask or you may end up losing all your data.
Click to expand...
Click to collapse
Thanks for your tips, but like I said it's stuck in bootloop and I can't access it through pc.
Also adb won't work an yes, I've installed all drivers :b

RestlessScreams said:
Thanks for your tips, but like I said it's stuck in bootloop and I can't access it through pc.
Also adb won't work an yes, I've installed all drivers :b
Click to expand...
Click to collapse
Why don't you try the fastboot method.
Put your phone into Fastboot by pressing volume down+power button. Connect it to your PC, fastboot would recognize it for sure. You then enter the command. You can even use adb from fastboot.

forgotter said:
Why don't you try the fastboot method.
Put your phone into Fastboot by pressing volume down+power button. Connect it to your PC, fastboot would recognize it for sure. You then enter the command. You can even use adb from fastboot.
Click to expand...
Click to collapse
It just says "device not found" when using adb.
with fastboot I can flash things but can't pull or?

RestlessScreams said:
It just says "device not found" when using adb.
with fastboot I can flash things but can't pull or?
Click to expand...
Click to collapse
Is your boot loader unlocked, if not you'll have to unlock it first (but doing so will void your warranty).
Assuming that you have a unlocked device follow the steps below to get all your data. (I myself tried and it worked, so it must work on your device also)
1. Make sure you have installed drivers for your Moto G, if not then do it.
2. Download the adb file to access your phone during fast boot.
3. Download the TWRP recovery 2.7.0.0 by dhacker for falcon (Moto G) on your PC and copy it in the adb folder.
4. Rename the downloaded file to "recovery.img" without quotes.
5. Connect you phone in fastboot mode to your PC and flash the recovery by command "fastboot flash recovery recovery. img" without quotes.
7. On your phone then go to recovery option and press volume up key until phone vibrates. The phone will then go to recovery mode.
8. On your PC, in command prompt(adb) enter command "adb pull /data/media/0/ C:\Moto" without quotes. The process will start and may take hours depending on no's of file and their size.
P.S. I won't be able to answer any more of your question as I won't have data connection any more. I'm sure if you will follow all the steps properly, you will get all your data. If you can't understand anything then just Google it.

Phone doesn't proceed from boot animation!
Guys!
This would be my 1st time here. I've never faced any sort of problem with any of my android devices but this one.
My phone got lost a week back. So, I used "android device manager" to wipe/lock the phone but I think it didn't as the phone was switched off all this while.
So, some gentleman found my phone and returned it to me just today. I put it up for charging. It popped up 0% battery screen and turned on after 10-15min.
As soon as the boot animation(earth/buildings) finished it jumped to a black screen.
It has been on charging for last 3 hours.
So my questions are
1) Can I make back up of the data without turning it on/formatting it?
2) How can I make it to work?
Thanks a lot in advance!

vjsharma89 said:
Guys!
This would be my 1st time here. I've never faced any sort of problem with any of my android devices but this one.
My phone got lost a week back. So, I used "android device manager" to wipe/lock the phone but I think it didn't as the phone was switched off all this while.
So, some gentleman found my phone and returned it to me just today. I put it up for charging. It popped up 0% battery screen and turned on after 10-15min.
As soon as the boot animation(earth/buildings) finished it jumped to a black screen.
It has been on charging for last 3 hours.
So my questions are
1) Can I make back up of the data without turning it on/formatting it?
2) How can I make it to work?
Thanks a lot in advance!
Click to expand...
Click to collapse
@vjsharma89 :I have posted the answer in your thread.
And after you had backuped your data, factory reset your phone from fastboot by choosing factory option and then reboot it. Or should work fine.

delete this pls, wrong thread

[Q] Motorola Moto G Lost OS

Hey guys,
Recovery : TWRP 2.6.3.3
USB Debugging : Off
Cannot connect to PC.
Recently, I accidently formatted my Moto G through the advanced wipe and I selected all the partitions to be wipe such as dalvik cache, data, internal storage, cache and system. And now my Moto G doesn't have any OS in it and I can't reboot it at all. I don't have any idea what to do right now. Can someone please help me how can I install a new rom for my Moto G so I can use it like a normal phone again. Please no harsh words, I know it's my mistake and I really need help.

Make sure you post things like this in the Q&A section ull get better help over there then in this General section

Xavier102296 said:
Make sure you post things like this in the Q&A section ull get better help over there then in this General section
Click to expand...
Click to collapse
Thanks

You just need to flash a ROM.

Ammar115 said:
Hey guys,
Recovery : TWRP 2.6.3.3
USB Debugging : Off
Cannot connect to PC.
Recently, I accidently formatted my Moto G through the advanced wipe and I selected all the partitions to be wipe such as dalvik cache, data, internal storage, cache and system. And now my Moto G doesn't have any OS in it and I can't reboot it at all. I don't have any idea what to do right now. Can someone please help me how can I install a new rom for my Moto G so I can use it like a normal phone again. Please no harsh words, I know it's my mistake and I really need help.
Click to expand...
Click to collapse
If you are able to go to recovery(which you should be able to do), download any custom ROM of your choice like PA, CM, SLIM etc.. flash that rom by following the Installation instructions in the thread. YOu should be able to get the phone back to normal. And if you want the stock ROM, then download the stock files and flash it, you might loose custom recovery, then follow the same things you did to get TWRP in the first place.

phanitej said:
If you are able to go to recovery(which you should be able to do), download any custom ROM of your choice like PA, CM, SLIM etc.. flash that rom by following the Installation instructions in the thread. YOu should be able to get the phone back to normal. And if you want the stock ROM, then download the stock files and flash it, you might loose custom recovery, then follow the same things you did to get TWRP in the first place.
Click to expand...
Click to collapse
I would if I could. The problem is I formatted the whole phone which included the internal storage too. My CM Rom is in the internal storage and it's already deleted. I tried to connect my phone to the pc so that I could transfer a rom into it but failed cause my pc won't recognized my phone as the media transfer devices. It's only recognized my phone as fastboot falcon s. I've installed Motorola Device Manger but it's also failed. I also tried to install using adb sideload but I got device not found error and my phone doesn't listed in the device attached after I typed 'adb devices'. For the OTG and memory card reader method I haven't try yet because I don't have any of it.

Ammar115 said:
I would if I could. The problem is I formatted the whole phone which included the internal storage too. My CM Rom is in the internal storage and it's already deleted. I tried to connect my phone to the pc so that I could transfer a rom into it but failed cause my pc won't recognized my phone as the media transfer devices. It's only recognized my phone as fastboot falcon s. I've installed Motorola Device Manger but it's also failed. I also tried to install using adb sideload but I got device not found error and my phone doesn't listed in the device attached after I typed 'adb devices'. For the OTG and memory card reader method I haven't try yet because I don't have any of it.
Click to expand...
Click to collapse
What does it say when you try
Code:
adb devices
or
when you reboot to bootloader with phone connected and type
Code:
fastboot devices
If it shows a device for fastboot devices then follow this to flash back to stock. Make sure you download the right stock firmware for your phone.

phanitej said:
What does it say when you try
Code:
adb devices
or
when you reboot to bootloader with phone connected and type
Code:
fastboot devices
If it shows a device for fastboot devices then follow this to flash back to stock. Make sure you download the right stock firmware for your phone.
Click to expand...
Click to collapse
when I type 'adb devices' it give me an error saying that my device is not found. for the 'fastboot devices', I tried it too but also an error. It say, 'fastboot' is not recognized as an internal or ecternal command, operable program or batch file.

Ammar115 said:
when I type 'adb devices' it give me an error saying that my device is not found. for the 'fastboot devices', I tried it too but also an error. It say, 'fastboot' is not recognized as an internal or ecternal command, operable program or batch file.
Click to expand...
Click to collapse
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files

phanitej said:
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files
Click to expand...
Click to collapse
This is what I get using minimal adb and fastboot. What does it mean?

phanitej said:
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files
Click to expand...
Click to collapse
I've followed all the instructions but my phone still not rebooting. When I try to reboot it, it only show me the warning of unlocked bootloader screen, black screen, warning of unlocked bootloader screen then dead android screen. What should I do now?

It means your phone is in fastboot mode and recognised by your PC. Next you'll have to "fastboot flash" the necessary files to install a recovery and a system, and you should be good to go.

Few weeks back I ****ed up soft bricked my phone had kindda same issue when I switch my phone on I get a dead android logo. Gave to the service center in India and got a replacement a new xt1033
P.s I was trying to root and my warranty was void still got a new one try your luck bruhhh
Sent from my XT1033 using XDA Free mobile app

SbM_ said:
It means your phone is in fastboot mode and recognised by your PC. Next you'll have to "fastboot flash" the necessary files to install a recovery and a system, and you should be good to go.
Click to expand...
Click to collapse
I only want to connect my phone to my pc so I can transfer any rom to my phone so that I can install the rom. But right now, my pc won't recognized it as media transfer that's why I can't transfer any file to my phone. I tried everything. I've installed motorola device manager but all that I got is motorola adb interface that make my phone can connect to the pc when in bootloader mode.I don't have any OTG cable or mobile sd card reader.

phanitej said:
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files
Click to expand...
Click to collapse
Hey, I've done all of the flashing instruction from the xda forum link that you gave me. My problem for now is, why is my phone not rebooting? The only thing that happen after the flashing is my phone only show the 'warning bootloader unlocked' and the dead android with red triangle screen. It won't boot into the stock rom that I've flashed. The stock rom/firmware that I used is correct. Please help me.. I really need to use my phone.

Ammar115 said:
Hey, I've done all of the flashing instruction from the xda forum link that you gave me. My problem for now is, why is my phone not rebooting? The only thing that happen after the flashing is my phone only show the 'warning bootloader unlocked' and the dead android with red triangle screen. It won't boot into the stock rom that I've flashed. The stock rom/firmware that I used is correct. Please help me.. I really need to use my phone.
Click to expand...
Click to collapse
K there's a resolve for this...Provided that you haven't ****ed up your phone by making it hard bricked...
1 - Get a freaking rom and sideload it through TWRP to boot into system...
+ Download a ROM
+ Put it in the same folder as ADB and Fastboot and rename it to something easier that you can type exactly (ex: 1.zip, backup.zip...)
+ Shift + Right Click at a blank field in the window
+ Choose Open Command....
+ On TWRP, go to Advanced => Sideload => Tick the 2 boxes => Swipe to start sideloading
+ Type in adb sideload <yourzipname>.zip on the cmd (on your computer)
+ Wait for the process to finish, then you now have a working phone...
2 - Follow this guide using the proper firmwares that match your original one : http://forum.xda-developers.com/showthread.php?t=2542219

Zerelth said:
K there's a resolve for this...Provided that you haven't ****ed up your phone by making it hard bricked...
1 - Get a freaking rom and sideload it through TWRP to boot into system...
+ Download a ROM
+ Put it in the same folder as ADB and Fastboot and rename it to something easier that you can type exactly (ex: 1.zip, backup.zip...)
+ Shift + Right Click at a blank field in the window
+ Choose Open Command....
+ On TWRP, go to Advanced => Sideload => Tick the 2 boxes => Swipe to start sideloading
+ Type in adb sideload <yourzipname>.zip on the cmd (on your computer)
+ Wait for the process to finish, then you now have a working phone...
2 - Follow this guide using the proper firmwares that match your original one : http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Done but still, the same thing happened.

Ammar115 said:
I only want to connect my phone to my pc so I can transfer any rom to my phone so that I can install the rom. But right now, my pc won't recognized it as media transfer that's why I can't transfer any file to my phone. I tried everything. I've installed motorola device manager but all that I got is motorola adb interface that make my phone can connect to the pc when in bootloader mode.I don't have any OTG cable or mobile sd card reader.
Click to expand...
Click to collapse
Your PC will not recognize it as media transfer / storage while you are in bootloader / fastboot mode, its perfectly normal. When you type fastboot devices it should show you a number which means it working as intended. This is an old thread but it shows how to transfer your ROM to sdcard via adb push command. http://forum.xda-developers.com/showthread.php?t=1667929

Ammar115 said:
I only want to connect my phone to my pc so I can transfer any rom to my phone so that I can install the rom. But right now, my pc won't recognized it as media transfer that's why I can't transfer any file to my phone. I tried everything. I've installed motorola device manager but all that I got is motorola adb interface that make my phone can connect to the pc when in bootloader mode.I don't have any OTG cable or mobile sd card reader.
Click to expand...
Click to collapse
The output of the "fastboot devices" command clearly shows your phone is recognised by your PC. As I said all you need to do now is use the correct "fastboot flash" commands to restore recovery and system. Tutorials can be found in this forum.

Thank you.
I would like to say thank you to all peoples who help me solving my lost os problem. Thanks for all the informations. My moto G is working perfectly normal right now.

[Q] systemUI broken?

Hey,
I have a major issue on my HAM7 L09, which runs on 5.1 lollipop, is rooted and has TWRP recovery.
Yesterday I was triyng to install Xposed framwork via TWRP. Okay, that failed. But then, when I rebooted my phone, my softkeys and Statusbar, overall SystemUI, is not working. I tried factory reset which didn't help. Since i did factory reset, i can no longer use adb commands from my computer, because it wont no longer authorize my phone. Even tried to downgrade to B127 to install custom rom after that, but because I have TWRP I cant downgrade. And since adb commands are not working, I cannot flash stock recovery either.
Any help please?
Urgent.
Thank you

Getoo said:
Hey,
I have a major issue on my HAM7 L09, which runs on 5.1 lollipop, is rooted and has TWRP recovery.
Yesterday I was triyng to install Xposed framwork via TWRP. Okay, that failed. But then, when I rebooted my phone, my softkeys and Statusbar, overall SystemUI, is not working. I tried factory reset which didn't help. Since i did factory reset, i can no longer use adb commands from my computer, because it wont no longer authorize my phone. Even tried to downgrade to B127 to install custom rom after that, but because I have TWRP I cant downgrade. And since adb commands are not working, I cannot flash stock recovery either.
Any help please?
Urgent.
Thank you
Click to expand...
Click to collapse
Hey Buddy, i did the same thing you did when twrp came out which was to install xposed. Also got the same issue where aspect's of the phone's UI (Status bar, nav bar, homescreen) were missing. I even did the factory reset via twrp. I was able to get out of it, but it required some focus, patience and lots of rebooting. I don't recall exactly what I did for the first step, butThat being said when you plug you phone to your PC, does your PC still recognize it? (ex.prompt to install Android Hisuite Manager pops-up on your monitor)
- If the answer is yes, with your M7 connected to the PC, enable "Developer Options" (if you haven't done it yet)>then reboot. On next boot>go to Developer's Options again>select "Revoke USB Debugging Authorizations".
-Once done, remove the USB connection from your PC's USB port then place it back in again. Let me know if the "ADB Authorization" screen appears.

Okay, as soon as I get home, I'll try that. Right now I'm using button saviour for softkeys
Sent from my HUAWEI MT7-L09 using XDA Free mobile app

blitzkriegger said:
Hey Buddy, i did the same thing you did when twrp came out which was to install xposed. Also got the same issue where aspect's of the phone's UI (Status bar, nav bar, homescreen) were missing. I even did the factory reset via twrp. I was able to get out of it, but it required some focus, patience and lots of rebooting. I don't recall exactly what I did for the first step, butThat being said when you plug you phone to your PC, does your PC still recognize it? (ex.prompt to install Android Hisuite Manager pops-up on your monitor)
- If the answer is yes, with your M7 connected to the PC, enable "Developer Options" (if you haven't done it yet)>then reboot. On next boot>go to Developer's Options again>select "Revoke USB Debugging Authorizations".
-Once done, remove the USB connection from your PC's USB port then place it back in again. Let me know if the "ADB Authorization" screen appears.
Click to expand...
Click to collapse
Being tring your solution for 4 hours. Sadly it doesn't work. authprization screen wont appear

Getoo said:
Being tring your solution for 4 hours. Sadly it doesn't work. authprization screen wont appear
Click to expand...
Click to collapse
Does your computer recognize your phone?

blitzkriegger said:
Does your computer recognize your phone?
Click to expand...
Click to collapse
yes, it does. I can watch my folders and so on.

Getoo said:
yes, it does. I can watch my folders and so on.
Click to expand...
Click to collapse
Sorry for the late reply Buddy as I'm at work at the moment. Found an easier solution. Make sure your phone is connected to your computer. Also open up the folder where you have your ADB files ans stock lollipop recovery. Open the command prompt within that folder.
Next do the following
1.) Turn off your phone and manually invoke TWRP via physical button combination
2.) Once on TWRP, select "Reboot" then choose "Bootloader".
3.) Once the phone is on bootloader mode, connect your phone to your PC's USB port then switch to your open command prompt and type:
fastboot devices
Your device should then be displayed.
4.) next flash the stock lollipop recovery for L09 via the command:
fastboot flash recovery <recoveryname.img>
5.) Once done flashing execute:
fastboot reboot
6.) Once your phone is back on, you can then use your computer to place the "Transition" update.app either within internal storage (create dload folder within internal memory) or sd card/usb drive. Proceed to do local update or update from usb.
7.) Once your phone has the transition lollipop firmware copy the Kitkat rollback firmware then do the usual drill via local/usb update.

blitzkriegger said:
Sorry for the late reply Buddy as I'm at work at the moment. Found an easier solution. Make sure your phone is connected to your computer. Also open up the folder where you have your ADB files ans stock lollipop recovery. Open the command prompt within that folder.
Next do the following
1.) Turn off your phone and manually invoke TWRP via physical button combination
2.) Once on TWRP, select "Reboot" then choose "Bootloader".
3.) Once the phone is on bootloader mode, connect your phone to your PC's USB port then switch to your open command prompt and type:
fastboot devices
Your device should then be displayed.
4.) next flash the stock lollipop recovery for L09 via the command:
fastboot flash recovery <recoveryname.img>
5.) Once done flashing execute:
fastboot reboot
6.) Once your phone is back on, you can then use your computer to place the "Transition" update.app either within internal storage (create dload folder within internal memory) or sd card/usb drive. Proceed to do local update or update from usb.
7.) Once your phone has the transition lollipop firmware copy the Kitkat rollback firmware then do the usual drill via local/usb update.
Click to expand...
Click to collapse
Holy god, dude you are awsome, it worked. Thank you so much. :angel:

How to save my media files from a bootlooping OnePlus One?

Hi,
I am totally lost and need help to get my personal data (images, videos most important) back from my bootlooping phone.
I browsed the privacy guard settings and disabled some boot and caller rights for google services and google play (with the intention to prevent it from looking up for updates constantly and drain my battery).
Then it restarted itself as I plugged it in for charge and is bootlopping since.
I have no root, the latest official CM update and a the build in Cyanogen recovery, since it came out of nowhere no usb bugging enabled (I believe).
When I try to enter the phone via ABD sideload from the CM Recovery "pull" my folders it says error:closed. adb backup wont work either.
It tells me: adb: unable to connect for backup: closed
This whole topic is kind a new for me - I never was in that situation and for now all I want is my images and videos back from my phone at least. I will try any method to save them.
I hope some can help me - I don´t know what to do anymore

This should theoretically work.
Flash TWRP by fastboot, then boot into this newly installed TWRP, then connect the device to your PC, as TWRP natively supports MTP, your Internal & External SD (If any) should be visible and you can copy your data over.

Thank you so much for this hint!
I will try that.
So I Just change my recoverer with this method right? This is possible without root and usb debugging?

Joshwin Aranha said:
This should theoretically work.
FlashTWRP] by fastboot, then boot into this newly installed TWRP, then connect the device to your PC, as TWRP natively supports MTP, your Internal & External SD (If any) should be visible and you can copy your data over.
Click to expand...
Click to collapse
It says:
writing recovery
FAILED (remote: Device not unlocked cannot flash or erase)
Is this game over?

Sore6 said:
It says:
writing recovery
FAILED (remote: Device not unlocked cannot flash or erase)
Is this game over?
Click to expand...
Click to collapse
Well no, it means your device has a locked bootloader, and you'll have to unlock it, the problem there is unlocking bootloader formats the device. Not always, but there's a good chance that you might lose your data, still thought give this a try,
fastboot devices (to confirm that your One is detected by the PC)
fastboot oem unlock (to unlock the device)
fastboot flash recovery recovery.img (to flash the recovery)
if this succeeds, disconnect the device and manually boot in to recovery, not to system, this is important because system will overwrite the TWRP with CYNGN recovery, so boot into recovery and try connecting your device to PC, see if MTP works.
PS - sorry for the late reply, i slept the whole sunday
EDIT - Wait, did you say that USB debugging is disabled ? then i think it might not work, give it a shot anyway tho.

Joshwin Aranha said:
Well no, it means your device has a locked bootloader, and you'll have to unlock it, the problem there is unlocking bootloader formats the device. Not always, but there's a good chance that you might lose your data, still thought give this a try,
fastboot devices (to confirm that your One is detected by the PC)
fastboot oem unlock (to unlock the device)
fastboot flash recovery recovery.img (to flash the recovery)
if this succeeds, disconnect the device and manually boot in to recovery, not to system, this is important because system will overwrite the TWRP with CYNGN recovery, so boot into recovery and try connecting your device to PC, see if MTP works.
PS - sorry for the late reply, i slept the whole sunday
EDIT - Wait, did you say that USB debugging is disabled ? then i think it might not work, give it a shot anyway tho.
Click to expand...
Click to collapse
Thanks for your help here - I guess I can´t win here with all my preconditions :/
One last question is:
Is there any method to wipe or flash the phone with a higher chance of keeping data even if little?

Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.

Sore6 said:
Thanks for your help here - I guess I can´t win here with all my preconditions :/
One last question is:
Is there any method to wipe or flash the phone with a higher chance of keeping data even if little?
Click to expand...
Click to collapse
I was just about to say to try booting into the recovery, follow @nitrobg's instructions, get the recovery and instead of flashing the recovery, just try booting into it, command is
fastboot boot recovery.img
Hope it helps you, the pain of losing precious data isn't unknown to the best of us
EDIT - What caused the bootloop ? Who knows, maybe we manage to fix that

EDIT - What caused the bootloop ? Who knows, maybe we manage to fix that
Click to expand...
Click to collapse
I disabled some google play and google services from booting via the official cm privacy settings
Reason was to disable the battery drain by play when searching constantly for GOOGLE android updates...
Needed to disable that in cm12 back then and it helped.

nitrobg said:
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Click to expand...
Click to collapse
I will try that! Thank you.
I get back here with the result.

nitrobg said:
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Click to expand...
Click to collapse
Unfortunately it gives me this in the commandline:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.430s

That's unfortunate.
Do you have adb access to your phone in the CM recovery? If you do, try removing/renaming com.google.android.gms from both system and data partitions. You might have to play around trying to get root or to remount the partitions but it could work.

nitrobg said:
That's unfortunate.
Do you have adb access to your phone in the CM recovery? If you do, try removing/renaming com.google.android.gms from both system and data partitions. You might have to play around trying to get root or to remount the partitions but it could work.
Click to expand...
Click to collapse
Sadly no - all adb commands end in "error:closed"

Try this:
Power Down the OnePlus One
Hold the Power Button Until Android Starts to Boot Up
As Soon as Android Starts Booting Up, Let Go of the Power Button
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons
Continue Holding Both Volume Buttons Until Android is Fully Booted
If you did everything correctly, Android *should* boot up just fine and show "Safe mode" on the lower left corner of the screen.

nitrobg said:
Try this:
Power Down the OnePlus One
Hold the Power Button Until Android Starts to Boot Up
As Soon as Android Starts Booting Up, Let Go of the Power Button
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons
Continue Holding Both Volume Buttons Until Android is Fully Booted
If you did everything correctly, Android *should* boot up just fine and show "Safe mode" on the lower left corner of the screen.
Click to expand...
Click to collapse
Didnt work because as far as i know one has to be in the android ui - hold pwer off key and then hold the restart menu item and then the volume buttons + power buttons code should work.
Thanks anyway - i wiped it now.
it works but all data is gone

Not really, you hold volume buttons while the OS is booting and it should force a safe mode boot with all apps disabled.
Well, too bad now. It could've worked.

nitrobg said:
Not really, you hold volume buttons while the OS is booting and it should force a safe mode boot with all apps disabled.
Well, too bad now. It could've worked.
Click to expand...
Click to collapse
Honestly - I held it for 4 Minutes. There was a Vibrate Signal everytime it wanted to boot up into android but it didnt. Then it kept the cynogenmod loader til the next little vibration. It was a loop with no entry to android GUI

It's sad that you had to lose your data
Anyway, Take a lesson from this, weekly nandroid backups
(That's what I do)

Joshwin Aranha said:
It's sad that you had to lose your data
Anyway, Take a lesson from this, weekly nandroid backups
(That's what I do)
Click to expand...
Click to collapse
Thanks man - jeah I took care of such case beforehand now and rooted, bought titaniuam backup and enabled usb debugging instantly...
Also I am now using TWRP.
Lesson learned.
Thanks to you all for helping me!
I am really thankful for your effort.
Kind regards

Some kind thanks on my replies maybe ?
Haha, anyway. Take care.

Completely stock OnePlus One stuck in bootloop after latest CM OTA update

Hi everyone,
I'm hoping you can help me. I've had a OnePlus One since August 2014, completely stock. Never modded it, never 'flashed' anything, never installed anything outside of the Google Play Store. Always installed the official OTA updates as they pop up on the phone itself. Basically a reeeeealllly boring android user!
So Thursday morning (09/06/2016) I got a notification that a system update was downloaded and ready to install. Clicked install, the process began, phone rebooted as per usual. However, on the install progress screen (the green android with the spinning cogs), about one third of the way through the phone freezes. About 20 seconds later the phone reboots itself and then tries to install the update again. Freezes. Reboots. Tries to install. Freezes. Reboots. Tries to install.... I think you get the idea. It was doing this for a couple of hours before I checked it.
I'm moderately tech-savvy but never really got involved with android modding, rooting or flashing. So I'm a bit confused as to why my completely stock phone is stuck in a bootloop after installing an official CyanogenMod OTA update. The current status of my phone is that I can only boot into Fastboot mode via VolUp + Power. I can get my computer to detect my phone in Fastboot mode, however it informs me that my bootloader is locked. Attempting to boot into recovery mode via VolDown + Power just starts the update install and enters the bootloop.
I've done some research in to flashing a recovery image or manually applying the OTA update. One problem I've noticed is that I have absolutely NO idea what version of Android / CM my device was at before the update, and I have NO idea what version it was trying to update to. I do know that it was some version of Marshmallow before it broke. I've had no issues with the phone before this, aside the occasional self-reboot.
I REALLY want to keep all my data (pictures, contacts etc.) and am very nervous about actually doing anything because I have very little idea as to what I'm really doing.
Can anyone offer any advice on how to get my phone to boot/update/recover through Fastboot with a locked bootloader and without losing any data?
Thanks,
Stormin'
AKA the "HOW DO I PLAY BOOM BEACH NOW?!" guy
Edit: I solved my issue. It might work for you too, permalink to my post (#9) below: http://forum.xda-developers.com/showpost.php?p=67278091&postcount=9

Are you able to get into recovery mode? If so, you should be able to just flash a new ROM. Sideload one using the adb push command, wipe your data (this will clear settings, apps, etc. DO NOT SELECT SD CARD - that will wipe your personal files including your photos). Then install. Hopefully it should all work fine.
If you can't access the recovery can you access the bootloader sceen (the one with the big green bugdroid)? Then I'd suggest using Fastboot to install a new recovery. Then try the above.
If you can't even get to that stage you're screwed, just like me (unless anyone has any ideas). I've had soft bricks many times before but today I can't even get to the bootloader screen. ADB says the phone is offline. The screen is back and flickers on for a split second every now and then. Bloody CM Updater.

As IBM9001 has said, if you can get into recovery - even being stock - you can still clear your cache - don't do a full factory reset, just the cache, this may help, but even if it doesn't it still rules out one option.

I can't access recovery mode, using the key combo it just boots straight into the installer.
I've got a support ticket open with OnePlus and a scheduled remote assistance tomorrow. However from the preparational email it looks like they are going to factory reset the phone and then clean install CM. They've instructed me to make sure that all my files are backed up... I assume this means I will lose them.
Is there ANY way just to access or pull the photos off my phone? That's the most important bit. Dropbox hit its storage limit at the beginning of 2015 and I refused to pay, so now I have 18 months worth of pictures that I have no other copies of on death row
The only thing I can access is Fastboot...
Edit:
ibm9001 said:
If you can't access the recovery can you access the bootloader sceen (the one with the big green bugdroid)? Then I'd suggest using Fastboot to install a new recovery.
Click to expand...
Click to collapse
I can boot into Fastboot mode, and plugging my phone into my PC works i.e. it is recognised. I have the fastboot .exe and USB drivers, and can issue commands to my phone through cmd such as
Code:
fastboot reboot-bootloader
which works.
How do I use a recovery .img through Fastboot? or can I pull the contents of the sd card through Fastboot?

Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..

Hi guys,
I have the same issue!
If I flash a new recovery from fast boot will I lose my data on sdcard?
Thanks.
Sent from my iPad using Tapatalk

masterjigar said:
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Click to expand...
Click to collapse
I cannot boot into recovery mode, unfortunately

masterjigar said:
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Click to expand...
Click to collapse
I'm currently having a very similar issue, but my phone completed the update. It's just stuck in a reboot/"optimizing apps" loop. I can boot into recovery and I tried to clear cache, but It's still just optimizing apps then rebooting and optimizing again over and over. Do you think your suggestion would help me too?

Wooooo, I've fixed it! I don't know why what I did fixed the issue (probably bypassed something) but my phone is up and running again! First thing I'm doing is making a freakin' backup!
So I was just trying everything in desperation. So that others can attempt to fix the same problem, here's what I did:
1. State of phone was either boots normally and crashes when installing update, or boots into fastboot. Would NOT boot into recovery!
2. Booted into fastboot using key combo (hold Volume Up, then Power Button)
3. Attached phone to computer via data usb lead
4. Started up cmd console, used command "fastboot devices" to check that device was recognised (note you need the fastboot files and USB drivers etc., Google it if you're not sure)
5. Used command "fastboot continue" to continue with 'autoboot'. This rebooted my phone but skipped the installer and went to the 'optimising apps' stage. Left phone alone for a couple of hours but it got stuck in another bootloop optimising apps, rebooting, optimising apps and so on.
6. Turned phone off, then booted normally with just the power button. This started the update install again except it didn't crash, and completed the update install. Then it optimised the apps again (albeit with a different total app count) and once finished, phone starts up normally.
Thanks for all the suggestions everyone! Happy to have my phone back. Now to go through the half-dozen or so voicemails I've collected over these last few days... great.

Hi guys,
@stormin, congrats!
@masterjigar, so you didn't lose the data like photos etc. doing so?
I can boot to recovery, but can't connect by PC to it.
In fast boot mode my PC sees it as well as in dab sideload mode.
I haven't the boot loader unlocked then I have to do it first, right?
But cyanogen site says that unlocking the boot loader will wipe all the device data.
Is there any way get the photos and other files back?
Thanks.

From the FAQ:
Q4a: Can I flash ROMs or SuperSU or anything else with the stock recovery?
No, the stock recovery can only flash zips that are signed by CM, this means official updates only. You need a custom recovery to flash anything else.​
Click to expand...
Click to collapse
Does it mean I can flash an official CM firmware without unlocking the boot loader?
Thanks.

hibernick said:
Hi guys,
@stormin, congrats!
@masterjigar, so you didn't lose the data like photos etc. doing so?
I can boot to recovery, but can't connect by PC to it.
In fast boot mode my PC sees it as well as in dab sideload mode.
I haven't the boot loader unlocked then I have to do it first, right?
But cyanogen site says that unlocking the boot loader will wipe all the device data.
Is there any way get the photos and other files back?
Thanks.
Click to expand...
Click to collapse
That's what adb sideload is all about. It will give you temporary adb access (which is always after unlocking bootloader and root). So you can also flash xip via sideload. Without losing data and media..

Same problem, Also PC not detecting my phone
Hey Guys, I am Stuck at the same thing at Bootloop. But to do anything further I need to connect my phone to the PC. I haven't been able to connect my phone to PC since the time I have got the phone. I tried all available drivers and even tried different cables. I dont know what has been left out to try.
If any one has a working driver pls share the link. Its been three days now that my phone is dead.
Pls help!!
Thanks in advance.

masterjigar said:
That's what adb sideload is all about. It will give you temporary adb access (which is always after unlocking bootloader and root). So you can also flash xip via sideload. Without losing data and media..
Click to expand...
Click to collapse
can I flash this cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img with the sideload and get adb working over usb?
Thanks

hibernick said:
can I flash this cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img with the sideload and get adb working over usb?
Thanks
Click to expand...
Click to collapse
You can't adb sideload .img or a partition.
You have to use fastboot.
Code:
fastboot flash boot boot_img_name.img
or
Code:
fastboot boot boot_img_name.img

saurav007 said:
You can't adb sideload .img or a partition. You have to use fastboot.
Click to expand...
Click to collapse
Yes but then I have to unlock my bootloader first. And unlocking bootloader erase all the user files....
Is there other way to to run cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img on the devise?