I was using Mahdi rom , I have backup off all my roms ( cm11s stock 38r, Mahdi backup, pa rom backup). I also multirom with 3 secondary rom.
Ok, I swap my Mahdi rom with liquid smooth rom, so liquid smooth is my primary, didn't like it so I backup, restore cm11s 38r used it. Until now I reboot into recovery and swap 38r with Mahdi rom what I started in the beginning. Reboot it was stuck at the oneplus logo to a long time. Happen before to me and usually just hold the volume down and power it would be fine, when I did it this time it didn't work and it would end back in the oneplus logo. So I boot in to recovery then I notice everything is gone. No OS, no multirom, nothing in my restore. How do I get my phone running again. I know it's a long shot but my data like photo are gone or can I get them back? Haha
Don't know what to do, please thanks you.
if you can get into fastboot then it can be saved. simply boot recovery twrp and mount your phone as a drive. Then copy over your rom files and flash them.
Geo411m said:
if you can get into fastboot then it can be saved. simply boot recovery twrp and mount your phone as a drive. Then copy over your rom files and flash them.
Click to expand...
Click to collapse
how do i mount my phone as a drive in twrp? i cant seem to find it.
i could get in to fastboot mode, but dont know what to do from there. i see a few but are different from each other, so i didnt want to take the risk trying it.
chailee said:
how do i mount my phone as a drive in twrp? i cant seem to find it.
i could get in to fastboot mode, but dont know what to do from there. i see a few but are different from each other, so i didnt want to take the risk trying it.
Click to expand...
Click to collapse
Once you're in TWRP go to mounts and at the bottom right you'll see enable MTP. Click it and it should put your phone in USB mode. Now you should be able to copy your files to your phone to flash them without losing data.
This is what I did
chailee said:
I was using Mahdi rom , I have backup off all my roms ( cm11s stock 38r, Mahdi backup, pa rom backup). I also multirom with 3 secondary rom.
Ok, I swap my Mahdi rom with liquid smooth rom, so liquid smooth is my primary, didn't like it so I backup, restore cm11s 38r used it. Until now I reboot into recovery and swap 38r with Mahdi rom what I started in the beginning. Reboot it was stuck at the oneplus logo to a long time. Happen before to me and usually just hold the volume down and power it would be fine, when I did it this time it didn't work and it would end back in the oneplus logo. So I boot in to recovery then I notice everything is gone. No OS, no multirom, nothing in my restore. How do I get my phone running again. I know it's a long shot but my data like photo are gone or can I get them back? Haha
Don't know what to do, please thanks you.
Click to expand...
Click to collapse
I had a similar issue with a OPO I purchased from a “non-technical” person on CL. I looked high and low for the answer but nobody had the exact same problem. Your issue sounds almost exactly like mines. Here are the specifics…..
Issue: The phone’s OS was gone and it would just sit at the OPO logo splash screen.
Note: I was able to get into fast boot mode. I was also able to get into TWRP. I was not able to unlock the bootloader. The phone wouldn’t let me make system chances because the bootloader was locked. The OEM unlock command never worked for me.
Fix:
-I downloaded the drivers for the oneplus one. If you don’t already have them, you’ll find various links on XDA to point you in right direction.
-I downloaded the stock cyanogen 11 image from the OPO website.
-I downloaded the a file called "OnePlusOne-BootUnlocker.zip”
-I booted the phone into TWRP and used the command line to push the "OnePlusOne-BootUnlocker.zip" to the phone…….
adb push OnePlusOne-BootUnlocker.zip
-Once I did this, the file showed up in TWRP. I selected the file and ran it. This unlocked my bootloader. Once the bootloader is unlocked, you can actually push the stock image back to the phone.
-I downloaded the image file called cm-11.0-XNPH33R-bacon-signed-fastboot_64GB.zip (i have the 64gb model)
-I booted the phone into TWRP and pushed the stock image to the phone (i used the same push command I used to push the bootunlocker file) The file appeared in TWRP and I ran it. It installed the stock image on the phone.
NOTE: I am not a developer. I’m just an IT guy who played around for a day or so and fixed it myself. I didn’t see anyone with the exact same problem as me so I took bits and pieces from other solutions and created my own. I’m sure there’s a developer looking at this like WTF but this is what worked for me.
Geo411m said:
Once you're in TWRP go to mounts and at the bottom right you'll see enable MTP. Click it and it should put your phone in USB mode. Now you should be able to copy your files to your phone to flash them without losing data.
Click to expand...
Click to collapse
when i click enable mtp, doesnt work.
Jokool_7777 said:
I had a similar issue with a OPO I purchased from a “non-technical” person on CL. I looked high and low for the answer but nobody had the exact same problem. Your issue sounds almost exactly like mines. Here are the specifics…..
Issue: The phone’s OS was gone and it would just sit at the OPO logo splash screen.
Note: I was able to get into fast boot mode. I was also able to get into TWRP. I was not able to unlock the bootloader. The phone wouldn’t let me make system chances because the bootloader was locked. The OEM unlock command never worked for me.
Fix:
-I downloaded the drivers for the oneplus one. If you don’t already have them, you’ll find various links on XDA to point you in right direction.
-I downloaded the stock cyanogen 11 image from the OPO website.
-I downloaded the a file called "OnePlusOne-BootUnlocker.zip”
-I booted the phone into TWRP and used the command line to push the "OnePlusOne-BootUnlocker.zip" to the phone…….
adb push OnePlusOne-BootUnlocker.zip
-Once I did this, the file showed up in TWRP. I selected the file and ran it. This unlocked my bootloader. Once the bootloader is unlocked, you can actually push the stock image back to the phone.
-I downloaded the image file called cm-11.0-XNPH33R-bacon-signed-fastboot_64GB.zip (i have the 64gb model)
-I booted the phone into TWRP and pushed the stock image to the phone (i used the same push command I used to push the bootunlocker file) The file appeared in TWRP and I ran it. It installed the stock image on the phone.
NOTE: I am not a developer. I’m just an IT guy who played around for a day or so and fixed it myself. I didn’t see anyone with the exact same problem as me so I took bits and pieces from other solutions and created my own. I’m sure there’s a developer looking at this like WTF but this is what worked for me.
Click to expand...
Click to collapse
doesnt work for me, when i boot my phone into twrp, i cant push anything to phone. i pretty sure i got all the files need.
instead of going through twrp, can i do everything in fastboot? and flash the zip file?
Hope this will do it......
chailee said:
doesnt work for me, when i boot my phone into twrp, i cant push anything to phone. i pretty sure i got all the files need.
instead of going through twrp, can i do everything in fastboot? and flash the zip file?
Click to expand...
Click to collapse
NOTE: I apologize, I dont think I specified that it should be pushed to the SD Card. This should be done FIRST for the bootunlocker file and then the Stock Cyanogen file.
Try it like this.........
Turn the phone off then boot into recovery mode by holding volume down + power. Leave the phone at the main screen of the custom recovery for now.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools (This location will be specific to your pc and will change depending on where the file is located and how you have it named)
Code:
adb push ***INSERT FILE HERE*** /sdcard/
Related
First time post and it's been a hell of a day. I need to figure out how to either sideload the factory ROM, load a 3rd party ROM, or actually factory reset my phone to stock.
I unlocked my bootloader and installed TWRP and SuperSU earlier in the day. I then wanted to try to load Cyanogen11, but there were issues with the load, it constantly failed. I made a backup before I did this, but when I attempted to load the backup, nothing happened, it would just continually boot to recovery.
I attempted a few other things, clearing caches, doing wipes, powering the phone off for 5~ minutes, etc. etc.
Nothing is working, I can't load any ROM now and phone is either stuck at a bootcycle or the HTC Splash screen (Aside from being able to load bootloader/CWP)
jdolbeer said:
First time post and it's been a hell of a day. I need to figure out how to either sideload the factory ROM, load a 3rd party ROM, or actually factory reset my phone to stock.
I unlocked my bootloader and installed TWRP and SuperSU earlier in the day. I then wanted to try to load Cyanogen11, but there were issues with the load, it constantly failed. I made a backup before I did this, but when I attempted to load the backup, nothing happened, it would just continually boot to recovery.
I attempted a few other things, clearing caches, doing wipes, powering the phone off for 5~ minutes, etc. etc.
Nothing is working, I can't load any ROM now and phone is either stuck at a bootcycle or the HTC Splash screen (Aside from being able to load bootloader/CWP)
Click to expand...
Click to collapse
Are you still having issues? If so, PM me and I'll help you out.....
Got everything sorted with the great help of Nelvin. I had previously gone to the twrp support IRC and after answering a few questions, they just stopped talking... Glad there are people out there still willing to help! He spent a good hour or so with me making sure everything was working.
Hey you two!
Did you solve your problem via PM, then maybe send me the log of it please.
I dont know exactly if we have the same problem, but i'll try to explain mine:
I wanted to put a ROM on my mini, because it is branded.
I unlocked the bootloader on the htc one mini and then put the twrp recovery on it. It seems to work.
Next i wanted to put super su on it, but I'm already stuck in a bootcircle, so i cant put any files onto the phone. I tried to move files with Qick ADB Pusher, but always when I try to send the file from PC(win7) to one mini it says "Opeartion Failed! Exit Code 1". I tried this when i was in Bootloader. When I am in Recovery ADB doesnt even recognize the phone via USB.
If there is more explanation needed, please feel free to ask.
Thank you for your help in advance!
Greetins,
just2lose.
just2lose said:
Hey you two!
Did you solve your problem via PM, then maybe send me the log of it please.
I dont know exactly if we have the same problem, but i'll try to explain mine:
I wanted to put a ROM on my mini, because it is branded.
I unlocked the bootloader on the htc one mini and then put the twrp recovery on it. It seems to work.
Next i wanted to put super su on it, but I'm already stuck in a bootcircle, so i cant put any files onto the phone. I tried to move files with Qick ADB Pusher, but always when I try to send the file from PC(win7) to one mini it says "Opeartion Failed! Exit Code 1". I tried this when i was in Bootloader. When I am in Recovery ADB doesnt even recognize the phone via USB.
If there is more explanation needed, please feel free to ask.
Thank you for your help in advance!
Greetins,
just2lose.
Click to expand...
Click to collapse
Hi, can you let me know: Which ROM you want to flash, if you have attempted to s-off, and that you can boot to recovery?
Also, i'd advise against using utilities like the "pusher", please download this http://d-h.st/qmi and create a directory called c:\adb\ - move your ROM and SuperSU zip files here and extract the adb_windows.zip file to the directory.....
I did not attempt s-off, just normal htc dev bootloader.
First i wanted to flash Magio R4, but then i was thinking about Stock Rom Sense 5.5, which tr1gg3r84 uploaded.
i created folder and moved rom there. i also extracted the adb_windows zip there. what to do next? (i just wanna ask, because im a little scared of totaly breaking the phone now)
Thanks for now!
just2lose said:
I did not attempt s-off, just normal htc dev bootloader.
First i wanted to flash Magio R4, but then i was thinking about Stock Rom Sense 5.5, which tr1gg3r84 uploaded.
i created folder and moved rom there. i also extracted the adb_windows zip there. what to do next? (i just wanna ask, because im a little scared of totaly breaking the phone now)
Thanks for now!
Click to expand...
Click to collapse
Boot to recovery, then
adb push therom.zip /sdcard/
adb push UPDATE-SuperSU.zip /sdcard/
Remember to extract the boot.img from the ROM zip file, and after flashing the ROM and SuperSU, boot to bootloader and FASTBOOT menu then:
fastboot flash boot boot.img
you mean to push with the quick ADB Pusher? but in this programm (on PC) it doesnt find the phone whilie it is is recovery boot.
just2lose said:
you mean to push with the quick ADB Pusher? but in this programm (on PC) it doesnt find the phone whilie it is is recovery boot.
Click to expand...
Click to collapse
No, use the adb binary from the download link I posted......
If your phone isn't found, check the windows device manager and verify that you have ADB Android device listed..... if not, download adb drivers for windows and install - then plug your phone back in.....
You are using TWRP 2.6.0.0 recovery image from here right? http://forum.xda-developers.com/showthread.php?t=2418938
the adb.exe just pops up the cmd console, showing a lot of commands for half a second and then its gone again.
the android device is listed on device manager.
no, i did not use this one(twrp). i used some explanation how to do it from another forum and another file.
should i use this one now? how exactly to do that? theres no explanation :/
Open a command prompt in Windows and cd to c:\adb
Then when your phone is in recovery, type the adb commands I posted earlier.....
Sent from my HTC One mini using XDA Premium 4 mobile app
terdingb all
cmd says that the command is wrong or misstyped
(im in c:/adb typing: adb push rom.zip /sdcard/)
Is your ROM zip file called rom.zip? Can you post a screenshot?
Sent from my HTC One mini using XDA Premium 4 mobile app
ok got it.
now the rom and the supersu.zip are on the phone.
i cleared cache and dalvik and flashed both files(Stock Sense 5.5 4.3 Rooted Odex/Deodex;UPDATE-SuperSU-v1.86; both zip files) and , after that i went into fastboot and tried (fastboot folder) "fastboot flash boot boot.img" but cmd only says "waiting for device"
just2lose said:
ok got it.
now the rom and the supersu.zip are on the phone.
i cleared cache and dalvik and flashed both files(Stock Sense 5.5 4.3 Rooted Odex/Deodex;UPDATE-SuperSU-v1.86; both zip files) and , after that i went into fastboot and tried (fastboot folder) "fastboot flash boot boot.img" but cmd only says "waiting for device"
Click to expand...
Click to collapse
Check device manager on your pc, most likely the adb driver device isn't listed - if not, reboot your pc and try again.... This has happened to me several times......
ok now it worked. writing boot and so on .. finished. total time: 2.717.
i shut it down and started the phone again.
now it almost made the starting sound. after 5 boot cycles it played the whole starting sound and also showed the second screen with the "o1ne" and "beatsaudio" on the bottom.
but thats it. boot cycling in a different way now .
seems like it just doesnt want to work.
i'm so sorry that I am bothering you for so long now..
another idea?
thanks again!
edit: im gonna go through everything again with magio rom r5...
ok got it now. thanks a lot dude!
i deleted the rom files now from the phone but still there is 9gb used on the phone. this is way to much, isnt it?
is there a safe method to clean the whole phone .. something like c:format ?
thanks ³
No problem dood.....
Download an app called diskusage from the store - start it and choose storage card.... Post a screenshot please!
Sent via a weather balloon towed by a flock of seagulls. That's how this messaging stuff works, right?
after the phone went out of battery, it was in a boot cycle again after loading and rebooting.
flashed super su.zip again, but it didnt help. stupid me didnt do a backup yet. so do i have to install the rom again and do all the configs from scretch?
What's your hboot status? Locked/unlocked, s-on/s-off etc
Also, did you do, or install anything before your phone powered off?
Sent from my HTC One mini using XDA Premium 4 mobile app
So I forgot and did a dirty flash to the final version of Lollipop without wiping data. I should have moved my data over but now I'm stuck with a black screen and a back arrow once I boot up the OS.
I know that in order to fix this, I need to flash again and do a full wipe, however, I need to get my files (pics and music) off the phone. I am unable to put a custom recovery on the phone. When I flash TWRP to the phone, it says it succeeded but then I just get the open android with the red thing on it when I try to go to recovery mode.
I've tried adb pull in fastboot mode, but I am unable to get my computer to recognize my device in fastboot mode through adb (fastboot works of course).
When I've booted up, my lock is on the phone so I cannot use adb to pull files without getting into the OS (which is impossible at this point).
I'm running out of ideas on how to get the files, but I'm sure that someone here must have run into the same issue.
Any assistance would be appreciated.
wangkomi said:
So I forgot and did a dirty flash to the final version of Lollipop without wiping data. I should have moved my data over but now I'm stuck with a black screen and a back arrow once I boot up the OS.
I know that in order to fix this, I need to flash again and do a full wipe, however, I need to get my files (pics and music) off the phone. I am unable to put a custom recovery on the phone. When I flash TWRP to the phone, it says it succeeded but then I just get the open android with the red thing on it when I try to go to recovery mode.
I've tried adb pull in fastboot mode, but I am unable to get my computer to recognize my device in fastboot mode through adb (fastboot works of course).
When I've booted up, my lock is on the phone so I cannot use adb to pull files without getting into the OS (which is impossible at this point).
I'm running out of ideas on how to get the files, but I'm sure that someone here must have run into the same issue.
Any assistance would be appreciated.
Click to expand...
Click to collapse
theres no adb in the bootloader, just fastboot.
i dirty flashed from kitkat(rastakat rom) to lollipop, didnt have any issues at all. what did you dirty flash from? you could just flash the factory img via fastboot, but not flash the userdata.img, which would let you keep your data.
When you're in bootloader and try to flash TWRP (try the latest), make sure you hit reboot bootloader to see if that helps.
I went from the last pre-release to the official release. of lollipop.
I'm going to try twrp again see what I get.
Thanks
wangkomi said:
I went from the last pre-release to the official release. of lollipop.
I'm going to try twrp again see what I get.
Thanks
Click to expand...
Click to collapse
somebody posted a thread today about how to dirty flash from the preview to lollipop. it appears normally you cant.
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?
So today my new One Plus 6 arrived. I tested it out for a bit made sure everything seemed to be working ok.
Then I unlocked bootloader, flashed twrp, magisk, all without issue. (I followed a guide I found on google) While setting everything up, I noticed that there was an update avaliable. So I installed that and got a message that the update will remove root. I thought "ok, i'll just have to do that again after. Update installed, rebooted device to recovery and realize TWRP is also gone after the update. So then I rebooted again to the bootloader and do fastboot devices command on my pc. Phone is there. Next I do the fastboot flash boot twrp.img command.
Sending.. Writing.. Finished... But I was still on the bootloader on the phone. I tried it a couple more times with no result. Restarted the phone only to boot into TWRP now. I thought to myself "hmm I'm not sure that's what's supposed to happen" but I continued to flash twrp.zip anyway. Rebooted the device.. TWRP booted again. Tried rebooting a couple more times with the same result.
Now, maybe this is where I messed things up more seriously. I'll also mention I foolishly didn't perform a backup on TWRP before doing all this. Not sure what to do, I flashed magisk as well. And I tried rebooting system, then when that didn't work I think I rebooted "slot B' for some reason.... After that it would only show the oneplus boot animation for a seemingly indefinite period of time.
I found I could get int the bootloader menu by holding vol up and power. Tried flashing TWRP, seemed to work on my computer's end but didn't boot recovery on phone. I rebooted into recovery from bootloader menu, brought me to endless oneplus boot animation again. Selecting start on the boot loader booted to TWRP. From there I rebooted back to slot A. Now it boots straight into TWRP.
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.
Your not supposed to fastboot flash the twrp, youre supposed to fastboot boot it. Just reflash stock boot.img and you'll be good
usernameisausername said:
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.
Click to expand...
Click to collapse
A number of things work differently on this phone. Don't assume any of your previous knowledge transfers over. There is a steep learning curve.
Stay away from random guides on Google. There are reliable guides here that, if you follow them to the letter, will keep you out of trouble.
fastboot flash boot [.IMG]
Is the issue. Should be
fastboot boot [.IMG]
On www.twrp.me/Devices you'll find the OnePlus 6 plus a corresponding how-to, directly from the source.
Your best bet:
1. Download the full ROM zip from either OnePlus directly or one of the links here on XDA.
2. Download latest TWRP files from twrp.me
3. fastboot boot [.IMG]
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it)
5. Flash the ROM in TWRP as you would flash any other ROM.
6. Should work, your system is now back to stock (also recovery). Let it boot once to be sure and then retry magisk but with the right fastboot commands.
To flash TWRP permanently, move the installer.zip you find on TWRP.me to your phone, fastboot boot the .IMG and flash the installer.zip in recovery.
Let me know if it worked
schwarzerfleck said:
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it))
Click to expand...
Click to collapse
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.
iElvis said:
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.
Click to expand...
Click to collapse
Yeah that's why I suggested the ADB push
schwarzerfleck said:
Yeah that's why I suggested the ADB push
Click to expand...
Click to collapse
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all
Eilermoon said:
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all
Click to expand...
Click to collapse
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).
iElvis said:
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).
Click to expand...
Click to collapse
Thanks for the info! If anyone has a source for this, that'd be awesome
Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.
bump
xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.