Related
My FireTV was rooted, I got the ClockworkMod recovery installed and working. I chose to do a factory reset on my FireTV because I wanted to start clean. After I chose to reset to factory settings, I keep getting back to the ClockworkMod menu. If I put it through a reboot, I see it booting up and it shows me the following on the screen:
- Choose a language.
- setting up ethernet.
- downloading firmware (this lasts about 2 seconds)
- restarting the FireTV
and then I'm back to the ClockworkMod menu.
I tried installing from Zip and going to bueller-51.1.3.0_513011820-rooted.zip, but I when I try this I get the following in the ClockworkMod menu:
Installing: /sdcard/bueller-51.1.3.0_513011820-rooted.zip
Finding update package...
Opening update package...
Installing update...
Amazon kernel detected: not patching
Install from sdcard complete.
I assume something went wrong, and if I try to reboot after this it brings me back to the same cycle as I've mentioned before and I end up right back in the ClockworkMod menu.
Can anyone give me some advise on how to get this thing back to the bueller-51.1.3.0_513011820-rooted.zip?
Thanks in advance.
Did you try restoring the cwm backup you made before flashing?
nhumber said:
Did you try restoring the cwm backup you made before flashing?
Click to expand...
Click to collapse
I didn't make one
What are my options from the CWM menu to bring this back to life (in any form rooted/stock)?
That message is fine. It's not an error. The newest CWM can install custom kernels and they need to be patched. That message in red is just saying it found a stock Amazon kernel that does not need patching. When you say you "reboot", what are you doing? Are you pulling the power because you think the install failed? You just need to hit esc to get back to the main menu and "choose reboot" system from there.
kraqh3d said:
That message is fine. It's not an error. The newest CWM can install custom kernels and they need to be patched. That message in red is just saying it found a stock Amazon kernel that does not need patching. When you say you "reboot", what are you doing? Are you pulling the power because you think the install failed? You just need to hit esc to get back to the main menu and "choose reboot" system from there.
Click to expand...
Click to collapse
That is exactly what I'm doing (reboot through CWM). The reboot brings up the Amazon boot up logo, and then proceeds to check ethernet, says it is downloading some firmware and then spits me back into the CWM menu.
DaveTO said:
That is exactly what I'm doing (reboot through CWM). The reboot brings up the Amazon boot up logo, and then proceeds to check ethernet, says it is downloading some firmware and then spits me back into the CWM menu.
Click to expand...
Click to collapse
If it's booting into the OS, it could be detecting that there is an updating, downloading it, and then rebooting to install it. CWM won't auto update, so it's just going to sit there. If you aren't on the latest version, that'll be why. So you'll need to update to that latest version through the prerooted roms.
And you'll have to get the latest pre-rooted image onto the firetv either via adb while cwm is running or from a usb stick.
kraqh3d said:
And you'll have to get the latest pre-rooted image onto the firetv either via adb while cwm is running or from a usb stick.
Click to expand...
Click to collapse
The easiest way to install updates is just to select install from sideload in cwm and use adb connect ip and then adb sideload.
rbox said:
The easiest way to install updates is just to select install from sideload in cwm and use adb connect ip and then adb sideload.
Click to expand...
Click to collapse
Is it pretty straight forward? I've sideloaded apks but not OS zip files. I'll try this when I get home tonight:
1) Install from sideload.
2) Connect to FireTV via adb.
3) adb sideload bueller-51.1.4.0_514006420-rooted+updated.zip
4) reboot after some on screen indication that the process is done?
DaveTO said:
Is it pretty straight forward? I've sideloaded apks but not OS zip files. I'll try this when I get home tonight:
1) Install from sideload.
2) Connect to FireTV via adb.
3) adb sideload bueller-51.1.4.0_514006420-rooted+updated.zip
4) reboot after some on screen indication that the process is done?
Click to expand...
Click to collapse
Yup.
Do you have to install BOOT MENU every time before you update a Custom ROM?
http://www.aftvnews.com/roms/
Boot Menu MUST be installed BEFORE installing this ROM or you will brick your Fire TV. Boot Menu and ClockworkMod are NOT the same thing.
You MUST first have installed Pre-Rooted ROM version 51.1.4.0 at some point before installing this version. You don’t have to downgrade to 51.1.4.0 if you are running a newer pre-rooted ROM. You just can’t skip from 51.1.3.0 or older straight to this version.
md5sum: de2ab7f2d3072e10d3e592b73ca52750
Released: 4/15/2015
Click to expand...
Click to collapse
Neo3D said:
Do you have to install BOOT MENU every time before you update a Custom ROM?
http://www.aftvnews.com/roms/
Click to expand...
Click to collapse
If I remember right, you only have to install the custom boot menu when applying either of the most recent updates. However, if you downgrade back to an older update that doesn't require the menu and decide to go back to the one of the newer updates, then you have to re-install the custom boot menu. I think it's only a requirement for the last two updates that're at the top of the list in the updates thread, the ones listed below don't require the custom menu. I know from experience that after install the custom menu and then the latest update, then going back to the build I was on before that, I lost the menu. Either way, though, just make sure you install the custom menu BEFORE applying the latest update, otherwise you'll get stuck on the Amazon logo screen, and the only way to get into recovery mode is to do the Fire TV version of the three finger salute: Alt+Shift+Print Screen, I think, and keep doing it til you get to recovery. I apologize in advance if I confused you a little, sometimes I get a little informative and ramble, kind of like what I'm doing right now
will4958 said:
If I remember right, you only have to install the custom boot menu when applying either of the most recent updates. However, if you downgrade back to an older update that doesn't require the menu and decide to go back to the one of the newer updates, then you have to re-install the custom boot menu. I think it's only a requirement for the last two updates that're at the top of the list in the updates thread, the ones listed below don't require the custom menu. I know from experience that after install the custom menu and then the latest update, then going back to the build I was on before that, I lost the menu. Either way, though, just make sure you install the custom menu BEFORE applying the latest update, otherwise you'll get stuck on the Amazon logo screen, and the only way to get into recovery mode is to do the Fire TV version of the three finger salute: Alt+Shift+Print Screen, I think, and keep doing it til you get to recovery. I apologize in advance if I confused you a little, sometimes I get a little informative and ramble, kind of like what I'm doing right now
Click to expand...
Click to collapse
I had Boot Menu previously installed but didn't reinstall it again before updating to this latest Custom ROM and now my AFTV is in a boot loop. I also noticed that the Boot Menu is now gone?
Is there anything I can do to fix this?
I can go into Recovery using the three finger salute, thanks!
But what do I do next?
Neo3D said:
I had Boot Menu previously installed but didn't reinstall it again before updating to this latest Custom ROM and now my AFTV is in a boot loop. I also noticed that the Boot Menu is now gone?
Is there anything I can do to fix this?
I can go into Recovery using the three finger salute, thanks!
But what do I do next?
Click to expand...
Click to collapse
Cool. Glad you were able to get back in there. When it happened to me, my arms got a little sore from having to smash the keyboard so much, but the keyboard is a little on the stiff side, so it didn't take much. Anyway, at this point you want to restore a backup you hopefully made, install the custom boot menu, then install the new update again. On the chance you don't have a recent backup, or any backup handy, just install any the last version you were on that didn't require the menu, reboot to make sure it took, install the custom menu, flash the new update, then reboot. That should get you back up and running.
will4958 said:
Cool. Glad you were able to get back in there. When it happened to me, my arms got a little sore from having to smash the keyboard so much, but the keyboard is a little on the stiff side, so it didn't take much. Anyway, at this point you want to restore a backup you hopefully made, install the custom boot menu, then install the new update again. On the chance you don't have a recent backup, or any backup handy, just install any the last version you were on that didn't require the menu, reboot to make sure it took, install the custom menu, flash the new update, then reboot. That should get you back up and running.
Click to expand...
Click to collapse
Thanks! Unfortunately, I didn't make any backups of before when it was working.
How do I copy the Custom ROM zip file onto the AFTV?
Neo3D said:
Thanks! Unfortunately, I didn't make any backups of before when it was working.
How do I copy the Custom ROM zip file onto the AFTV?
Click to expand...
Click to collapse
Since you're only able to get into recovery mode at this point, you'd have to copy the ROM to a flash drive. If you have a USB hub, preferably a powered one, plug the flash drive into the hub, along with a usb/wireless keyboard if you have either. The Fire TV should automatically detect the flash drive as long as it's formatted with a Windows file format. At that point, installing the update is just like doing it from the Fire TV itself, but since you're using a flash drive you'll want to select the install from USB option. I forget exactly what it's called, but you'll know it when you see it. The only thing that'll pop up will be the custom ROM you copied to the drive.
will4958 said:
Since you're only able to get into recovery mode at this point, you'd have to copy the ROM to a flash drive. If you have a USB hub, preferably a powered one, plug the flash drive into the hub, along with a usb/wireless keyboard if you have either. The Fire TV should automatically detect the flash drive as long as it's formatted with a Windows file format. At that point, installing the update is just like doing it from the Fire TV itself, but since you're using a flash drive you'll want to select the install from USB option. I forget exactly what it's called, but you'll know it when you see it. The only thing that'll pop up will be the custom ROM you copied to the drive.
Click to expand...
Click to collapse
So, I copy my zip file onto a USB drive and plugged it into a hub into the AFTV. However, I can't find any option to access the USB drive from inside Clockwork?
When I go into /sda1/ it doesn't actually show the contents of the USB drive. I'm using the same USB drive that I normally have plugged into the AFTV (for downloading videos from Genesis).
Neo3D said:
So, I copy my zip file onto a USB drive and plugged it into a hub into the AFTV. However, I can't find any option to access the USB drive from inside Clockwork?
When I go into /sda1/ it doesn't actually show the contents of the USB drive. I'm using the same USB drive that I normally have plugged into the AFTV (for downloading videos from Genesis).
Click to expand...
Click to collapse
Your flash drive has to be formatted to FAT or NTFS, both of which are Windows file system formats. Once you plug the drive into the Fire TV or hub, it will automatically detect it. Give it a few seconds to do so, then select Install zip. On the next screen you'll see the usual methods for installing a ROM, but now you should also see an option that says Choose zip from USB, or something similar to that. Once you choose it, the next screen should show the zip file for the custom ROM you placed on your flash drive, but the drive has to be formatted as a FAT32 or similar Windows file system drive for the Fire TV to see the drive. And yes, I know it sounds a little silly considering the Fire TV runs on a version of Linux, but that's technology for you
will4958 said:
Your flash drive has to be formatted to FAT or NTFS, both of which are Windows file system formats. Once you plug the drive into the Fire TV or hub, it will automatically detect it. Give it a few seconds to do so, then select Install zip. On the next screen you'll see the usual methods for installing a ROM, but now you should also see an option that says Choose zip from USB, or something similar to that. Once you choose it, the next screen should show the zip file for the custom ROM you placed on your flash drive, but the drive has to be formatted as a FAT32 or similar Windows file system drive for the Fire TV to see the drive. And yes, I know it sounds a little silly considering the Fire TV runs on a version of Linux, but that's technology for you
Click to expand...
Click to collapse
Here are the options that I see?
Choose zip from /sdcard
Choose zip from last install folder
Install zip from sideload
My recovery is version: 6.0.5.1.4a
http://www.aftvnews.com/recovery/
Neo3D said:
Here are the options that I see?
Choose zip from /sdcard
Choose zip from last install folder
Install zip from sideload
My recovery is version: 6.0.5.1.4a
http://www.aftvnews.com/recovery/
Click to expand...
Click to collapse
Yeah, it looks like it's not detecting your flash drive. Did you format the drive to something like FAT, FAT32, or NTFS? If not, it won't detect the drive, and you won't be able to install the ROM from the flash drive. Also, if the drive is already plugged in, you could try pulling it out then reinserting it again. But like I said, none of that will work if the drive isn't formatted properly.
will4958 said:
Yeah, it looks like it's not detecting your flash drive. Did you format the drive to something like FAT, FAT32, or NTFS? If not, it won't detect the drive, and you won't be able to install the ROM from the flash drive. Also, if the drive is already plugged in, you could try pulling it out then reinserting it again. But like I said, none of that will work if the drive isn't formatted properly.
Click to expand...
Click to collapse
Yes, it is NTFS?
Neo3D said:
Yes, it is NTFS?
Click to expand...
Click to collapse
I'd say if it's not detecting it with that format, try formatting as FAT32. I just checked a drive I've used before for the same thing, and it's formatted as FAT32 and it still has a recent update on it I tried before.
will4958 said:
I'd say if it's not detecting it with that format, try formatting as FAT32. I just checked a drive I've used before for the same thing, and it's formatted as FAT32 and it still has a recent update on it I tried before.
Click to expand...
Click to collapse
Thank you! I will try that.
So, I guess I should have re-installed BOOT MENU before upgrading the custom ROM.
It kind of doesn't make sense to have to re-install BOOT MENU if you already have it running before upgrading?
Neo3D said:
Thank you! I will try that.
So, I guess I should have re-installed BOOT MENU before upgrading the custom ROM.
It kind of doesn't make sense to have to re-install BOOT MENU if you already have it running before upgrading?
Click to expand...
Click to collapse
I can't remember the reason the custom boot menu requirement before applying the new update, but it does give you a couple different options when booting. Can't remember what they are, but the logo looks cool. As far as having to reinstall the custom boot menu, though, it's only a requirement for the two newest updates on this forum, and the way the thing is programmed it's made to look for that custom menu when booting. It only takes a couple minutes to install the menu, and after that you're back to watching Netflix, playing Dead Trigger, or whatever.
will4958 said:
I can't remember the reason the custom boot menu requirement before applying the new update, but it does give you a couple different options when booting. Can't remember what they are, but the logo looks cool. As far as having to reinstall the custom boot menu, though, it's only a requirement for the two newest updates on this forum, and the way the thing is programmed it's made to look for that custom menu when booting. It only takes a couple minutes to install the menu, and after that you're back to watching Netflix, playing Dead Trigger, or whatever.
Click to expand...
Click to collapse
Yea, it was confusing whether or not the BOOT MENU needed to be re-installed before EVERY new update when you already have it installed and working.
i did not install the bootmenu again when i did update from 1.4.1 to 1.4.3 nor from 1.4.3 to 1.5.0.
I just installed the zip file via recovery.
Why dont you boot to recovery and adb push the update .zip file to your internal storage? IIRC adb is enabled in recovery,
(since you seem to be having problems with the usb drive)
aHcVolle said:
i did not install the bootmenu again when i did update from 1.4.1 to 1.4.3 nor from 1.4.3 to 1.5.0.
I just installed the zip file via recovery.
Why dont you boot to recovery and adb push the update .zip file to your internal storage? IIRC adb is enabled in recovery,
(since you seem to be having problems with the usb drive)
Click to expand...
Click to collapse
Yea, I didn't think I had to either since my BOOT MENU had been installed and working....but I got stuck in a boot loop after upgrading??
I ended up using SIDELOAD to push a zip to the AFTV: https://www.youtube.com/watch?v=dWXHD7PlaQc
Thanks!
Hi.
International version, Europe, S-off, Unlocked.
I think that I managed to write a wrong firmware on a stock, but rooted rom (im not shure if this is the cause, i followed the instructions and the log was ok). The result is that if I flash a rom (with TWRP), no matter which (L or MM), the phone boots, the initial setup starts, language selection ok, wireless connection functional, but when i reach the google account checking, even the email and password are ok, it continuously throw me back to the google email checking...
The situation now is like this:
- can enter TWRP, fully functional
- can enter download mode
- can enter bootloader mode.
The problem is that the phone is recognized by the computer only when in TWRP, no connection on download/bootloader. So I cannot use adb to push commands. When in TWRP i can put anything on internal or external storage and flash...
Please, help me with some advice in order to fix this.
Thank you.
Dont bother. Found the lollipop oficial ruu zip, flashed from the external card in download mode, system fully operational in 5.1 now.
Its an odd one to say the least. I had a similar issue when rooting my phone last night. After installing twrp I couldn't speak the phone for love nor money.
Tried a sideload in twrp and it told me that my adb.exe was too old for my phone so I updated it and then I had adb control at least.
Changed my twrp from newer to older and then everything seemed ok.
Sent from my HTC One M9 using Tapatalk
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.