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/
Hey all,
So, my smart self was attempting to flash Marshmallow 6.0 from 4.3 (rooted)...I did the same thing that was here on this THREAD and now my tab can only go into TWRP, but there's no OS installed because I wiped (and didn't make a darn backup....), but there are a few differences from the thread I referred to:
- I can get into my Bootloader
- I can get into TWRP
- I have the current TWRP 2.8.7
- I've tried the Nexus Toolkit from HERE, my device serial is recognized, but it states that I'm offline
- Because I'm offline, I can't push any files to my device through the tool
- When I'm in TWRP, my computer will recognize my tablet and I can actually get into folders and what not, but I can't copy/paste any files to flash within TWRP and I get an error
- Anytime I power down or reboot within TWRP, it tells me that I have No OS installed
- I can't use ADB (as far as I know) because my device shows that it's offline
Is there any hope that I can recover even back to 4.3?
Any guidance would really be appreciated. I have to step away because I'm frustrated and am angry at myself that I didn't make a nandroid.
Thanks in advance.
kevs888 said:
Hey all,
So, my smart self was attempting to flash Marshmallow 6.0 from 4.3 (rooted)...I did the same thing that was here on this THREAD and now my tab can only go into TWRP, but there's no OS installed because I wiped (and didn't make a darn backup....), but there are a few differences from the thread I referred to:
- I can get into my Bootloader
- I can get into TWRP
- I have the current TWRP 2.8.7
- I've tried the Nexus Toolkit from HERE, my device serial is recognized, but it states that I'm offline
- Because I'm offline, I can't push any files to my device through the tool
- When I'm in TWRP, my computer will recognize my tablet and I can actually get into folders and what not, but I can't copy/paste any files to flash within TWRP and I get an error
- Anytime I power down or reboot within TWRP, it tells me that I have No OS installed
- I can't use ADB (as far as I know) because my device shows that it's offline
Is there any hope that I can recover even back to 4.3?
Any guidance would really be appreciated. I have to step away because I'm frustrated and am angry at myself that I didn't make a nandroid.
Thanks in advance.
Click to expand...
Click to collapse
Are you using stock rom? Because if you are, I wouldn't even try. What with the widespread knowledge that stock might brick, some people insist on it. Otherwise, if you can get to the bootloader:
(1) Make sure it's unlocked (if you're not familiar, connect tab to PC, make sure fastboot works, then enter "fastboot oem unlocked" without the quotes then follow instructions on your tab);
(2) Flash bootloader 4.05 if you haven't already;
(3) Get a USB OTG thumb drive (you might need an OTG adapter for this); and download a Marshmallow-based custom rom in the Android Development section;
(4) Get into TWRP and mount USB OTG. You should see all the files on your thumb drive;
(5) Copy all data you care about to your PC;
(6) Wipe everything except USB OTG twice. Then go to Format and do it twice too. If yours is 32GB, it will take a while (30 Mins average depending on how much data);
(7) Flash rom, then Gapps.
You should be able to boot after that. Good luck.
(4)
graphdarnell said:
Are you using stock rom? Because if you are, I wouldn't even try. What with the widespread knowledge that stock might brick, some people insist on it. Otherwise, if you can get to the bootloader:
(1) Make sure it's unlocked (if you're not familiar, connect tab to PC, make sure fastboot works, then enter "fastboot oem unlocked" without the quotes then follow instructions on your tab);
(2) Flash bootloader 4.05 if you haven't already;
(3) Get a USB OTG thumb drive (you might need an OTG adapter for this); and download a Marshmallow-based custom rom in the Android Development section;
(4) Get into TWRP and mount USB OTG. You should see all the files on your thumb drive;
(5) Copy all data you care about to your PC;
(6) Wipe everything except USB OTG twice. Then go to Format and do it twice too. If yours is 32GB, it will take a while (30 Mins average depending on how much data);
(7) Flash rom, then Gapps.
You should be able to boot after that. Good luck.
(4)
Click to expand...
Click to collapse
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
kevs888 said:
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
Click to expand...
Click to collapse
It shouldn't make a difference what rom you flash now so long as you wipe and format everything inside TWRP. But you must make sure you have bootloader 4.05. 4.02 will not allow you to flash LL or MM successfully, and the system does not upgrade on its own no matter what rom you're flashing now.
Since you said you couldn't get TWRP to copy anything, I suggested that you use a thumb drive. Basically, if you turn the tab totally off, hold power + volume down for a few seconds, it should take you to the fastboot page (pic). Look to see what bootloader version you have there.
From here, you can basically flash anything. I recommended that you wipe and format first with TWRP because it happened to me a few times when for some reason, wiping alone still left some residual data that interfered with flashing newer roms.
Stay away from anything stock for the moment. God knows it has bricked more than a few devices. Download SkipsoftToolKit and flash from the fastboot page if you want an automated process. It has worked wonderfully in my experience. Ask if you have more questions. Have fun.
kevs888 said:
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
Click to expand...
Click to collapse
Fastboot page
graphdarnell said:
It shouldn't make a difference what rom you flash now so long as you wipe and format everything inside TWRP. But you must make sure you have bootloader 4.05. 4.02 will not allow you to flash LL or MM successfully, and the system does not upgrade on its own no matter what rom you're flashing now.
Since you said you couldn't get TWRP to copy anything, I suggested that you use a thumb drive. Basically, if you turn the tab totally off, hold power + volume down for a few seconds, it should take you to the fastboot page (pic). Look to see what bootloader version you have there.
From here, you can basically flash anything. I recommended that you wipe and format first with TWRP because it happened to me a few times when for some reason, wiping alone still left some residual data that interfered with flashing newer roms.
Stay away from anything stock for the moment. God knows it has bricked more than a few devices. Download SkipsoftToolKit and flash from the fastboot page if you want an automated process. It has worked wonderfully in my experience. Ask if you have more questions. Have fun.
Click to expand...
Click to collapse
This is really helpful...I think I'm almost there.
I'm on a super old Bootloader (see attachment) so I'll need to update. I downloaded the update from this XDA Thread
More questions:
- Would I be able to push the 4.05 bootloader update and custom whatever Marshmallow ROM via the toolkit instead of from a USB OTG?
- If I was rooted on 4.3, am I still rooted so that I would be able to flash the custom ROM? I don't want to risk doing further damage, lol.
- I'm not home at the moment, so I can't test this out -- I'm thinking I couldn't put anything into my tablet last night because it was running TWRP and I didn't have it on the Fastboot screen. Would being in the Fastboot screen possibly allow me to copy/paste the zip files into my tablet?
- If there's nothing I need to copy from the tablet, would I still need the USB OTG? Or could I just use the Toolkit to push everything into my tablet and flash via TWRP?
Based on your answers to the above would this be the correct order:
1. Push 4.05 bootloader update and custom ROM via toolkit to my tablet
2. Flash 4.05 bootloader update within TWRP
3. *Per your earlier advice* Wipe everything except USB OTG twice. Is this cache, dalvik, system, and data? Or literally there's an option for "wipe everything" (I don't remember what I saw)?
4. Then go to Format and do it twice, too. I have a 32GB, so I'm expecting it to take awhile for the format
5. Flash ROM, then Gapps. I don't have any apps I need to put back so much as I need an OS to load, so I can add later.
Thanks again for everything!
EDIT:
Okay, so I came home and was able to use the Toolkit to recognize the device in fastboot mode. However, I wasn't able to push anything into the phone because the Toolkit said that I needed to be booted into Android.
The last thing I saw when I was in TWRP poking around was that I saw that I could install .zip files from USB OTG. Are either of these alright for me to connect my flash drive to and be recognized inside TWRP?
Example 1
Example 2
kevs888 said:
This is really helpful...I think I'm almost there.
I'm on a super old Bootloader (see attachment) so I'll need to update. I downloaded the update from this XDA Thread
More questions:
- Would I be able to push the 4.05 bootloader update and custom whatever Marshmallow ROM via the toolkit instead of from a USB OTG?
- If I was rooted on 4.3, am I still rooted so that I would be able to flash the custom ROM? I don't want to risk doing further damage, lol.
- I'm not home at the moment, so I can't test this out -- I'm thinking I couldn't put anything into my tablet last night because it was running TWRP and I didn't have it on the Fastboot screen. Would being in the Fastboot screen possibly allow me to copy/paste the zip files into my tablet?
- If there's nothing I need to copy from the tablet, would I still need the USB OTG? Or could I just use the Toolkit to push everything into my tablet and flash via TWRP?
Based on your answers to the above would this be the correct order:
1. Push 4.05 bootloader update and custom ROM via toolkit to my tablet
2. Flash 4.05 bootloader update within TWRP
3. *Per your earlier advice* Wipe everything except USB OTG twice. Is this cache, dalvik, system, and data? Or literally there's an option for "wipe everything" (I don't remember what I saw)?
4. Then go to Format and do it twice, too. I have a 32GB, so I'm expecting it to take awhile for the format
5. Flash ROM, then Gapps. I don't have any apps I need to put back so much as I need an OS to load, so I can add later.
Thanks again for everything!
EDIT:
Okay, so I came home and was able to use the Toolkit to recognize the device in fastboot mode. However, I wasn't able to push anything into the phone because the Toolkit said that I needed to be booted into Android.
The last thing I saw when I was in TWRP poking around was that I saw that I could install .zip files from USB OTG. Are either of these alright for me to connect my flash drive to and be recognized inside TWRP?
Example 1
Example 2
Click to expand...
Click to collapse
If you're comfortable using the ToolKit, you don't need an OTG cable. Connect your tab to PC, fire up ToolKit, complete all the prelim BS, then flash the bootloader from TK. Do not use TWRP for this. To do this, open the ToolKit folder in drive C:, locate the folder therein for zips, place the zip files (4.05 bootloader; TWRP; or custom roms) in there, and start to install. I am talking off the top of my head. But give me a few minutes to check the Kit again, and I'll give specific instructions. Bear with me, as I'm on Linux at the moment and therefore cannot start ToolKit (which is in Windows).
Things to do in order:
1. Download bootloader 4.05 (flashable zip HERE); and custom rom of your choice (zip format)
2. Locate the Unified Android ToolKit on drive C: on your PC and open it;
3. Locate the folder “put zip file to sideload here” → “Nexus 7 2013” then paste
bootloader zip and Rom zip in there;
4. Fire up Toolkit with tab connected; complete all the prelim questions;
5. Follow all the steps to install TWR 2870 (pic 8, choice 6);
6. Go to TWRP, wipe and format.
7. Go back to TWRP main page → “Advanced” → “ADB sideload”;
8 Go to ToolKit (pic 8) enter choice 16 (Look at the pics that follow for the correct choices) to
sideload Bootloader;
9. Flash Bootloader.
10. Go back to TWRP main page → Reboot → Bootloader. Once there check bootloader version 4.05;
11. Get into TWRP to sideload Rom; flash it.
graphdarnell said:
Things to do in order:
1. Download bootloader 4.05 (flashable zip HERE); and custom rom of your choice (zip format)
2. Locate the Unified Android ToolKit on drive C: on your PC and open it;
3. Locate the folder “put zip file to sideload here” → “Nexus 7 2013” then paste
bootloader zip and Rom zip in there;
4. Fire up Toolkit with tab connected; complete all the prelim questions;
5. Follow all the steps to install TWR 2870 (pic 8, choice 6);
6. Go to TWRP, wipe and format.
7. Go back to TWRP main page → “Advanced” → “ADB sideload”;
8 Go to ToolKit (pic 8) enter choice 16 (Look at the pics that follow for the correct choices) to
sideload Bootloader;
9. Flash Bootloader.
10. Go back to TWRP main page → Reboot → Bootloader. Once there check bootloader version 4.05;
11. Get into TWRP to sideload Rom; flash it.
Click to expand...
Click to collapse
Wow, this is awesome. Thank you so much.
I had already flashed TWRP 2870 before I wiped the OS, but I figured I'd try again using the Toolkit, but I got an error. I stopped here just in case.
Earlier, I tried flashing the zip for the bootloader the same way you just instructed, but my serial number turned into question marks?
Please see attachments. My pics are on the right side of the comparisons and I blacked out some of my serial number just in case for the TWRP pic.
Thanks again for the continued support!
kevs888 said:
Wow, this is awesome. Thank you so much.
I had already flashed TWRP 2870 before I wiped the OS, but I figured I'd try again using the Toolkit, but I got an error. I stopped here just in case.
Earlier, I tried flashing the zip for the bootloader the same way you just instructed, but my serial number turned into question marks?
Please see attachments. My pics are on the right side of the comparisons and I blacked out some of my serial number just in case for the TWRP pic.
Thanks again for the continued support!
Click to expand...
Click to collapse
Ok. One step at a time. Since you don't have an OS installed, ToolKit cannot complete the process of sideloading because it normally would have to use ADB from within the OS (which is absent) to restart the tab into recovery mode (TWRP). But if you're already in sideload mode within TWRP, it would detect it and transfer the file over to your tab. Let's go back.
(1) Fire up ToolKit (TK), go to sideload step, type the file name and stop. Get to fastboot page on your tab. Go back to TK and hit enter. TK should detect fastboot mode, download TWRP 2.7.1.1, take the tab into TWRP, tell you to go to sideload mode. Thereafter, it should detect this mode and transfer the file over. Then TWRP would flash the bootloader 4.05 automatically. If successful, sideload the rom the same way to flash it. Then upgrade TWRP back to 2870 with TK.
(2) Failing the above (because TWRP somehow doesn't function correctly), put the tab in fastboot mode, go to TK and follow the steps to flash TWRP anew. TK should detect fastboot and begin to flash the recovery. That done, go back and restart (1) above.
(3) If that still doesn't work, we have to resort to fastboot.exe and do it by command lines. But that's far ahead. Try the above first. We'll cross that bridge if we get to it.
I can send you an automated package that would upgrade the bootloader to 4.04 that I downloaded a year ago from Scott's Roms (thanks to him). It's good enough for Lollipop 5.1. The file is about 4MB and I'm not sure how we can do this through XDA. But if we ever get there, I'm certain we'll find a way. And smile, it's only a lousy tab.
graphdarnell said:
Ok. One step at a time. Since you don't have an OS installed, ToolKit cannot complete the process of sideloading because it normally would have to use ADB from within the OS (which is absent) to restart the tab into recovery mode (TWRP). But if you're already in sideload mode within TWRP, it would detect it and transfer the file over to your tab. Let's go back.
(1) Fire up ToolKit (TK), go to sideload step, type the file name and stop. Get to fastboot page on your tab. Go back to TK and hit enter. TK should detect fastboot mode, download TWRP 2.7.1.1, take the tab into TWRP, tell you to go to sideload mode. Thereafter, it should detect this mode and transfer the file over. Then TWRP would flash the bootloader 4.05 automatically. If successful, sideload the rom the same way to flash it. Then upgrade TWRP back to 2870 with TK.
(2) Failing the above (because TWRP somehow doesn't function correctly), put the tab in fastboot mode, go to TK and follow the steps to flash TWRP anew. TK should detect fastboot and begin to flash the recovery. That done, go back and restart (1) above.
(3) If that still doesn't work, we have to resort to fastboot.exe and do it by command lines. But that's far ahead. Try the above first. We'll cross that bridge if we get to it.
I can send you an automated package that would upgrade the bootloader to 4.04 that I downloaded a year ago from Scott's Roms (thanks to him). It's good enough for Lollipop 5.1. The file is about 4MB and I'm not sure how we can do this through XDA. But if we ever get there, I'm certain we'll find a way. And smile, it's only a lousy tab.
Click to expand...
Click to collapse
Let me just say, I'm so thankful for your help in all of this. Seriously. Thank you.
I kept on tinkering with the ToolKit and Fastboot kept on stopping everytime I switched to TWRP. I got to the point where TWRP showed 2.7.1 but the ADB Sideload kept getting stuck at the "Starting Sideload" prompt.
I went out and bought a $3 OTB USG cable and figured I'd give it a go since this sounded easier (theoretically). At first, I couldn't understand why the OTG wasn't recognized within TWRP. Then, I realized I needed to mount it within TWRP.
Once it mounted, I wiped and flashed the 4.05 bootloader zip. Success.
I went back into the Fastboot screen to verify 4.05. Success.
Went back into TWRP 2.8.7 and flashed a 6.0 ROM from these boards. Success.
Flashed Gapps. Success.
Rebooted. I'm now running a custom Marshmallow ROM and it runs so smoothly now.
Seriously. Thank you.
kevs888 said:
Let me just say, I'm so thankful for your help in all of this. Seriously. Thank you.
I kept on tinkering with the ToolKit and Fastboot kept on stopping everytime I switched to TWRP. I got to the point where TWRP showed 2.7.1 but the ADB Sideload kept getting stuck at the "Starting Sideload" prompt.
I went out and bought a $3 OTB USG cable and figured I'd give it a go since this sounded easier (theoretically). At first, I couldn't understand why the OTG wasn't recognized within TWRP. Then, I realized I needed to mount it within TWRP.
Once it mounted, I wiped and flashed the 4.05 bootloader zip. Success.
I went back into the Fastboot screen to verify 4.05. Success.
Went back into TWRP 2.8.7 and flashed a 6.0 ROM from these boards. Success.
Flashed Gapps. Success.
Rebooted. I'm now running a custom Marshmallow ROM and it runs so smoothly now.
Seriously. Thank you.
Click to expand...
Click to collapse
I'm glad you got it working again. Sorry you had to make a trip to the store. You should've waited for KT to switch the tab to TWRP 2711 for you. But it was not a waste of time anyway.
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.
Did standard unlock bootloader (went fine)
Moved a TWRP zip onto phone sd root directory (twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.zip)
adp fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img. (went fine)
But when I look for the zip file (or any system files) it does not show up , even in TWRP file manager.
Redid data wipe and it tells me "Failed to mount /system_root and /vendor
I am 99% sure that its just because these will not mount:
Does anyone have any idea what I can do to get these mounted to start a regular TWRP flash ?
Well I tried adjusting data format and ended up losing the Stock Rom.
And the stuff will still not mount.
UPDATE, rewiped data and got stock rom to load.
Now Data will load but vendor will not.
UPDATE : data and vendor will mount after data wipe. But still cannot see anything that is placed on device.
Such as the zip files I need to install.
UPDATE: now I sideloaded TWRP onto new phone, but now cannot get it to reboot into Rom.
Its odd after plugging it in , it went to a stock recovery even when TWRP was installed.
Found the issues, finally had to run MSM download tool and fix everything from there and start from scratch.
Ended up installing TWRP from fastboot flash recovery image.
Now to get root going on it and magisk.
What device do you have?
You're in the 7T forum but saying you used the 7 Pro twrp.
If you're using 7T, the reason why you don't see internal storage is because TWRP cannot decrypt on OOS (this is not because of a mounting error, this is simply due how oneplus has implemented their encryption).
And on 7T you don't need a zip of any sort to install twrp.
Reading the actual twrp thread would be a good start.
Lossyx said:
What device do you have?
You're in the 7T forum but saying you used the 7 Pro twrp.
If you're using 7T, the reason why you don't see internal storage is because TWRP cannot decrypt on OOS (this is not because of a mounting error, this is simply due how oneplus has implemented their encryption).
And on 7T you don't need a zip of any sort to install twrp.
Reading the actual twrp thread would be a good start.
Click to expand...
Click to collapse
Yes, I read though the threads, But got so bombarded with pages of stuff kind of lost track.
This is why I posted . Also it is a combined Christmas gift for my daughter that she cannot know I am working on. So I think I tried to rush it when she was in school.
Found out about the decryption part after I started the process. Then it was too late and ended up having to start over with tools.
It was a newb move to end up this far and try to rush it.
People did help me get back on track and now I am working on figuring out Magisk. (good help on magisk threads).
Thanks for your response.
eracet said:
Well I tried adjusting data format and ended up losing the Stock Rom.
And the stuff will still not mount.
UPDATE, rewiped data and got stock rom to load.
Now Data will load but vendor will not.
UPDATE : data and vendor will mount after data wipe. But still cannot see anything that is placed on device.
Such as the zip files I need to install.
UPDATE: now I sideloaded TWRP onto new phone, but now cannot get it to reboot into Rom.
Its odd after plugging it in , it went to a stock recovery even when TWRP was installed.
Found the issues, finally had to run MSM download tool and fix everything from there and start from scratch.
Ended up installing TWRP from fastboot flash recovery image.
Now to get root going on it and magisk.
Click to expand...
Click to collapse
Magisk IS your root