Related
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
callison.168 said:
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
Click to expand...
Click to collapse
It seems your boot.img file either corrupted or missing.
Find a working copy of file, flash it via ADB interface or fastboot. Flash recovery file CWM. If that doesnt work, Try flashing CM7 Rom or someother ROM.
Did you check http://forum.xda-developers.com/showthread.php?t=895545 ?
Odin should be your last resort, if nothing really works for you.
If you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 .
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
Download your rom of choice (stock, custom)
Flash Cwm via fastboot if you haven't already
Boot into recovery.
Use adb push to push your zipped rom to the sdcard (adb push file.zip /sdcard/file.zip)
Use cwm to flash this zip.
Sent from my Nexus S using xda premium
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=9866675
http://forum.xda-developers.com/showthread.php?t=884093
These threads should be a complete solution to your issue.
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Wow fast responses. I bet it's annoying to help yet another person having issues (again, phone was given to me like this but yeah...) while you guys or gals already know how to do these things very well. Here's where I'm stuck. I enter this code in cmd:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
and it just says < waiting for device >.
Here's a pic of the screen that I'm on with my phone when i enter the command.
http://imgur.com/Pey3W
If I'm just in the first screen by holding volume up and power, the computer won't read the phone. So I click recovery, the screen shows it's trying to install something then the triangle exclamation mark, i press volume up/down with power and get this screen and the computer can "see" my phone on cmd.
How do I get this flipping clockwork on this phone or get the stock image on my sd card? Thanks again for helping me out guys. I have taken a look at the links you have sent me and that's where i found the download as well as the code to enter. I will keep looking at them but if you find a faster solution, please let me know.
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
callison.168 said:
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
Click to expand...
Click to collapse
So you already tried "fastboot devices" while in fastboot mode?
Edit: Actually it sounds you really want stock so download the complete stock OTA ROM (including boot.img etc.), rename it to update.zip and put it on the root of your sdcard. Boot into the stock recovery like you did already and hit apply update.
EDIT: Go here to download the correct OTA http://forum.xda-developers.com/showthread.php?t=1056062
Find the correct 2.3.6 "Full ROM" for your phone model. Sounds like in those instructions you don't need to rename to update.zip. Haven't seen stock recovery for a while so I don't remember.
If there is a wipe option in the stock recovery then do that first.
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Also, I can't get the phone to boot at all, like I can't get passed the Google Logo if I reboot so I can't access the sdcard in the traditional way.
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
If fastboot devices returns NOTHING then this is most likely a driver issue. Remove the device through device manager, make sure you have a recent SDK (for the USB driver) and let it re-detect.
callison.168 said:
Also, I can't get the phone to boot at all, like I can't turn on the phone so I can't access the sdcard in the traditional way.
Click to expand...
Click to collapse
If you can get into the boot loader and get a proper USB driver you should be able to flash a recovery.
Once you've flashed Clockwork Mod (recovery) you'll be able to push to the sdcard using ADB or possibly mount the sd card through the CWM menu (although I've yet to have that work).
In order to get a recovery flashed though you need to get fastboot to see your device (unless you can already boot into recovery, then just use ADB).
irishrally said:
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
Click to expand...
Click to collapse
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
krohnjw said:
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
Click to expand...
Click to collapse
He said he can access stock recovery and has connected with adb, unless I read wrong.
irishrally said:
He said he can access stock recovery and has connected with adb, unless I read wrong.
Click to expand...
Click to collapse
Indeed - I saw no clockwork and figured he'd toasted his recovery image as well, but it does look like stock recovery is there. ADB should push fine to the sdcard from recovery then.
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
That noise is that it detects a device has been connected (assuming a recent version of windows). If you want to flash CWM you need to get the driver sorted for the device. No amount of plugging/unplugging is going to fix it.
If you have the stock recovery you can boot into the stock recovery, use adb to push the full OTA package to the sd card and then just flash that from the stock recovery.
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
Go to the stock recovery like you have done before and type the adb command I wrote above.
Thanks is all I can say. Okay so when I type in the command, this is what I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
the "stock recovery" I can get into is the picture I posted a link for. That's what I can access as well as the fastboot mode when I first turn on the phone with volume up/power. But when my computer makes the noise that it's connected (using Windows 7 64bit) it makes a different sound then the normal "device connected." Like it's corrupted.
by the way...if we can get this working, I'll post a picture of me holding the fixed phone!
I just rooted my phone last night. I tried to flash cynanogen 10 and forgot to back up the the stock rom. I haven't done this since my last phone. But I got stuck at the cynanogen bootloader screen. I tried to get back to recovery mode but it won"t go. Can someone please help me and give very detailed instructions to get my phone unbricked pleeeeease? I don"t want to to buy another phone. Thank you.
How long did u wait at boot logo screen first boot can take a while and did u flash boot. Img? Are u t mob?
Sent from a man, using a mobile phone
1. Wipe
2. Flash
3. Wipe cache
4. Fastboot boot.IMG
5. Boot
6. Reboot
7. Flash gapps
8. Wipe cache
9. Enjoy the speed
Note this method will only work for hboot under 1.13
k1llacanon said:
How long did u wait at boot logo screen first boot can take a while and did u flash boot. Img? Are u t mob?
Sent from a man, using a mobile phone
Click to expand...
Click to collapse
All I know is that I downloaded the ROM from here, used CWM to flash it on, phone said update installed and rebooted the phone. I waited for an hour and it still did nothing past the bootload screen. Also, yes I'm t-mobile.
Fredfly said:
1. Wipe
2. Flash
3. Wipe cache
4. Fastboot boot.IMG
5. Boot
6. Reboot
7. Flash gapps
8. Wipe cache
9. Enjoy the speed
Note this method will only work for hboot under 1.13
Click to expand...
Click to collapse
If I can't get into recovery, how do I do this, or what can I use to do this?
Fredfly said:
1. Wipe
2. Flash
3. Wipe cache
4. Fastboot boot.IMG
5. Boot
6. Reboot
7. Flash gapps
8. Wipe cache
9. Enjoy the speed
Note this method will only work for hboot under 1.13
Click to expand...
Click to collapse
I have hboot 1.14
Can get ur phone into bootloader mode or fastboot...if yea...then u cn save ur phone...i faced the same problem some days back...and successfully recovered my phone and nw i am using energy rom...
Sent from my HTC VLE_U using xda app-developers app
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Ruwin said:
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Click to expand...
Click to collapse
Ok, I downloaded the sdk and my computer recognizes the phone, and I can get into recovery mode, I did a factory reset but it did nothing.
Ruwin said:
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Click to expand...
Click to collapse
It keeps telling me device not ready
marcus8141981 said:
I just rooted my phone last night. I tried to flash cynanogen 10 and forgot to back up the the stock rom. I haven't done this since my last phone. But I got stuck at the cynanogen bootloader screen. I tried to get back to recovery mode but it won"t go. Can someone please help me and give very detailed instructions to get my phone unbricked pleeeeease? I don"t want to to buy another phone. Thank you.
Click to expand...
Click to collapse
I git it fixed. I thank everyone for their help.
marcus8141981 said:
It keeps telling me device not ready
Click to expand...
Click to collapse
Can you give me more details? Where do you see that message and when exactly? Maybe an ADB logcat?
If you can get into fastboot usb, you can easily google for flashing solutions using fastboot.
always good to say how you fixed it for others who may have similar issue--
Ruwin said:
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Click to expand...
Click to collapse
I do that and my phone just keeps flickering and goes back in to cwm recovery. Please any ideas?
Purchased an Lg Gpad 7 Wifi tablet (v400) 2 weeks ago. Came with preinstalled Lollipop android so i couldnt install a recovery rom to flash any other custom roms. Downgraded to Kitkat version following the instructions on Xda forums and succesfully installed Twrp. When i installed Cyanogenmod 12.1 through Twrp i got stuck in fastboot screen.
Any suggestions and / or solutions would be greatly appreciated.
I had a similar problem.. Only mine was stuck at the bootloader. Go in TWRP and repair /data and other partitions. My data partition gave me an error since F2FS is a little flaky and some ROMs corrupted it (claimed they supported it). I would recommend erasing the system, cache and data partition if you can't get into TWRP.
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Hakalai said:
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Click to expand...
Click to collapse
if you have an sd card, try removing that, then reboot.
if that doesnt work, try entering fastboot command, fastboot continue
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Hakalai said:
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Click to expand...
Click to collapse
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
bweN diorD said:
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
Click to expand...
Click to collapse
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Hakalai said:
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Click to expand...
Click to collapse
hmm, ok, im guessing it would have said that normally, when not broken. all the command does is try to release it past where its stuck. it doesnt actually flash, lock, unlock, or change anything.
imo, this seems good, because now we know fastboot is working.
i own lg devices, but not your specific device. i would hate to give you some bad advice and make your tablet broken more, but if it were me in this situation, i would try to flash the factory KK firmware you used to downgrade with odin or however you did it. hopefully, that will clean everything up and let it boot properly.
if for whatever reason you cant do that, we could try extracting the factory file, and just flashing recovery and system, those should be the only things that got changed putting on twrp and cm normally.
Sorry, I have the serious proplem wtih my LG pad V400, I rooted it and using <LG Flash Tool 2014> with <V40010c_00.kdz> to downgrate the firmware but their is error then my LG pad stuck in fastboot menu as with just turn off, restart and restart bootloader. if i seclect one one them the tablet just logged again the fastboot menu
it stuck on the fastboot menu and i cannot do nay think with it. I can restart with factory restore mode but when select yes to restore, it will restart and log in fastboot menu again.
I downloaded adb and fastboot program and put in one folder <Minimal ADB and Fastboot> in C:\Program Files (x86)\Minimal ADB and Fastboot
I dont have recovery image so i download file <cm-13.0-20160421-NIGHTLY-v400-recovery.img> form your link to download TWRP file
move it to folder of fastboot programe and changed its name to <recovery.img>
I turn on the tablet and it waited at fastboot menu
when i run the command <fasboot flash recovery recovery.img> and they said some thing wrong like in picture
please help me
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 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.