Related
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
amplifier1980 said:
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Click to expand...
Click to collapse
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit? http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Lexus One said:
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit?
Click to expand...
Click to collapse
Hi. Meanwhile i found a thread in nexus5 Android development area which contains both deodexed and odexed stock rooted full rom . so i just flashed odexed Version over my 4.4... Now i am on 4.4.2 finally... And still rooted..
Thank u anyway..
Greetz, fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
Hi,
You can try performing a full unroot in the SuperSU app if it still doesn't work... I had to adb sideload mine to work, don't know how it works with toolkit, but you have to first set your tablet to receive it. As you are on TWRP you simply go to advanced and select adb sideload, then try using the tool, or following the instructions on it to do so .
You cannot install a OTA zip like a Custom ROM zip, they are a little bit different hehe.
Hope this helps,
~Lord
PS.: This will work for N5 too.
I somehow got the idea that rooted Nexus devices with a custom recovery could handle OTA's without trashing the recovery. I guess I expected that I would lose root. I think I'm just going to wait for someone to put together a "CleanROM" based on 4.4.2 or newer. I've been waiting for a rom like this since I bought my Nex10 anyway. I don't think I'll suffer too much running on 4.4 until then.
Thanks to those who contributed, I'll remember your suggestions. Especially if I end up waiting a long time for a 4.4.2 based Cleanrom.
Update: Thanks to Wug's toolkit. I'm now running 4.4.2..
I should ask for a sticky for this but these instruction will work EVERY TIME if you are running either custom recovery or Root.
You will need the latest adb/fastboot from google, you can either install the SDK or download any of the many smaller adb/fastboot and libs for your os
You will need STOCK 4.4/4.3/4.2 recovery depending on what version of android you are currently on. Download the factory image from here. Open the zip within the package and pull out recovery.img and rename it stockrecovery.img
Copy your custom recovery to the adb folder name it twrp.zip or short name for whatever you are using I am using twrp.
You will need the correct OTA you are seeking to apply - rename it to something short simple and obvious - for this example I will use otaupdate.zip
If you wish to root get the latest patch (I believe its up to 1.75 now) and copy it to the adb/fastboot folder.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If you are already Rooted:
If you are using SuperSU - go to the application options and completely unroot and reboot if needed
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If not rooted start here:
I am assuming most of you are Windows users. Open your file explorer and open the ADB folder.
On the left hand folder where ADB is located press shift and right click the ADB folder and select "Open command window from here". This will open a command prompt window for you to run all your adb/fastboot commands from. This is the same folder where you copied your recoveries and updates to.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
Copy your custom recovery and stock recovery to your adb folder
Copy and rename the OTA to the adb folder
Copy your root.zip patch to the /sdcard downloads folder (if you wish root)
>adb reboot bootloader
>fastboot flash recovery stockrecovery.img
>fastboot reboot-bootloader
Go into recovery and wait till dead droid appears
Press power and Volume Up at same time to go into the stock recovery menu
Using the volume buttons move and down the blue list of options and select: Apply update from ADB
You will now have orange text at the bottom of the screen - follow the instructions to side load by typing >adb sideload otaupdate.zip in your command prompt window
Wait and watch the progress, at this point you should see the ota processing steps of which there a few and will vary depending on the package. When its complete there will be a "install complete" or similar message
Reboot and let the update complete the system optimizations and go in validate your device is working and the version is what you wanted
>adb reboot bootloader
>fastboot flash twrp.zip
>fastboot reboot-recovery
Using your newly installed custom recovery you can now apply zips/root etc
Reboot as needed and update root if using older .zip to current binaries and enjoy your updated device.
And yes you only need to backup once prior to starting but many people skip that step -DON'T BE ONE OF THOSE PEOPLE.
Hopefully I've not missed a bit.
You can also use these same instructions if you're stuck in boot loop or applied a patch without first replacing stock or unrooting - just boot to bootloader using fastboot and replace recovery and apply the patches. This will usually work just fine and prevent much heart ache on your part.
Hey. I long story short - I have wiped OS, and the only thing that I can do is use fastboot and also install TWRP or stock recovery.
I found OxygenOS file, but cant install it as there are problems sideloading the file to the device, it looks like ADB drivers on PC are not recognizable. Can someone help me to get back OS? Thanks
Tried a lot of things but anyway nothing happens.
BooBzi said:
Hey. I long story short - I have wiped OS, and the only thing that I can do is use fastboot and also install TWRP or stock recovery.
I found OxygenOS file, but cant install it as there are problems sideloading the file to the device, it looks like ADB drivers on PC are not recognizable. Can someone help me to get back OS? Thanks
Tried a lot of things but anyway nothing happens.
Click to expand...
Click to collapse
Push the OOS rom via usb to the phone, command: adb push namerom /scard
Next time check the drivers installation result first.
I wish I knew the reply above mine.
How I fixed my issue:
I installed the latest TWRP 3.1.1 in one of the installation guides on this forum for the OP5. Make sure you pick the version that is called the "last latest build". I was able to flash a full zip for 4.5.2 and it worked!
chaojimbo said:
I wish I knew the reply above mine.
How I fixed my issue:
I installed the latest TWRP 3.1.1 in one of the installation guides on this forum for the OP5. Make sure you pick the version that is called the "last latest build". I was able to flash a full zip for 4.5.2 and it worked!
Click to expand...
Click to collapse
I had problems with ADB drivers, anyway got back to life:
1) booted to TWRP
2) adb push ".zip" /sdcard/.
3) tried installing it at TWRP, no success, so get back stock recovery and flashed the file there.
So my issue is resolved. thanks!
Dear Android Community,
I have a small problem during the process of rooting my phone - Google Pixel 2 XL.
Before I will explain what I have already tried, I would like to notice that in the past I already rooted exactly this phone. But then, after a while, I started to have some screen issues, I thought it can be some firmware issue, so i wiped my phone completely through cmd (flash-all.bat). A moment after I've realized, that the screen issue was the hardware issue.
Afterwards every time I try to root my phone, i follow this loop:
fastboot boot twrp 3.2.3-1,
adb push twrp.rar & install
*phone works normally*
From there on I have usually two further loops:
a)
adb reboot bootloader,
adb push magisk (various versions)
install magisk.rar (success)
Android can't load - stuck in loading screen
adb reboot bootloader
flash-all.bat
b1)
download & install Magisk manager
download magisk.rar from manager
adb reboot recovery
install magisk.rar (success)
phone can't load
adb reboot bootloader
flash-all.bat
b2)
download & install Magisk Manager
copy & paste the boot.img,
patch boot.img in Magisk Manager
copy it back on my computer
adb reboot bootloader
fastboot flash boot patched_boot.img
phone can't load
adb reboot bootloader
flash-all.bat
I did that both with and sometimes without allow debugging through USB option (from dev options). No difference.
Anyway, at the end, I have to install android system from over and over again, without any success. Google can't help, DuckDuckGo can't help, I hope you guys can help. As I have mentioned, this phone was rooted once, so it has to be possible!
Thanks in advance for any help
Regards
Where are you getting the rar files? I've only ever used zip files.
jd1639 said:
Where are you getting the rar files? I've only ever used zip files.
Click to expand...
Click to collapse
Sorry, my mistake. Of course I meant zip files.
One thing I would not do is push the zip or TWRP image to the device. Instead, in Android I would download the zip or image from twrp.me using Chrome, which will store it in the downloads folder. I then download the Magisk zip file using Magisk Manager, which stores it in the downloads folder. Once that's done, try the following:
fastboot boot twrp.img.
Navigate to the previously downloaded file and install it.
Flash Magisk.
Reboot.
Be patient.
The last one I put in there because there have been occasions where it has taken my P2XL a few minutes to get to the lock screen, but it eventually gets there. Now, if you're still looping a half hour later that's a cause for concern and you may need to redo things.
Strephon Alkhalikoi said:
One thing I would not do is push the zip or TWRP image to the device. Instead, in Android I would download the zip or image from twrp.me using Chrome, which will store it in the downloads folder. I then download the Magisk zip file using Magisk Manager, which stores it in the downloads folder. Once that's done, try the following:
fastboot boot twrp.img.
Navigate to the previously downloaded file and install it.
Flash Magisk.
Reboot.
Be patient.
The last one I put in there because there have been occasions where it has taken my P2XL a few minutes to get to the lock screen, but it eventually gets there. Now, if you're still looping a half hour later that's a cause for concern and you may need to redo things.
Click to expand...
Click to collapse
I just tried your system, unfortunately doesn't work for me. I was waiting around 20-30 min, nothing happened. Which version of image / OTA do you use? Maybe I should use some custom ROM?
I would boot into TWRP, install Magisk Uninstaller to clean up the old Magisk files, then install magisk again, followed by clear dalvik and cache. Then reboot system.
Downloads, here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
VanDerPe said:
Maybe I should use some custom ROM?
Click to expand...
Click to collapse
No need for a custom ROM.
I'm totally stock, except for root and TWRP. I download my OTAs direct from where Google hosts them, so these are complete system images.
Back up your device. Download the latest stock ROM image (NOT an OTA) and flash it using fastboot. Boot into Android, make sure OEM Unlocking is enabled, then return to the bootloader so you can flash TWRP and then Magisk.
Strephon Alkhalikoi said:
One thing I would not do is push the zip or TWRP image to the device. Instead, in Android I would download the zip or image from twrp.me using Chrome, which will store it in the downloads folder. I then download the Magisk zip file using Magisk Manager, which stores it in the downloads folder. Once that's done, try the following:
fastboot boot twrp.img.
Navigate to the previously downloaded file and install it.
Flash Magisk.
Reboot.
Be patient.
The last one I put in there because there have been occasions where it has taken my P2XL a few minutes to get to the lock screen, but it eventually gets there. Now, if you're still looping a half hour later that's a cause for concern and you may need to redo things.
Click to expand...
Click to collapse
Patience is good advice, I wiped my phone a few days ago, when all was said and done, I should have waited longer, because I was not boot looping.
I had the same problem yesterday as the OP, and running Magisk Uninstaller fixed it for me.
I've tried to upgrade the rom in MOTO G4 Plus using TWRP version of 3.2.1.0 and during installation process I wiped out the existing android 7.0.1 without backup(understood the cost of backups now). As I faced error while installing android 9.0.1 with error 255 code because of TWRP some upgrade issue couldn't complete the installation process successfully.
I tried multiple ways to upgrade TWRP which was not successful and even fastboot commands aren't working now. Whenever I try fastboot + combinational command like devices and etc it goes into an infinite loop with an error code iterator not found. After a good amount of search found about ADB and happily can connect to my device using ADB now. Then started trying with multiple options like adb side load after reading multiple forum answers and posts I did pushed a rom to scared/data/media after reading this forum NEED HELP: Accidentally deleted OS in TWRP/Cant install Rom which was successfully pushed but didn't do any thing nor I couldn't understand what to do after pushing it.
Then started search again to install stock rom in any different ways before coming here and stumbled at this question which is similar did read the question and included forum post in it to go start the process when I did download stock rom stock rom download couldn't find any flashall.sh file to start the process
Now I'm stuck and couldn't find better place to find a working solution for this situation. Can somebody help me? What can I do while my phone is in this state?
can someone please help me out from this situation
Do you still have access to TWRP on your device? If so, what ROM did you push to your device? You might like to try with a TWRP flashable like the stock ROM Oreo flashable https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 and follow the instructions to install it (i.e. push to your device, or copy to an SD card, then tap install in TWRP to flash it to your device). This TWRP flashable should work on your TWRP version since it's 32 bit.
The stock ROM download would still require fastboot, so I'm not sure why your fastboot is not working. What fastboot are you using (is it minimal ADB/fastboot or the Google ADB) and have you downloaded/installed the Motorola USB drivers as well? https://support.motorola.com/us/en/drivers
(As you probably found out, error 255 when flashing custom Oreo or Pie ROMs means that your TWRP is 32 bit, whereas the custom ROM requires a 64 bit TWRP. What 64 bit TWRP are you flashing that are not successful, and how are you flashing the 64 bit TWRP, via fastboot or in TWRP?)
echo92 said:
Do you still have access to TWRP on your device? If so, what ROM did you push to your device? You might like to try with a TWRP flashable like the stock ROM Oreo flashable https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 and follow the instructions to install it (i.e. push to your device, or copy to an SD card, then tap install in TWRP to flash it to your device). This TWRP flashable should work on your TWRP version since it's 32 bit.
The stock ROM download would still require fastboot, so I'm not sure why your fastboot is not working. What fastboot are you using (is it minimal ADB/fastboot or the Google ADB) and have you downloaded/installed the Motorola USB drivers as well? https://support.motorola.com/us/en/drivers
(As you probably found out, error 255 when flashing custom Oreo or Pie ROMs means that your TWRP is 32 bit, whereas the custom ROM requires a 64 bit TWRP. What 64 bit TWRP are you flashing that are not successful, and how are you flashing the 64 bit TWRP, via fastboot or in TWRP?)
Click to expand...
Click to collapse
HI Echo92,
Thanks a ton and you are really awesome. It worked and I'm really thankful to you again Echo.
For the later questions:
I haven't been using the 64bit TWRP for flashing this Custom Pie ROM which was my mistake. I was using 32bit and doing on TWRP directly. What version of TWRP should I use in order to install the Custom Pie ROM I've mentioned in this reply Echo? Could you please share the link or help me with the version.
Thanks a ton and ahead again Echo.
chintu008 said:
HI Echo92,
Thanks a ton and you are really awesome. It worked and I'm really thankful to you again Echo.
For the later questions:
I haven't been using the 64bit TWRP for flashing this Custom Pie ROM which was my mistake. I was using 32bit and doing on TWRP directly. What version of TWRP should I use in order to install the Custom Pie ROM I've mentioned in this reply Echo? Could you please share the link or help me with the version.
Thanks a ton and ahead again Echo.
Click to expand...
Click to collapse
Try https://forum.xda-developers.com/mo...t/recovery-team-win-recovery-project-t3842903 or https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206
Both are 64 bit TWRP recoveries. You should be able to download them to your device, then install them via your existing TWRP recovery. Reboot to recovery then flash the 64 bit custom ROM and the relevant 64 bit (arm64) GApps package.
echo92 said:
Try https://forum.xda-developers.com/mo...t/recovery-team-win-recovery-project-t3842903 or https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206
Both are 64 bit TWRP recoveries. You should be able to download them to your device, then install them via your existing TWRP recovery. Reboot to recovery then flash the 64 bit custom ROM and the relevant 64 bit (arm64) GApps package.
Click to expand...
Click to collapse
I Tried to install both TWRP with fastboot but unfortunately my fastboot is not yet working Echo. It is looping infinite times when I tried any commands with fastboot.
chintu008 said:
I Tried to install both TWRP with fastboot but unfortunately my fastboot is not yet working Echo. It is looping infinite times when I tried any commands with fastboot.
Click to expand...
Click to collapse
As I mentioned, did you try to flash the recovery whilst booted into TWRP, instead of using fastboot? You should be able to install the zip then reboot to the recovery, then you should have 64 bit TWRP.
From presently installed TWRP on the device:
* Copy the .img file to your phone and reboot to recovery
* Tap Install > Choose Flash Image > Navigate to the path where you copied the .img file and choose it.
* Choose Recovery Partition
* After the install being successful, go to home and tap Reboot > Reboot Recovery.
At this point, twrp should greet you and after you allow modifications, do whatever you want to.*
Click to expand...
Click to collapse
Credit to https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206
Hi guys,
I have been reading similar threads and trying to find a solution but could not find what could help and ran into other issues. Hope someone can help me fix this.
I was trying to flash a custom ROM. had the device unlocked and installed twrp using adb.
It was a mistake to not back up. I tried to flash the firmware + extendedUI rom + magisk. Only magisk gave some error.
tried to reboot and got stuck in bootloop. Entered Twrp tried to do it again so wiped data,system,cache and then realised my folder with the rom disapeared. So now no OS and not sure what to do.
I was trying to use adb sideload to push the new zips on the device but the sideload just disconnects at 8% Understood that might drivers might be at fault. . Been trying to find and update drivers and might have done some mistakes there, as chose to update unknown device automatically with device manager and now it disappeared as well.
I read about recovering with Miflashtool but got confused whether thats the right way.
I would prefer to install a custom rom like the ExtendedUI or AOSPextended.
FuzzEdgar said:
Hi guys,
I have been reading similar threads and trying to find a solution but could not find what could help and ran into other issues. Hope someone can help me fix this.
I was trying to flash a custom ROM. had the device unlocked and installed twrp using adb.
It was a mistake to not back up. I tried to flash the firmware + extendedUI rom + magisk. Only magisk gave some error.
tried to reboot and got stuck in bootloop. Entered Twrp tried to do it again so wiped data,system,cache and then realised my folder with the rom disapeared. So now no OS and not sure what to do.
I was trying to use adb sideload to push the new zips on the device but the sideload just disconnects at 8% Understood that might drivers might be at fault. . Been trying to find and update drivers and might have done some mistakes there, as chose to update unknown device automatically with device manager and now it disappeared as well.
I read about recovering with Miflashtool but got confused whether thats the right way.
I would prefer to install a custom rom like the ExtendedUI or AOSPextended.
Click to expand...
Click to collapse
The zip files are to big to push them through adb sideload.
Just connect the cellphone to the pc while in twrp and mount otg