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.
Related
Hi all,
Been given a Nexus S i9023 by my brother who has been "tampering" with it and now it seems a bit messed up.
When booting up - it gets stuck on the "Google" screen with a padlock on it... I can get into fastboot and I can flash recovery but when I attempt to load any recovery - I get that same Google screen with the padlock! I've downloaded a stock rom and even flashed system etc via fastboot but that still gets me nowhere past the damn padlock!!
I've tried to "fastboot boot recovery.img" and I still get the Google screen with the padlock but it says "Fastboot status - OK" on the bottom left.
I've searched and searched but everyone just seems to give tips on how to flash recovery. I know how to flash recovery; it just seem to be going into it though! Could the internal memory be screwed?
Thanks for any advice!
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
albundy2010 said:
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
Click to expand...
Click to collapse
The phone stops at Google with the padlock on boot! Can't even get into the OS. Going to try to unbrick it and Odin but left my ubuntu laptop at my parents and can't be bothered to go get it... couldn't get it to work booting off cd rom. Kept giving me the "SBL Injection Failure Failed to find device" error booting ubuntu on a CD!
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
albundy2010 said:
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
Click to expand...
Click to collapse
No idea why I said Odin - I meant the unbrickable recovery thing.
I tried Odin with a Jig last night; got it into download mode and flashed with odin. Got the same result.
fastboot -w also gives the same issue...
If I have a storage issue - is there any way I can tell?
Basically you can tell by the issues you're having. Doing all the proper stuff to flash images etc and still having a booting/working device.
As far as a actual diagnostic tool I don't know of one. But it sure sounds like a hw issue to me.
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Pironi90 said:
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Click to expand...
Click to collapse
Reflash your recovery using fastboot.
polobunny said:
Reflash your recovery using fastboot.
Click to expand...
Click to collapse
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Pironi90 said:
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Click to expand...
Click to collapse
Flash custom recovery.img part
http://wiki.cyanogenmod.org/wiki/fastboot#Flash_Custom_Recovery.img
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
polobunny said:
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
I think so yes, I could access recovery before if that's what you mean by unlocked
Pironi90 said:
I think so yes, I could access recovery before if that's what you mean by unlocked
Click to expand...
Click to collapse
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
You are entering recovery. Stock recovery
If you want a custom one either flash with fastboot or if you're rooted with a app. Goo manager. Rom manager etc.
Keep it mind that if you're on a stock ROM the custom recovery gets overwritten back to stock when the phone boots up the os
Q
UselessSniper001 said:
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
Click to expand...
Click to collapse
Then my phone is unlocked yes
polobunny said:
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
In installed the drivers and I installed the fastboot executable, but what do I have to do next? If I run the fastboot.exe, it just quickly shows a CMD-window and then disappears.
Edit:
I just discovered that, when I'm at the bootloader (I think it's called that way, the screen where you can select recovery), and I choose to reboot, I get the same 'error' as when I try to enter recovery.
Edit:
Alright, I was able to flash a new recovery, using cmd, but now when I try to enter my recovery, the phone gets stuck at a black screen with Google logo and padlock...
I have same problem as wolverine_2k who made the post. My nexus, can't start, I tried reboot and recovery but didn't work. After reboot or recovery I see Google logo, than Nexus screen and that is it. It didn't move to home screen and it stay with lighting screen all the time till I remove the battery. I can't power off it and don't know what to do. I can't transfer data with my PC (it don't recognize the device - only notice that "unknown device" is connected). Please any ideas?
P.S.: My English is not good, if someone answer do it simple please
Thanks!
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
You need to find a driver that works so it'll recognize the device. Once you do this, you need to flash boot.img to restore the recovery since not working. Then, redo the ROM or restore from backup if you can. Flashing a new recovery boot.img should fix the issue.
2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
Hi, In first place, You are in the right place to get help:good:
2. ADB won't work on fastboot nor in a damaged recovery.
3. fastboot works:victory: Try to flash recovery once again (fastboot flash recovery recoveryname.img)
4. if 3 works, wipe system, caches. Flash the Rom you want, don't use that app anymore.
GUGUITOMTG4 said:
Hi, In first place, You are in the right place to get help:good:
2. ADB won't work on fastboot nor in a damaged recovery.
3. fastboot works:victory: Try to flash recovery once again (fastboot flash recovery recoveryname.img)
4. if 3 works, wipe system, caches. Flash the Rom you want, don't use that app anymore.
Click to expand...
Click to collapse
Thanks! got to recognize any way to do this without loosing data?
2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
There is a chance to keep your data + storage contents. If you manage to flash and boot into recovery, in 'wipe' menu manually check-mark "cache,system"
don't mark internal "storate and data", nothing will happen to your media and apps data.
2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
May be able to dirty flash but most likely, since you had the screen dimmed too much, you'll have to wipe data in order to override/remove the problem. You can try this way but may just send you back through this whole process if problem reoccurs. I'd just wipe the data to be safe.
2point said:
Well, I was using an app called screen dimmer, and did pressed the button to dim the screen when all of a sudden it froze. It was like this for a while so I restarted it, it is able to go in fastboot, but nothing else. When i start It it hangs on the boot loader screen and can stay like that all day. if I go into recovery the screen goes black and the display is only backlit. I was going to try to to use the adb to factory reset it, but I could not get it to recognize the nexus 5 as a device. I used a bunch of different drivers. I did root my phone, and have the exposed framework but this was done a long time ago and I had no problems since. no idea how to fix this any help?!?!? Sorry if this is the wrong place to put this I'm new to this site.
Click to expand...
Click to collapse
Oy vey! You shouldn't have been tinkering as you clearly don't know what you're doing.
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
2point said:
Thanks! got to recognize any way to do this without loosing data?
Click to expand...
Click to collapse
No, and if you had done your homework you would know that. If the data is so important, back it up before modding.
GUGUITOMTG4 said:
There is a chance to keep your data + storage contents. If you manage to flash and boot into recovery, in 'wipe' menu manually check-mark "cache,system"
don't mark internal "storate and data", nothing will happen to your media and apps data.
Click to expand...
Click to collapse
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
2point said:
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
Click to expand...
Click to collapse
Reflash the recovery.img
2point said:
When I do fastboot boot recovery.img I get the android bot with a red exclamation but nothing else I might just do flashall
Click to expand...
Click to collapse
The general idea is that your recovery is broken.
So, you need to flash a new recovery by placing a recovery.img file into your fastboot folder in the computer(recommend twrp). Like you did the first time you fladhed a recovery.
Then, turn off the phone, press volume down+ power button and it will boot into bootloader. Make sure it is on fastboot mode. After that, on the computer open cmd on the fastboot folder and and type:
fastboot flash recovery nameofrecoveryfile.img,
press enter.
It should flash a new recovery image if done correctly. Then, poweroff the phone, boot again into bootloader, choose recovery and it will reboot into recovery. Then follow. The steps of my first post.
jd1639 said:
Reflash the recovery.img
Click to expand...
Click to collapse
GUGUITOMTG4 said:
The general idea is that your recovery is broken.
So, you need to flash a new recovery by placing a recovery.img file into your fastboot folder in the computer(recommend twrp). Like you did the first time you fladhed a recovery.
Then, turn off the phone, press volume down+ power button and it will boot into bootloader. Make sure it is on fastboot mode. After that, on the computer open cmd on the fastboot folder and and type:
fastboot flash recovery nameofrecoveryfile.img,
press enter.
It should flash a new recovery image if done correctly. Then, poweroff the phone, boot again into bootloader, choose recovery and it will reboot into recovery. Then follow. The steps of my first post.
Click to expand...
Click to collapse
Did that and get a
C:\Users\nkkou_000\programs\adt-bundle-windows-x86_64-20131030\sdk\platform-tool
s>fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
sending 'recovery' (13272 KB)...
OKAY [ 0.620s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 44.593s
C:\Users\nkkou_000\programs\adt-bundle-windows-x86_64-20131030\sdk\platform-tool
s>
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
2point said:
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
Click to expand...
Click to collapse
You have a couple of options depending on how much data you can afford to lose on your phone. The least intrusive is to adb push a Rom on to your phone when you're in twrp Then flash that rom in twrp
The easier, but you'll lose all data on your phone is to flash the flash-all.bat file in fastboot
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
2point said:
But I can do fastboot boot openrecovery-twrp-2.6.3.4-hammerhead.img and will will boot into the recovery just fine
And that twrp says that i have no os installed
Click to expand...
Click to collapse
Then, it seems recovery now is good. If you have rom zip in the storage. Just wipe system and cache, flash the rom and see what happens
When in the twrp I can't get fastboot to recognize it as a device, or adb either
2point said:
When in the twrp I can't get fastboot to recognize it as a device, or adb either
Click to expand...
Click to collapse
Your adb drivers aren't setup correctly. They're different than the fastboot ones. Try Google tool adb fastboot drivers xda.
jd1639 said:
Your adb drivers aren't setup correctly. They're different than the fastboot ones. Try Google tool adb fastboot drivers xda.
Click to expand...
Click to collapse
When you are on twrp. You dont need to use fastboot nor adb. Just flash a rom if have one to flash
GUGUITOMTG4 said:
When you are on twrp. You dont need to use fastboot nor adb. Just flash a rom if have one to flash
Click to expand...
Click to collapse
How do i do that?
2point said:
How do i do that?
Click to expand...
Click to collapse
Have you flashed roms before? And do you have one on your internal sdcard? If so flash it in twrp
jd1639 said:
Have you flashed roms before? And do you have one on your internal sdcard? If so flash it in twrp
Click to expand...
Click to collapse
I have the factory image from google for my nexus 5
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?
hello all this what happens I flash a bad room and it keeps rebooting and I cannot go back to recovery check this video if someone have an idea or fix it before.
thanks in advance.
https://www.youtube.com/watch?v=Qh5BTDVhGOY
https://www.youtube.com/watch?v=Ya-0WwswJi8
kasey348 said:
hello all this what happens I flash a bad room and it keeps rebooting and I cannot go back to recovery check this video if someone have an idea or fix it before.
thanks in advance.
https://www.youtube.com/watch?v=Qh5BTDVhGOY
Click to expand...
Click to collapse
You can try re-flashing TWRP which may clean it up and allow you in. Power down the phone (pull the battery and put it back in), hold down the volume down, and plug your phone into your computer while keeping the volume down pressed. Should get you into fastboot/bootloader. From there you can do "fastboot flash recovery twrp-3.0.2-0-h918.img". You can then reboot via "fastboot reboot". Now I'm not too familiar with the h918 model so I'm not for sure you can do this in fastboot/bootloader but if you can it's worth a shot.
Try "fastboot erase cache" instead. Your TWRP seems to be getting stuck running an OpenRecoveryScript which is located in the cache partition according to documentation. If you clear the cache it should theoretically let you into TWRP instead of running the script on start.
redshorty4 said:
You can try re-flashing TWRP which may clean it up and allow you in. Power down the phone (pull the battery and put it back in), hold down the volume down, and plug your phone into your computer while keeping the volume down pressed. Should get you into fastboot/bootloader. From there you can do "fastboot flash recovery twrp-3.0.2-0-h918.img". You can then reboot via "fastboot reboot". Now I'm not too familiar with the h918 model so I'm not for sure you can do this in fastboot/bootloader but if you can it's worth a shot.
Try "fastboot erase cache" instead. Your TWRP seems to be getting stuck running an OpenRecoveryScript which is located in the cache partition according to documentation. If you clear the cache it should theoretically let you into TWRP instead of running the script on start.
Click to expand...
Click to collapse
thanks man
but I can only lock or unlock my boot-loader it doesn't take any other commands to reboot into recovery i need to make work adb shell.
thanks for your advice.
kasey348 said:
thanks man
but I can only lock or unlock my boot-loader it doesn't take any other commands to reboot into recovery i need to make work adb shell.
thanks for your advice.
Click to expand...
Click to collapse
Was worth a shot. If you can get an adb shell you should be able to fix recovery. Did you try locking and then unlocking the bootloader? It wipes userdata and cache when you lock/unlock. That could fix your TWRP.
redshorty4 said:
Was worth a shot. If you can get an adb shell you should be able to fix recovery. Did try locking and unlocking the bootloader? It wipes userdata and cache when you lock/unlock. That could fix your TWRP.
Click to expand...
Click to collapse
yes i did that too it wipes the phone then it boots into the system but all the apps keeps crashing all i get is a black screen.
Mine is doing the exact same thing,,, Except I don't get passed the LG logo. I'm on the same version of TWRP also.
The G.O.A.T. said:
Mine is doing the exact same thing,,, Except I don't get passed the LG logo. I'm on the same version of TWRP also.
Click to expand...
Click to collapse
crap i have the whole week without phone i guess the only way we can fix this is loading or flashing a tot file i just need a dll file that one have it anywhere,
but if i find a solution i will let you know my friend, don't give up we are get it fix trust me.
keep looking on this tread i'm downgrading my pc to windows 7 today I been installing a lot crap to make this phone work and nothing i read that windows 7 works better.
hello guys previous night my opo is automatically restart and hang on logo i try to restart several times and leave mobile upto 1 hour but cant succeded.... the condition is set is going to fastboot and recovery and charging also i try wipe cache but still same.... i have very important data inside my opo.... please guide me how i recover my opo or inside data....
oneplus one
variant 64gb
os cyanogen 12
Is it a stock COS ROM?
I suggest you to dirty flash the rom without overwriting /data
So if you flash the zip it's OK but if you flash from fastboot be aware of not flashing userdata_64.img
yes my ROM is stock rom .... what is dirty flash please guide me....
imran72199 said:
yes my ROM is stock rom .... what is dirty flash please guide me....
Click to expand...
Click to collapse
-Is your bootloader unlocked?
-What recovery do you have?
Available signed flashable ROMs: https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/
Find yours or just chose one, and download the signed flashable zip, then copy it to the phone (while in recovery the phone has MTP enabled on the PC) then just flash that ROM from the recovery, this will overwrite system but won't touch data and most likely fix the bootloop.
Before rebooting after flash wipe cache and dalvik just in case.
Next time do a nandroid backup if you have sensible data. I usually don't keep anything important on the phone, everything on google drive.
I don't know my bootloader is locked or unlocked.... when I try to connect phone in recovery and connect USB nothing happen but when I restart phone and set is on onelus logo and attch usb PC recognized as mtp USB device but driver failed....
I don't know my bootloader is locked or unlocked.... when I try to connect phone in recovery and connect USB nothing happen but when I restart phone and set is on onelus logo and attch usb PC recognized as mtp USB device but driver failed....
imran72199 said:
I don't know my bootloader is locked or unlocked.... when I try to connect phone in recovery and connect USB nothing happen but when I restart phone and set is on onelus logo and attch usb PC recognized as mtp USB device but driver failed....
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Do this.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Do this.
Click to expand...
Click to collapse
He wants to keep data... So he at least should try my method first.
seanwlk said:
He wants to keep data... So he at least should try my method first.
Click to expand...
Click to collapse
Then reply him about his latest query.
imran72199 said:
I don't know my bootloader is locked or unlocked.... when I try to connect phone in recovery and connect USB nothing happen but when I restart phone and set is on onelus logo and attch usb PC recognized as mtp USB device but driver failed....
Click to expand...
Click to collapse
Which recovery? Stock or twrp? I'm not sure that when you have stock recovery on the phone gets recognized as mtp on the PC.
I can think of adb to push the ROM zip on the PC but if you claim it doesn't get recognized I have no clue. Are you sire you have the google USB drivers installed?
seanwlk said:
Which recovery? Stock or twrp? I'm not sure that when you have stock recovery on the phone gets recognized as mtp on the PC.
I can think of adb to push the ROM zip on the PC but if you claim it doesn't get recognized I have no clue. Are you sire you have the google USB drivers installed?
Click to expand...
Click to collapse
i have cyanogen recovery.... my set is previously rooted with kingoroot..... i dont know what to do which driver should install or which rom should be good for me..... please give me simple method to recover my data from opo..... i dont have twrp recovery installed.... only cyanogen recovery after pressing vol+ vol- and power this are the options under cyanogen recovery.....
reboot system now
apply update
wipe data/factory reset
wipe cache partition
wipe media
reboot to bootloader
power down
view recovery logs
inside apply update
apply from adb
choose from internal storage
imran72199 said:
i have cyanogen recovery.... my set is previously rooted with kingoroot..... i dont know what to do which driver should install or which rom should be good for me..... please give me simple method to recover my data from opo..... i dont have twrp recovery installed.... only cyanogen recovery after pressing vol+ vol- and power this are the options under cyanogen recovery.....
reboot system now
apply update
wipe data/factory reset
wipe cache partition
wipe media
reboot to bootloader
power down
view recovery logs
inside apply update
apply from adb
choose from internal storage
Click to expand...
Click to collapse
Install fastboot,adb and google USB drivers : https://drive.google.com/file/d/0B9fZIF6vzIBzT2ZtZkNSVFI5ZHc/view?usp=drivesdk
Reboot the pc
Download twrp: https://dl.twrp.me/bacon/twrp-3.1.0-0-bacon.img.html
Reboot in fastboot mode.
Open a command prompt on the PC inside the folder where the downloaded recovery is.
-Find the folder (maybe user/Downloads)
-while holding shift mouse right click inside the folder
-select "open command prompt here"
Connect your phone and type in cmd
Code:
fastboot devices
If you're lucky and did everything correctly then your phone should appear and you can continue, if not uninstall the drivers you previously had and kingroot and whatever minitool you used and try again.
Now that the device is visible
Code:
fastboot flash recovery twrp twrp-3.1.0-0-bacon.img
Phone should reboot. Just turn off and boot into recovery and hopefully you'll see twrp.
Now connect the phone to the PC an you should see the mass storage and you'll be able to copy the ROM zip there.
Now just flash the zip of the rom and you're done.
U cannot assure you that it will fix the bootloop but it's your best choice.
In the future:
-Never use kingroot or other ****ty mini tools. CMD and manual flash are always the best choice.
-Do a backup if you are not confident with this kind of stuff.
-Don't keep too much stuff on the phone. Use google drive. And services to save contacts, notes images videos.
seanwlk said:
Install fastboot,adb and google USB drivers : https://drive.google.com/file/d/0B9fZIF6vzIBzT2ZtZkNSVFI5ZHc/view?usp=drivesdk
Reboot the pc
Download twrp: https://dl.twrp.me/bacon/twrp-3.1.0-0-bacon.img.html
Reboot in fastboot mode.
Open a command prompt on the PC inside the folder where the downloaded recovery is.
-Find the folder (maybe user/Downloads)
-while holding shift mouse right click inside the folder
-select "open command prompt here"
Connect your phone and type in cmd
Code:
fastboot devices
If you're lucky and did everything correctly then your phone should appear and you can continue, if not uninstall the drivers you previously had and kingroot and whatever minitool you used and try again.
Now that the device is visible
Code:
fastboot flash recovery twrp twrp-3.1.0-0-bacon.img
Phone should reboot. Just turn off and boot into recovery and hopefully you'll see twrp.
Now connect the phone to the PC an you should see the mass storage and you'll be able to copy the ROM zip there.
Now just flash the zip of the rom and you're done.
U cannot assure you that it will fix the bootloop but it's your best choice.
In the future:
-Never use kingroot or other ****ty mini tools. CMD and manual flash are always the best choice.
-Do a backup if you are not confident with this kind of stuff.
-Don't keep too much stuff on the phone. Use google drive. And services to save contacts, notes images videos.
Click to expand...
Click to collapse
writing recovery failed remote: device not unlocked cannot flash or erase
imran72199 said:
writing recovery failed remote: device not unlocked cannot flash or erase
Click to expand...
Click to collapse
This means your bootloader is still locked so you basically can't do anything. To unlock it you would need to factory reset. So your only option is to try installing the ROM via adb on the cyanogen recovery.
PS
Please don't spam my PM I can read you here I get notifications instantly. Thanks. I want to keep the post public in order to help future users in similar conditions so I'm not going to help you in private if it's not strictly necessary.
oneplus one data recovery
seanwlk said:
This means your bootloader is still locked so you basically can't do anything. To unlock it you would need to factory reset. So your only option is to try installing the ROM via adb on the cyanogen recovery.
PS
Please don't spam my PM I can read you here I get notifications instantly. Thanks. I want to keep the post public in order to help future users in similar conditions so I'm not going to help you in private if it's not strictly necessary.
Click to expand...
Click to collapse
if i try to install rom from adb it will kill my data??
imran72199 said:
if i try to install rom from adb it will kill my data??
Click to expand...
Click to collapse
Try to push the zip from adb to /sdcard and then flash the zip through the recovery (which technically should do it since it's a stock ROM)
This will result in a "dirty flash" which will not delete data.
This is your only option in the current state of your phone, if you had rooted your phone properly without kingroot you would have booloader unlocked an you would've had more options. If this doesn't work you are forced to factory reset. And use this opportunity to unlock bootloader with
Code:
fastboot oem unlock
Which due to security measurements will delete all the data.
Before you going to flash anything using adb or something, do this.....
1. Turn off your phone completely.....
2. Connect the charger and let it charger for 10 minutes
3. While the charger is still connected, press the power button (turn it on)
4. Wait....
If the phone boot normally while the charger is still connected, unplug the charger and waits....if the phone goes back bootloop after a few minutes and hours without charger connected then your problem is a dying battery not software....buy a new battery and once your replace it, it will solved your problem without having to flash anything via adb or recovery...it also can save all your data....
iPusak Gaoq™ said:
Before you going to flash anything using adb or something, do this.....
1. Turn off your phone completely.....
2. Connect the charger and let it charger for 10 minutes
3. While the charger is still connected, press the power button (turn it on)
4. Wait....
If the phone boot normally while the charger is still connected, unplug the charger and waits....if the phone goes back bootloop after a few minutes and hours without charger connected then your problem is a dying battery not software....buy a new battery and once your replace it, it will solved your problem without having to flash anything via adb or recovery...it also can save all your data....
Click to expand...
Click to collapse
battery is ok i try your method but not worked
seanwlk said:
Try to push the zip from adb to /sdcard and then flash the zip through the recovery (which technically should do it since it's a stock ROM)
This will result in a "dirty flash" which will not delete data.
This is your only option in the current state of your phone, if you had rooted your phone properly without kingroot you would have booloader unlocked an you would've had more options. If this doesn't work you are forced to factory reset. And use this opportunity to unlock bootloader with
Code:
fastboot oem unlock
Which due to security measurements will delete all the data.
Click to expand...
Click to collapse
what if i flash ota update file through adb sideload of oxygen os
iPusak Gaoq™ said:
Before you going to flash anything using adb or something, do this.....
1. Turn off your phone completely.....
2. Connect the charger and let it charger for 10 minutes
3. While the charger is still connected, press the power button (turn it on)
4. Wait....
If the phone boot normally while the charger is still connected, unplug the charger and waits....if the phone goes back bootloop after a few minutes and hours without charger connected then your problem is a dying battery not software....buy a new battery and once your replace it, it will solved your problem without having to flash anything via adb or recovery...it also can save all your data....
Click to expand...
Click to collapse
Lolwat?? What kind of sorcery are you talking about.... ? if it was the battery it wouldn't have happend right after he messed with that stuff. Improve your troubleshot skills ? this kind of stuff happened to me insane amount of times and always were able to fix it, in this case the guy is limited by the fact he doesn't have the bootloader unlocked.
imran72199 said:
what if i flash ota update file through adb sideload of oxygen os
Click to expand...
Click to collapse
That depends if you are running oxygen os, you can't flash an OTA of OS that you are currently not running. To dirty flash you have to use the same version or distribution of the OS you are currently running.