[Q] Upgraded to CM12S - won't boot, no recovery...Help please? - ONE Q&A, Help & Troubleshooting

HI all
So I downloaded the OTA, flashed it with TWRP which was fine, then it rebooted.
Because it was encrypted it asked me to enter the password. Then it asked me again...
"Decryption unsuccessful - the password yo entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you setup your phone after the reset, you'll have an opportunity to restore and data that was backed up to your Google account"
One button - RESET PHONE
I press it and it tried to go into TWRP but appears to be in some kind of bootloop.
I can get into Fastboot but ADB DEVICES doesn't show a phone.
I can get into recovery (vol down + power) and the data appears to decrypt properly - all my files are there.
I'm trying a restore now. I'll update the thread when It's done.
Any suggestions on how to install the OTA? (assuming this works properly)

koocha said:
HI all
So I downloaded the OTA, flashed it with TWRP which was fine, then it rebooted.
Because it was encrypted it asked me to enter the password. Then it asked me again...
"Decryption unsuccessful - the password yo entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you setup your phone after the reset, you'll have an opportunity to restore and data that was backed up to your Google account"
One button - RESET PHONE
I press it and it tried to go into TWRP but appears to be in some kind of bootloop.
I can get into Fastboot but ADB DEVICES doesn't show a phone.
I can get into recovery (vol down + power) and the data appears to decrypt properly - all my files are there.
I'm trying a restore now. I'll update the thread when It's done.
Any suggestions on how to install the OTA? (assuming this works properly)
Click to expand...
Click to collapse
Adb devices will never return anything in fastboot because adb doesn't work in fastboot, only fastboot commands work in fastboot mode. Report back with any further information.
Transmitted via Bacon

timmaaa said:
Adb devices will never return anything in fastboot because adb doesn't work in fastboot, only fastboot commands work in fastboot mode. Report back with any further information.
Transmitted via Bacon
Click to expand...
Click to collapse
Ah right, that makes sense!
Backup restore failed. I can mount data via TWRP so I can pull the files off my phone to my computer, so I guess I'll do that then wipe it and flash it all again

koocha said:
Ah right, that makes sense!
Backup restore failed. I can mount data via TWRP so I can pull the files off my phone to my computer, so I guess I'll do that then wipe it and flash it all again
Click to expand...
Click to collapse
Sounds like a good idea to me.
Transmitted via Bacon

I am experiencing exactly the same thing. I can see the device in fastboot, but was unable to get the device into recovery until just now. It seems that holding Power+Volume Down during the TWRP bootloop will shut the phone off after several loops. Then I held Power+Volume Up to get into fastboot, but I can't seem to repeat it. After rebooting via fastboot command, I got back to the "Data corrupt" message. Holding the power button on that screen instead of touching Reset gave me a power menu. It properly shut down, and then I was able to Power+Volume Down into recovery.
Does anyone think I have a realistic chance of installing the previous CM11 over top of the botched CM12 to get back to a working phone without having to re-install all my apps? I don't know enough about Android upgrade processes to know if this is even a little bit feasable.

Related

[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

Okay, so I ****ed up...

Allright, so I ****ed up.
I had some issues (softwarewise) with my OPO and decided I wanted a factory-reset. As my settings menu softlocked constandly I decided to do it through the recovery module, however, instead of doing a factory reset, I wiped everything but my internal SD (meaning system, Dalvik Cache and one other option).
Currently, I can't get anywhere but to the TeamWin Recovery Module (version 2.7). I can't get anything onto my SD card, as far as I can tell) and I'm stuck.
I ****ed up, I've done this before and should've known better - but is there any way out of this?
Thanks in advance!
Edit: Additional info:
I have installed all drivers I could find (Quallcom 2012, from a dropbox link), have the Android SDK and global ADB drivers. The OPO recovery tool (the moduled one to install stock Cyano 11S) does not find/recognise my device and neither does the Quallcom Configuration Tool (QPST), but my computer does show it under "other devices". I'm stuck!
lrpvo said:
Allright, so I ****ed up.
I had some issues (softwarewise) with my OPO and decided I wanted a factory-reset. As my settings menu softlocked constandly I decided to do it through the recovery module, however, instead of doing a factory reset, I wiped everything but my internal SD (meaning system, Dalvik Cache and one other option).
Currently, I can't get anywhere but to the TeamWin Recovery Module (version 2.7). I can't get anything onto my SD card, as far as I can tell) and I'm stuck.
I ****ed up, I've done this before and should've known better - but is there any way out of this?
Thanks in advance!
Click to expand...
Click to collapse
follow this guide...but make sure your bootloader is unlocked and I am assuming you have 64 GB version if you don't have 64 GB version please use another guide....good luck
http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
What does it do when you try to access twrp? Sometimes its a pain but it takes continuous trying
Sent from my A0001 using XDA Forums
lrpvo said:
Allright, so I ****ed up.
I had some issues (softwarewise) with my OPO and decided I wanted a factory-reset. As my settings menu softlocked constandly I decided to do it through the recovery module, however, instead of doing a factory reset, I wiped everything but my internal SD (meaning system, Dalvik Cache and one other option).
Currently, I can't get anywhere but to the TeamWin Recovery Module (version 2.7). I can't get anything onto my SD card, as far as I can tell) and I'm stuck.
I ****ed up, I've done this before and should've known better - but is there any way out of this?
Thanks in advance!
Click to expand...
Click to collapse
Just flash the stock images with fastboot. Section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
XDA Moderator
Transmitted via Bacon
I just did the same thing, no boot logo and no fastboot option after resetting a couple times
You can use the adb sideload feature to push a zip file of your rom back on
I just loaded my rom on my phone and it's booting is i type
download sdk and run cmd prompt adb sideload rom.zip
Heisenberg said:
Just flash the stock images with fastboot. Section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I've seen that post, however, I do not get to fastboot (power + volUP just powers my device off). When I install SuperSU my device SHOWS fastboot mode but my PC does not allow moving files to it (my pc does recognise it, it makes the USB-device-added sound, but doesn't allow for file transfer).
I have the correct drivers (I'm pretty sure)
cristo_rey said:
I just did the same thing, no boot logo and no fastboot option after resetting a couple times
You can use the adb sideload feature to push a zip file of your rom back on
I just loaded my rom on my phone and it's booting is i type
download sdk and run cmd prompt adb sideload rom.zip
Click to expand...
Click to collapse
This. No need to go through all that hassle of returning to factory rom and losing your files. Do adb sideload from recovery.
lrpvo said:
I've seen that post, however, I do not get to fastboot (power + volUP just powers my device off). When I install SuperSU my device SHOWS fastboot mode but my PC does not allow moving files to it (it does recognise it, it makes the USB-device-added sound).
I have the correct drivers (I'm pretty sure)
Click to expand...
Click to collapse
Are you switching off, then powering back on while holding volume up?
gsmyth said:
Are you switching off, then powering back on while holding volume up?
Click to expand...
Click to collapse
Yes I am. I'm currently looking at "Fastboot Mode" from the thing TWRP asked me to install when it noticed I had no OS (SuperSU?). But it does not allow my PC to write files to it.
lrpvo said:
Yes I am. I'm currently looking at "Fastboot Mode" from the thing TWRP asked me to install when it noticed I had no OS (SuperSU?). But it does not allow my PC to write files to it.
Click to expand...
Click to collapse
SuperSU has nothing to do with fastboot. And fastboot mode doesn't allow file transfer, that isn't what it's for, but if you're in fastboot mode you don't need to transfer any files, you can just follow the instructions I linked you to earlier.
lrpvo said:
Yes I am. I'm currently looking at "Fastboot Mode" from the thing TWRP asked me to install when it noticed I had no OS (SuperSU?). But it does not allow my PC to write files to it.
Click to expand...
Click to collapse
Issue solved.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390 helped me out.

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?

Oneplus soft bricked only hang on logo data are most important please guide

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.

Categories

Resources