Related
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.
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.
So my laptop broke a while ago and I now have no way of updating without losing root which is not an option for me. So I've tried using android to android TV adb/fastboot commands over network but android to android adb doesn't seem to work at all. So while digging on what I could possibly do I've come up with an idea but not sure it will work. I have the nvidia shield TV (1st gen) 16gb version currently on 3.3, rooted with twrp installed. I found this:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
So my idea is to use these instructions to install the hacked twrp (Darcy) and then install update ota from there and then install root? Will this work?
Slayerkodi said:
So my laptop broke a while ago and I now have no way of updating without losing root which is not an option for me. So I've tried using android to android TV adb/fastboot commands over network but android to android adb doesn't seem to work at all. So while digging on what I could possibly do I've come up with an idea but not sure it will work. I have the nvidia shield TV (1st gen) 16gb version currently on 3.3, rooted with twrp installed. I found this:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
So my idea is to use these instructions to install the hacked twrp (Darcy) and then install update ota from there and then install root? Will this work?
Click to expand...
Click to collapse
What are you on now? 3.x or 5.0.0? If you're on 3.x, I'm not completely sure your idea will work. If you're on 5.0.0 it might.
Weird stuff happens between major build numbers.
I'm now on 5.0.2, what about somehow running windows or Linux from my phone and connect adb that way would it work? I could otg to otg or otg to USB, just not sure it would work
Depends on if TWRP can flash partitions that updates need to flash. I believe TWRP will just flash system, vendor and boot.
Slayerkodi said:
So my laptop broke a while ago and I now have no way of updating without losing root which is not an option for me. So I've tried using android to android TV adb/fastboot commands over network but android to android adb doesn't seem to work at all. So while digging on what I could possibly do I've come up with an idea but not sure it will work. I have the nvidia shield TV (1st gen) 16gb version currently on 3.3, rooted with twrp installed. I found this:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
So my idea is to use these instructions to install the hacked twrp (Darcy) and then install update ota from there and then install root? Will this work?
Click to expand...
Click to collapse
Yeah Ive been trying all night - tried with running Linux on android which worked well, I installed adb tools, run the server, connected with otg and USB and 'adb devices' shows nothing attached. I got network debugging to connect but I know that's pointless as it won't have WiFi connectivity once its in recovery where its needed to push twrp. Maybe one day
So went and borrowed a mates charger and all good now but I'm planning to get rid of my laptop and the only thing holding me back is this process of rooting and installing twrp, if I could do this on the shield itself or us another android device to push commands this would be a big help as then I really don't need a laptop at all
First, update TWRP to the unofficial version (latest), you can then download the OTA and supersu .zip in your phone and copy them to an external usb flash drive with an OTG usb cable/adapter.
You can check in your phone the files inside the compressed OTA package.
First do factory reset (if 16 gb model i would also wipe media)
Flash OTA from TWRP
Flash supersu right after (if you get an error that you cant write to data or similar then a reboot to recovery is a must)
Cross fingers to succesfully reboot to twrp again, then flash supersu and reboot system.
Root is systemless, be carefull to not do another factory reset or you'll wipe root too.
If twrp is gone, you must use a Windows machine because Nvidia provides fastboot drivers for when shield tv is booted up in bootloader or fastboot mode. Haven't seen linux drivers for that.
ADB is not really of much help or use but fastboot is. In case TWRP dissapears then the only way is flashing it back with fastboot and to boot into it from command line too.
I've installed Full Android Nougat on my 2015 shield tv and have gone back to stock and then again to full android. I also wanted to find a way to not be dependant of a pc/laptop, unfortunately there isn't one yet as far as i know. Also if you forget and do a factory reset from settings then root will be gone and no way to easily boot into TWRP again, you'll again need fastboot.
I have done enough tests and everything i mentioned i have done it myself or has happened to me and eather way or another I've find myself always having to use my laptop.
Enviado desde mi Moto X via Tapatalk!
lavero.burgos said:
First, update TWRP to the unofficial version (latest), you can then download the OTA and supersu .zip in your phone and copy them to an external usb flash drive with an OTG usb cable/adapter.
You can check in your phone the files inside the compressed OTA package.
First do factory reset (if 16 gb model i would also wipe media)
Flash OTA from TWRP
Flash supersu right after (if you get an error that you cant write to data or similar then a reboot to recovery is a must)
Cross fingers to succesfully reboot to twrp again, then flash supersu and reboot system.
Root is systemless, be carefull to not do another factory reset or you'll wipe root too.
If twrp is gone, you must use a Windows machine because Nvidia provides fastboot drivers for when shield tv is booted up in bootloader or fastboot mode. Haven't seen linux drivers for that.
ADB is not really of much help or use but fastboot is. In case TWRP dissapears then the only way is flashing it back with fastboot and to boot into it from command line too.
I've installed Full Android Nougat on my 2015 shield tv and have gone back to stock and then again to full android. I also wanted to find a way to not be dependant of a pc/laptop, unfortunately there isn't one yet as far as i know. Also if you forget and do a factory reset from settings then root will be gone and no way to easily boot into TWRP again, you'll again need fastboot.
I have done enough tests and everything i mentioned i have done it myself or has happened to me and eather way or another I've find myself always having to use my laptop.
Enviado desde mi Moto X via Tapatalk!
Click to expand...
Click to collapse
Ive found myself in that situation, no root, and no way to boot to twrp, after a while searching, found that theres a keyboard combination that reboots the shield (also works on ouya, nexus, maybe standard android?), and pressing this same key combination one or three times after the reboot, as soon as first logo shows, boots the shield to recovery
Combination = alt + print screen + i (no root, no adb required, was a life saver)
Edit
Usb keyboard required (maybe 2.4ghz keyboard might work to) , as theres no bluetooth/wifi during boot
Edit
Well actually, folks can test the initial reboot with a bluetooth keyboard, just wont be able to use the key combination during boot, and im pretty sure if the shield reboots, then the 'boot to recovery' aspect should work too(with usb keyboard)
Edit
Curious to know if this also works on the 2017 model
Would it be possible to downgrade from Nougat 5.1 back to Marshmallow 3.3?
savagepagan said:
Would it be possible to downgrade from Nougat 5.1 back to Marshmallow 3.3?
Click to expand...
Click to collapse
I wouldn't recommend that. I've seen like 5 users that have soft and hard bricking their Shield doing so.
If you flash full recovery images or OTA that contain and flash MM or a different model bootloader you will brick your device.
Enviado desde mi Moto X mediante Tapatalk
What you could do... Is before updating to Nougat. Make a hard backup of your SSHD (Sorry 16Gb Users), following the first Page of the SSHD to SSD Migration Threads.
And then just use that to roll back. It will also save your arse in the worst nightmare scenario. When you having just attempted to roll back to a lower version, and then find yourself with a Brick.
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.
I apologize if this has been covered before, but several searches haven't turned it up.
I'm trying to upgrade my Galaxy Tab Pro 8.4 to Android 7.1 and I'm running into a roadblock in the recovery mode. I have options for Wipe data/factory reset and Wipe cache partition, but there's no Advanced option, so I can't wipe the Dalvik cache.
The tablet is rooted -- I checked it after running Odin, and even ran Odin once more to be sure -- and I had Debugging checked under Developer Options, so I think I should be seeing the Advanced option, but it's not there.
I tried installing the new OS anyway, but I got failure messages, and then the tablet rebooted itself to 4.4.2, still rooted. I've restarted Developer Options and re-checked Debugging.
I must be missing something, but I can't see it. Thanks in advance.
This is driving me insane. Every time I think I'm making progress I run into a roadblock. At this point I'm just trying to load/install TWRP recovery so I can do a thorough wipe, including the Dalvik cache, but although I can find the flash file in my file manager, TWRP doesn't see it.
On the tablet's own storage TWRP starts its search at emulated/0, but I can't find folders in the file manager called emulated or 0. It will also look in sdcard, but even though I've copied the file there, TWRP doesn't see it, although it seems to be looking for "extsdcard." It also doesn't see zip files I've downloaded to the sd card, if that matters. It seems that TWRP can only find folders, not files.
I uninstalled and reinstalled TWRP, but it's the same. So I uninstalled TWRP again and tried to go with CWM, but it's not compatible with my tablet.
Part of me knows there must be a solution somewhere, but this has just about reached the point of "life's too short." If anyone can offer any help, it would be greatly appreciated.
I've finally had some success! I found instructions for installing TWRP with Odin, and they worked. And so, I expect, did the TWRP backup of the tablet's OS. All I need now is a Nougat 7.1 download that works; the one I have now:
Galaxy Tab Pro 8.4 Lineage OS 14.1 [mondrianwifi] [Android 7.1.1 Nougat]
...isn't working. TWRP attempted the zips I downloaded (OS and GAPPS?) but the verification failed. So at this point I can only boot to TWRP. If I just start the tablet normally, it hangs at the Samsung logo screen, and while I can turn it off, it starts itself again after 10 seconds or so, requiring a boot to TWRP and shut down from there.
I'm hopeful I'll find downloads that work, but some of the links I've found appear to have expired. I should be able to go back to 4.4.2 from the backup, but since I've gotten this far I'd like to follow through. It looks like I have more searching ahead of me.
More success! I found the following link to the OS and downloaded the Pico GAPPS as that author suggested, and it worked! My thanks to Marc0601!
https://forum.xda-developers.com/ga...m-resurrection-remix-5-8-5n-02-09-18-t3837764