In an attempt to unroot my OP3 I managed to (almost?) brick it. Fastboot still works so I could flash back TWRP which I already had replaced by the stock recovery. Also I have a backup available on the phone which I hoped to be able to restore. And here is where my problem comes in: I cannot choose any partition to restore because there are none and hence the restore fails with "No partitions selected for restore.".
What can I do now? Originally I was trying to sideload the current Oxygen OS using the stock recovery but that didn't work. Any ideas?
simu_lacrum said:
In an attempt to unroot my OP3 I managed to (almost?) brick it. Fastboot still works so I could flash back TWRP which I already had replaced by the stock recovery. Also I have a backup available on the phone which I hoped to be able to restore. And here is where my problem comes in: I cannot choose any partition to restore because there are none and hence the restore fails with "No partitions selected for restore.".
What can I do now? Originally I was trying to sideload the current Oxygen OS using the stock recovery but that didn't work. Any ideas?
Click to expand...
Click to collapse
Your not bricked at all. Just stuck with a phone without OS I think? Why does ADB sideload not work? Do you get the "cannot read" error? Use adb push file directory then manually flash it with twrp. Make sure you are in the latest one from Bluspark!
Yes, I'm stuck with a phone without OS. I did get the "cannot read" error but I don't know why because all the necessary files were in the very same directory from where I issued the adb commands. Where do i find or define an adb push file directory? Currently I habe TWRP 3.0.3-0. installed. Will that be sufficient?
Please keep in mind that I've also lost my partition information. adb sideload alfeady didn't work before that because of the "cannot read" error. Still I don't know what's the reason for that error.
Here you will find everything you need to recover your phone:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Related
Hi guys,
I've been running custom AOKP rom and decided to return back to stock.
I have the rogers version of the M8, and intended to flash a stock TWRP backup of someone's rogers save.
I made the poor decision of relocking and unlocking the bootloader again, leaving me without a functional OS and with only fastboot and TWRP recovery available to me. As a result, I can't get the rogers backup folder onto my phone ( I don't have a miscro SD), and the only other option I see is to manually push each file in the stock TWRP recovery with ADB to my phone, but I'm horrible with anything that involves command lines.
Any suggestions to get me out of this situation would be great. My end goal is to get the stock ROM / kernel running so I can get OTA's.
Edit: Solved by doing an advanced wipe and format in TWRP, and I flashed a stock Rogers nandroid
Just adb push or adb sideload a stock rooted ROM to your phone. Just a single command line.
If you want OTAs, you will also need stock recovery. But my recommendation is that OTAs have no place on a modded device.
redpoint73 said:
Just adb push or adb sideload a stock rooted ROM to your phone. Just a single command line.
If you want OTAs, you will also need stock recovery. But my recommendation is that OTAs have no place on a modded device.
Click to expand...
Click to collapse
I've tried flashing a ROM and unfortunately I get stuck on the boot animation.
Attempting to wipe my phone through TWRP before the zip install yields a failure:
E: Unable to mount '/data'
E: Unable to mount internal storage
Those two lines are repeated a couple times in the error screen.
It looks like I need to flash some form of backup but am not sure which one will hard reset my phone to stock from this scenario.
Flashnova said:
I've tried flashing a ROM and unfortunately I get stuck on the boot animation.
Click to expand...
Click to collapse
Which ROM? How did you try to flash it (how did you get it on the phone, did you adb sideload?)/
Flashnova said:
Attempting to wipe my phone through TWRP before the zip install yields a failure:
E: Unable to mount '/data'
E: Unable to mount internal storage
Click to expand...
Click to collapse
Select "Mount" in TWRP main screen and make sure data is checked (cache should also e checked by default). If so, and still getting this error, di you by chance try to factory reset in bootloader (not TWRP)?
redpoint73 said:
Which ROM? How did you try to flash it (how did you get it on the phone, did you adb sideload?)/
Select "Mount" in TWRP main screen and make sure data is checked (cache should also e checked by default). If so, and still getting this error, di you by chance try to factory reset in bootloader (not TWRP)?
Click to expand...
Click to collapse
I flashed dirty unicorns 4.4.4. I had a 2gb SD card which managed to get it to the phone (the 2gb isn't enough to move the system backup).
I can't check Mount in the settings and it remains unchecked, and yes, I did hit the factory reset in the bootloader thinking that it would help me (I assume this was another bad decision).
Flashnova said:
I can't check Mount in the settings and it remains unchecked, and yes, I did hit the factory reset in the bootloader thinking that it would help me (I assume this was another bad decision).
Click to expand...
Click to collapse
Yes, that was a bad decision. But probably not one that you could have known about. Doing a factory reset in bootloader on a modded M8 corrupts the internal memory. This is your main problem right there.
If you have a Windows PC, connect the phone, go to Device Manager and find the phone. Then select the option to format the memory.
In the future only do a factory reset within the OS (in Settings) or in recovery, not in bootloader.
If you've gone through this much, I'd highly recommend getting comfy with a few command line commands. These may very well save you some time and additional headache (speaking from experience).
After recently running into issues with my newly purchased Roger's M8, I needed to restore to stock as well. Honestly, I followed these instructions to the T and it got me out scrape-free.
But, note Step #6 may require you to "adb push" your unzipped folder. And that's it.
Once you've ADB'd the massive nandroid backup, you should be out of the woods (in TWRP, Restore, Select the pushed backup file).
Good luck, and as long as you've got recovery/hboot looking back at you, you should be fine.
redpoint73 said:
If you have a Windows PC, connect the phone, go to Device Manager and find the phone. Then select the option to format the memory.
Click to expand...
Click to collapse
I'm not too sure where that option is located, would you know how to get there?
esuohe said:
But, note Step #6 may require you to "adb push" your unzipped folder. And that's it.
Once you've ADB'd the massive nandroid backup, you should be out of the woods
Click to expand...
Click to collapse
After pushing the folder to my device I receive "protocol failure", so the push isn't working unfortunately.
Flashnova said:
I'm not too sure where that option is located, would you know how to get there?
Click to expand...
Click to collapse
On Win7, go to Start Menu, use the search function at the bottom that says "Search programs and files" and type "Device Manager".
Or go to Start Menu>Control Panel>Hardware and Sound; and under "Devices and printers" you will see Device Manager.
Flashnova said:
After pushing the folder to my device I receive "protocol failure", so the push isn't working unfortunately.
Click to expand...
Click to collapse
You aren't going to be able to write to the memory when its still corrupt.
redpoint73 said:
On Win7, go to Start Menu, use the search function at the bottom that says "Search programs and files" and type "Device Manager".
Or go to Start Menu>Control Panel>Hardware and Sound; and under "Devices and printers" you will see Device Manager.
Click to expand...
Click to collapse
Device manager does not provide a format option. Perhaps you mean disk manager? If I do format it will I have to somehow reinstall the android system?
Flashnova said:
Device manager does not provide a format option. Perhaps you mean disk manager? If I do format it will I have to somehow reinstall the android system?
Click to expand...
Click to collapse
I've often read it described as Device Manager. Can't personally say from experience as I've never actually had to do it myself, but seen this described on XDA quite a few times. If the option comes up in Disk Management, that should be fine, too.
Formatting internal storage should not affect the Android OS, as its a separate partition (note how Windows is only reading the internal storage as around 25 GB of the total 32 GB). But you have to re-install a ROM anyway, as you presently do not have one installed.
I recently picked up a new-to-me LS970 after an unfortunate encounter with gravity :/
I went to root/unlock the phone and all seemed to go well. I loaded TWRP 2.6.3.0 and proceeded to make a backup of my stock rom/settings/ESN. I then attempted to flash a new ROM and found that the MIUI port wasn't functional for me. I tried to flash CM12 as well but cannot get past the setup wizard.
Unfortunately, TWRP doesn't recognize my backup. If I go to the file manager, I can see the directory and files that compose my backup, but if I go to restore it, I get a blank menu with no restore options.
The ADB sideload option fails to connect (It says 'Starting ADB sideload feature...' forever until I cancel it) and I cannot get far enough into either ROM to enable me to push files over MTP. in CM12, I can get ADB to see my phone (appears when I use 'ADB devices') but if fails to push a file due to permission being denied.
What are my options here? How can I move forward with having a functional phone?
I was able to tinybin my way back to TWRP 2.6.0.0 and that has allowd me to ADB push files. Sideload still will not function. I tried flashing several ROMs but they always fail. I treid reformating my SD card, and that also fails (unable to read partition table). Any guess as to what is going on? MIUI successfully works now, so at least I'm through the worst of it.
LordKyleOfEarth said:
I recently picked up a new-to-me LS970 after an unfortunate encounter with gravity :/
I went to root/unlock the phone and all seemed to go well. I loaded TWRP 2.6.3.0 and proceeded to make a backup of my stock rom/settings/ESN. I then attempted to flash a new ROM and found that the MIUI port wasn't functional for me. I tried to flash CM12 as well but cannot get past the setup wizard.
Unfortunately, TWRP doesn't recognize my backup. If I go to the file manager, I can see the directory and files that compose my backup, but if I go to restore it, I get a blank menu with no restore options.
The ADB sideload option fails to connect (It says 'Starting ADB sideload feature...' forever until I cancel it) and I cannot get far enough into either ROM to enable me to push files over MTP. in CM12, I can get ADB to see my phone (appears when I use 'ADB devices') but if fails to push a file due to permission being denied.
What are my options here? How can I move forward with having a functional phone?
Click to expand...
Click to collapse
LordKyleOfEarth said:
I was able to tinybin my way back to TWRP 2.6.0.0 and that has allowd me to ADB push files. Sideload still will not function. I tried flashing several ROMs but they always fail. I treid reformating my SD card, and that also fails (unable to read partition table). Any guess as to what is going on? MIUI successfully works now, so at least I'm through the worst of it.
Click to expand...
Click to collapse
If it is your original TWRP backup (TWRP that Freegee installed) it might not restore, I had that problem a long time ago. Try installing an updated TWRP, that one is really old at this point.
If you have an updated TWRP you can mount MTP from recovery and transfer any files to your internal storage. I suggest starting out with the stock ZVC so you can have a fully working stock device and make sure everything works. From there you can copy zips to your device and flash away.
If you have issues copying a recovery to your device you can always use adb to flash. I believe it is
"fastboot flash recovery (name of recovery.img)" without quotes or parenthesis.
EDIT: On the CM 12 setup thing, @Shelnutt2 just posted in the CM12 thread that the bug is fixed and will be pushed to tonight's nightly.
Here is a newer recovery built by an international dev but this is the one I used when I had the OG.
http://dl.kevinjoa.me/recovery-geehrc/twrp/
Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.
Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.
Here's my situation:
I was attempting to sideload a custom rom (AICP) onto my Z1C.
I successfully wiped the device and sideloaded AICP and Open Gapps.
But then, like an idiot, I rebooted, with no OS installed.
Did I brick the device? Or is there some way I can still get it to install the zip file that's on there?
Right now I'm trying the ADB install command, but I keep getting "error: no devices found".
Is this the end of this device????
Wait... I reflashed the boot img and was able to get back to TWRP Recovery. Now I'm going to attempt sideload again but I WON'T REBOOT BEFORE I INSTALL
Ok, sorry for freaking out there. I'm back in TWRP and sideloadin successfully, except....
I can't find the sideloaded files now that I want to install them? Where do they go?
I don't have a MicroSD card at the moment.