Related
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
coluichepensa said:
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
Click to expand...
Click to collapse
I have the same exact problem, however it also occurs when I try to install the zip directly from CWM...perusing the other threads it seems as though it's an issue with BusyBox overwriting some files in /system/bin. For the life of me I cannot find how to correct this issue even though the it is repeatedly mentioned in the threads that is has been covered already. Seeing as I'm nearing my wits' end, I'd appreciate someone pointing me in the right direction. Thanks in advance.:crying:
---------- Post added at 10:02 PM ---------- Previous post was at 09:42 PM ----------
Just to clarify this is what I get when I try to install 4.1.1:
Verifying current system...
assert failed: apply_patch_check
('/system/bin/gzip", "afdda757b27b444f525a0f41726d2c1a83012869", "5ba3b3ecd509cf6dcee37b2f27110310a1f55045")
E:Error in /cache/9ZGgDXDi.zip
(Status 7)
Installation aborted.
Even flashing 4.0.4 vias CWM doesn't overwrite the problematic /system/bin files. I got as far as trying to flash a factory image of 4.0.4 but got too frustrated with the fastboot commands in Terminal on OSX.
Again, while not a total neophyte, I could really use some hand holding regarding this mess. Thanks in advance.
Bumping in hope that some kind soul can walk me through replacing the /system/bin files that were overwritten by busybox. Tried factory reset and reflashing the 4.0.4 OTA to no avail. I think that flashing a factory image of 4.0.4 would work but I can't figure that out. I'm on OS X for what it's worth.
I appreciate your time.
Flashing through fastboot is rather simple. Can't remember the exact Mac commands of top of my head. But they are basically the same just fastboot-mac or whatnot.
Anyways if that is really a issue/ don't wanna bother with it. Look for the full stock ROM for your device and flash that with cwm. Make sure you wipe the old rom off first.
albundy2010 said:
Flashing through fastboot is rather simple. Can't remember the exact Mac commands of top of my head. But they are basically the same just fastboot-mac or whatnot.
Anyways if that is really a issue/ don't wanna bother with it. Look for the full stock ROM for your device and flash that with cwm. Make sure you wipe the old rom off first.
Click to expand...
Click to collapse
Thanks for the prompt reply. I dl'ed the factory image for my device (I9020T) from the developers/google site but couldn't get the ./flash-all.sh script to run. I then took the image.zip file from the factory tgz file and tried to flash it via CWM but got installation aborted/ Error 7 as well. Seems to be the only way to overwrite the system/bin filed that BusyBox replaced is to flash a factory image via fastboot.
Is there a way in which I can replace the problematic system/bin files that are preventing me from installing JB without flashing a stock factory image? And if there isn't, could I get some help with the Terminal commands for getting the /.flash-all.sh script to run on Mac?
Thanks again for your help and patience.
Those images are not mean to flashed through any recovery.
You can ignore that script. Extract what you have downloaded until you are left with ALL .img files. You should have system.img boot loader, radio, and userdata.img
Flash them one at a time with fastboot. Can't remember the exact Mac command but its fastboot flash system system.img etc for windows. Just look it for Mac. Think its fastboot-mac then the command but not sure. I hate Macs.
This has Mac fastboot info in it. I hate Macs also
http://forum.xda-developers.com/showthread.php?t=1789216
Edit: this has some info to help you also, I just change to Mac fastboot
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
jayjay3333 said:
This has Mac fastboot info in it. I hate Macs also
http://forum.xda-developers.com/showthread.php?t=1789216
Edit: this has some info to help you also, I just change to Mac fastboot
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Those two links were extremely helpful, thanks for that. I got as far as having all the requisite factory image files ready to be flashed in the same folder, but when I issue the command to flash the bootloader.img I get
Code:
-bash: ./fastboot-mac: Permission denied
.
Think I may have gotten a little over my head with this whole rooting business
For the record I am rooted and have an unlocked bootloader.
coluichepensa said:
Good morning,
I have the ICS 404 stock, rooted with CW 6.0.0.7. I downlaoded via ota the JB but the system was not able to install the new JB. How can solve this problem?? Do I have to install manually? Where is the file downloaded?? Someone can help me on the procedure to follow??
thanks
Click to expand...
Click to collapse
try latest touch version here http://bit.ly/QHLhXs when the update go to install in cmw there one dailoge box come choose yes and choose reboot and its appear again dailoge box choose yes disable recovery flash.
I solved the problem flashing this stock rom. http://forum.xda-developers.com/showthread.php?t=1784497
Finally sussed it out as well! Thanks to all for the help. Flashing the stock ICS image allowed me to install the JB OTA - will never install the BusyBox from the market again.
Cheers again to all.
I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.
did you install any mods, kernels, change any files? if so its been documented all over the forums.
No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.
danielvago said:
No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.
Click to expand...
Click to collapse
It didn't work. I have no idea what to do, can I sideload the APK?
Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).
danielvago said:
It didn't work. I have no idea what to do, can I sideload the APK?
Click to expand...
Click to collapse
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
Theory said:
Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).
Click to expand...
Click to collapse
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.
wantabe said:
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.
Click to expand...
Click to collapse
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
What is the error when the OTA fails?
Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data
try incremental install
danielvago said:
I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.
Click to expand...
Click to collapse
try sideloading 4.4.1 first. .and then sideload 4.4.2 after that. see if that works.
EddyOS said:
Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data
Click to expand...
Click to collapse
I just updated a new 2012 N7 from 4.1 to 4.4.2 and I couldn't get removing the -w flag to work. I think the script needs more editing than just removing the -w part. Something new I had never tried before which I actually don't personally have much use for because it still flashes the stock recovery over a custom recovery if you are using one. Anyway.. flashing the bootloader and radio separately and then flashing the update zip with "fastboot update image-hammerhead-kot49h.zip" would be a little bit of a shortcut versus flashing ALL of the images and you don't lose data.
Never had an issue myself, but I always prefer to flash each image manually one at a time
EddyOS said:
Never had an issue myself, but I always prefer to flash each image manually one at a time
Click to expand...
Click to collapse
I've always flashed each image separately also, I was just being lazy and experimenting. Removing the -w from the .bat and/or the .sh wouldn't work for me.
---------- Post added at 10:33 AM ---------- Previous post was at 10:27 AM ----------
danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.
wantabe said:
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.
Click to expand...
Click to collapse
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?
danielvago said:
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?
Click to expand...
Click to collapse
Your path to adb isn't correct. Put the zip file in the same folder as adb
jd1639 said:
Your path to adb isn't correct. Put the zip file in the same folder as adb
Click to expand...
Click to collapse
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.
danielvago said:
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.
Click to expand...
Click to collapse
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something
jd1639 said:
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something
Click to expand...
Click to collapse
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?
danielvago said:
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?
Click to expand...
Click to collapse
Ok, so you're doing an adb sideload while in recovery?
jd1639 said:
Ok, so you're doing an adb sideload while in recovery?
Click to expand...
Click to collapse
Yes.
"system partition has unexpected contents" March 2016 OTA or Sideload Failed Error 7
Hi,
My N5 is rooted and on factory images (6.0.1). I have reverted to stock recovery from twrp 3.0.0.0 because my system wouldn't accept Feb security updates.
After reverting to stock recovery, Feb updates worked fine.
March updates however continually fail with Error 7 (modified system partition?), either by system OTA or sideloading over adb / stock recovery.
I think, the last thing that I did was installed Wake Lock Detector, converted to a system app, this broke and couldn't be removed or converted back to a user app, so I had to force remove it via a convoluted system of Ti and other Root Uninstaller apps. Got rid of it in the end.
Anyway, this is the only thing I can think of that may be causing this Error 7, and I'm out of options. That's why I'm here.
The CM team seem to have some solutions to this issue. Anyone have any ideas for stock peeps?
Do I really need to unroot and reflash stock etc etc etc? I'd rather not.
Thanks, as ever, for the great support on XDA!
1. Check if the bootloader is hhz12k
2. Try use twrp 2.8.7.1 instead
3. Check adb version installed in your pc
I've gone back to pure stock...huge pain. Before I did this I reset to full stock, rooted and tested again...root broke the OTA and side load with error 7. Hence why I'm back unrooted and fully stock again. I want updates.
tedrogers61 said:
I've gone back to pure stock...huge pain. Before I did this I reset to full stock, rooted and tested again...root broke the OTA and side load with error 7. Hence why I'm back unrooted and fully stock again. I want updates.
Click to expand...
Click to collapse
Not many people replied to you as it has been said over and over and over. On marshmallow any change to system partition breaks the ability to apply OTAs. If you want the updates so bad, just download the new factory image and fastboot flash system.img. Then re-root. You wont lose data this way.
Thanks very much. I didn't know this and I swear I searched high and low...obviously not in the right areas. I ask a question on XDA when I feel I've googled the topic to death with no satisfactory outcome. So I can reflash a new system image over the top and all data remains intact? Good to know. Thank you.
tedrogers61 said:
Thanks very much. I didn't know this and I swear I searched high and low...obviously not in the right areas. I ask a question on XDA when I feel I've googled the topic to death with no satisfactory outcome. So I can reflash a new system image over the top and all data remains intact? Good to know. Thank you.
Click to expand...
Click to collapse
@tedrogers61: Make sure you only flash the system.img part - you have to do that manualy, dont use the .bat in the package.
Otherwise you WILL lose your data 100%, because the .bat file is flashing anything AND erase userdata+cache partition by default !
What you need to do :
1. Download factory image at https://developers.google.com/android/nexus/images#hammerhead
2. Use 7zip to unpack the .tgz, then again unzip the .tar, then unzip the image-hammerhead-mmb29v.zip (if you are using windows)
3. copy the system.img to a easy to find location (optional, just helps to find the system.img)
4. if you have USB Debug activated+USB cable + ADB installed (which i guess you have), connect your phone to USB, Phone runing normally and open a command prompt.
Enter these commands:
Code:
adb reboot bootloader
fastboot flash system <path-to-your-system.img>
On first command, the phone should reboot and display should show an android laying on his back
Next command should give you feedback in command prompt like "Erasing system"..."sending system"..."writing system".
The phone display should show similiar informations.
Thats it - you need to apply root after this.
You need to restart the phone manualy but as long as the command prompt shows OKAY and "finished. total time xyz seconds", everything worked fine.
Thank you @Warlord711, I worked out it was fastboot flash system system.img.
Testing this on my N5 right not which won't receive April OTA.
Might give this a go on my N5X later, which won't go past Feb OTA.
Is there a pattern here? Is there something wrong with my account which is preventing OTA's perhaps?
wangdaning said:
Not many people replied to you as it has been said over and over and over. On marshmallow any change to system partition breaks the ability to apply OTAs. If you want the updates so bad, just download the new factory image and fastboot flash system.img. Then re-root. You wont lose data this way.
Click to expand...
Click to collapse
Thank you very much.
tedrogers61 said:
Thank you @Warlord711, I worked out it was fastboot flash system system.img.
Testing this on my N5 right not which won't receive April OTA.
Might give this a go on my N5X later, which won't go past Feb OTA.
Is there a pattern here? Is there something wrong with my account which is preventing OTA's perhaps?
Click to expand...
Click to collapse
As mentioned, if anything is modified (root, custom recovery, etc) you will not be able to use OTA. Another problem, for people like me, cannot access google servers. Your google account is not linked to OTA, so it is not that. Doesn't really matter anyway, like you found, easy enough to just do it yourself. I live in China so have no choice anyway, haha, but it is simple. Personally, I do not use stock roms anyway, so don't really care.
After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it
This is really sad. They said it was going to be this week and a global roll out.
Nothing!
I can't wait until Samsung release the S8E.. Giving this phone to my 8 years old niece to have!
can u make some order here ?
what is your model ?
if u flashed 24.246-45 then u said it needs to be 40
then did u flash the 40 over 45 ?
thanks
hassanman1997 said:
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware,
Click to expand...
Click to collapse
This is really helpful. I hit the same snag when I tried to upgrade from -17 firmware.
Any chance you could upload the Canadian Rogers firmware (-45) to Mega? It's so painful waiting for 9 hours for it to fail a few minutes from the end.
Yeah I can try, but I won't be home until night, the only pain was waiting 9 hours, and the firmware is -45, I accidently wrote -40 , I don't think there is any firmware with-40
I tried all the above. Still fails for me.
---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------
I think because the file has been replaced with a v2 so it's failing verification
I'm uploading the Rogers .45 firmware to mega right now. I'll update this post once its done uploading.
Link: https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Downloaded straight from FileFactory and uploaded directly to Mega
Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome
svetius said:
Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome
Click to expand...
Click to collapse
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?
Prfndhatrdofman said:
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?
Click to expand...
Click to collapse
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
You got further than me. ADB Sideload wouldnt even look at the Nougat OTA zip. tried multiple ADB versions too
svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
Sideload was successful for me, but still completely in a bootloop as well..
for me it worked fine with ADB sideload.
my bootloader is unlocked, i tried locking it back to get official OTA but failed to lock it again.
I tried every method that was mentioned but failed over and over
so here is what I did:
1) removed all the personal files from phone (pictures, videos, texts etc) so i don't lose em
2) flashed the rogers [XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml] firmware by using mfastboot, make sure you grab the mfastbootv2, you can google and download it, use mfastboot and flash the firmware by command lines
3)after flashing, rebooted, set up the device and skipping a few steps to get into homescreen, and then powered off the phone.
4)downloaded Blur_Version.24.21.46.griffin.retail.en.US.zip and placed it in the adb folder, make sure you download the latest adb tools, you can google and find them easily too
5) extract the adb folder and place the Blur_Version.24.21.46.griffin.retail.en.US.zip in side that folder
6) reboot the phone and press volume to navigate to recovery, you should boot into stock recovery as you flashed stock firmware
7) hold power button and press volume up and youll see the menu, select update by ota and connect to the phone
8) open command line in the adb tools and use command to flash ota via adb
9) mine failed at 95% because of system image error, so instead of rebooting it, i used the command again and flashed the ota via adb, it failed again, however when i rebooted i was presented by the new red moto boot animation, there i knew it was updated to android N
*Delete*
hassanman1997 said:
After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it
Click to expand...
Click to collapse
OK, so i got it working. But there were some difficulties.
I was on 24.246-45 already, but i installed TWRP and a custom kernel. I reflashed the recovery and boot from the BELL 24.246.45 firmware, and proceeded sideloading the update. It errored out, saying system was mounted r/w once (after I installed TWRP, but I never altered it beyond that).
So i flashed the system chunks from the firmware ( "mfastboot flash system system.img_sparsechunk.0" , "mfastboot flash system system.img_sparsechunk.1" etc.), then i retried the sideload, and it worked. The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.
gomisensei said:
... The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.
Click to expand...
Click to collapse
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...
enetec said:
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...
Click to expand...
Click to collapse
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...
gomisensei said:
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...
Click to expand...
Click to collapse
:laugh:
Does that actually work for other software channels as well?
I'm from india, my software chanel is retin (retail India) can I still flash the one that came for retus?
Sent from my Moto Z using XDA Labs
Hello,
i need your help with my htc u 12+., please (
What happened
While I was happily using the phone a pop up from Magisk manager showed up, asking if I wanted to update. I said ok.
Magisk manager updated. Then it asked to update Magisk itself to 17.1. Checked on XDA if it was stable. It was. I chose the suggested method and tapped ok.
Here's where the nightmare begins. The installation seemed successful but the phone couldn't boot properly. The HTC animation stopped suddenly on the three green dots and the phone didn't react at all. It was not really a bootloop, it was like it couldn't boot any more.
What I did
Tried not to freak out and managed to boot into bootloader and then recovery. Tried to uninstall magisk through the magisk uninstaller, couldn't do it.
I didn't know if I could install Magisk 16.0 over a newer version, and I preferred not to try by luck. So I decided to restore a previous NAND Back up I had made. The NAND backup could restore everything but the /vendor partition.
Now, the phone successfully reboots but:
- I have no root (Magisk is gone)
- when I plug my USB cable, it only charges. No communication between the phone and the PC, unless I boot into bootloader (then the connection is there again and I can use fastboot commands). When I go to Developer options, no matter what communication protocol I choose for USB, it sticks to "Charge". Debug USB is ON, of course.
Tried to install Magisk again through a temporary TWRP, but the issue is still there: I can't mount /vendor partition and it fails.
I've looked for a solution here and there; what I found out is that I should use a treble-enabled TWRP, but my limited knowledge doesn't help me with that.
Please could you help me? It's crazy how messy can be just tapping ok on a notification :crying:
EDIT - FIXED:
To restore the USB communication, flashing the RUU solved the problem.
Using the patched boot.img method to install Magisk could succesfully work around the /vendor issue.
Huge thanks to the guys who helped, that was essential.
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
I had the same issue this morning and finally figured it out. Just use the new uninstaller from the magisk thread. Once you flash that in twrp you will be able to install the new magisk without any problems!
MNoisy said:
I had the same issue this morning and finally figured it out. Just use the new uninstaller from the magisk thread. Once you flash that in twrp you will be able to install the new magisk without any problems!
Click to expand...
Click to collapse
Unfortunately, the new uninstaller is the one that doesn't work for me due to the /vendor partition, that my TWRP is not able to mount..
Tachi91 said:
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
Click to expand...
Click to collapse
Thank you, maybe this one will help me.
Should I check something before trying ? (like CID.. or.. something else?)
And can I launch the RUU when I'm in bootloader mode? It's the only way I have to make the PC recognize the device.
EDIT: trying to launch the RUU, but after a few clicks it closes.. maybe my PC can't find a device, even in bootloader mode, and the software is shut down.
Tachi91 said:
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
Click to expand...
Click to collapse
[canceled]
sbiricuda said:
Unfortunately, the new uninstaller is the one that doesn't work for me due to the /vendor partition, that my TWRP is not able to mount..
Click to expand...
Click to collapse
I was having the same issue with error 2 and 255 (Maybe 225?) with the vendor mount problem. I think I rebooted/changed from slot a to slot b then back again. Then I was able to run uninstaller and the new installer. System and vendor were both unchecked and automatically mounted with the magisk script during the new install.
I actually recommend flashing the stock boot image before you do any of this to. You should not have to RUU. I had the identical problems today.
MNoisy said:
I was having the same issue with error 2 and 255 (Maybe 225?) with the vendor mount problem. I think I rebooted/changed from slot a to slot b then back again. Then I was able to run uninstaller and the new installer. System and vendor were both unchecked and automatically mounted with the magisk script during the new install.
I actually recommend flashing the stock boot image before you do any of this to. You should not have to RUU. I had the identical problems today.
Click to expand...
Click to collapse
So basically I should give:
fastboot --set-active=a
fastboot --set-active=b
(or vice versa if i'm on A)
right?
And where can i get the stock boot? The NAND-restore restored the /boot I had just after unlocking the bootloader, it's a very early nand-backup. Should I still flash the stock boot image?
Anyway, if only I could connect my phone stuck on "just charge" USB option, I wouldn't mind to RUU and start over again. The phone only has two days, it won't take long to set it up again.
sbiricuda said:
So basically I should give:
fastboot --set-active=a
fastboot --set-active=b
(or vice versa if i'm on A)
right?
And where can i get the stock boot? The NAND-restore restored the /boot I had just after unlocking the bootloader, it's a very early nand-backup. Should I still flash the stock boot image?
Anyway, if only I could connect my phone stuck on "just charge" USB option, I wouldn't mind to RUU and start over again. The phone only has two days, it won't take long to set it up again.
Click to expand...
Click to collapse
I did mine through a temporary boot of twrp
Stock boot images can be found in the spreadsheet linked in the second post of the image/firmware/boot/OTA thread here
Boot to download mode
temporary boot twrp
install stock boot image only (From thread linked above)
After the boot image is installed, to be safe, you might want to reboot again to download mode and then temporary boot twrp again just to ensure the boot image installation completed fully and is recognized (Just a guess based on my experience)
Now that you are back in twrp with the stock boot image installed, run the new magisk uninstaller (You should not need to worry about mounting anything since the magisk script does it automatically if not mounted)
Once uninstaller is complete, install the new magisk 17.1 through twrp and you should be good to go.
If you have issues with errors, try the process again. If still having issues, use the reboot menu in TWRP to switch slots back and forth and then try again.
It took me a good 30 min to find the combination that worked but it consisted of the steps above. 7 minutes of it was trying to get the damn phone to stop boot looping but my finger kept double tapping or screwing up the pressure to hold down power!
MNoisy said:
I did mine through a temporary boot of twrp
Stock boot images can be found in the spreadsheet linked in the second post of the image/firmware/boot/OTA thread here
Boot to download mode
temporary boot twrp
install stock boot image only (From thread linked above)
After the boot image is installed, to be safe, you might want to reboot again to download mode and then temporary boot twrp again just to ensure the boot image installation completed fully and is recognized (Just a guess based on my experience)
Now that you are back in twrp with the stock boot image installed, run the new magisk uninstaller (You should not need to worry about mounting anything since the magisk script does it automatically if not mounted)
Once uninstaller is complete, install the new magisk 17.1 through twrp and you should be good to go.
If you have issues with errors, try the process again. If still having issues, use the reboot menu in TWRP to switch slots back and forth and then try again.
It took me a good 30 min to find the combination that worked but it consisted of the steps above. 7 minutes of it was trying to get the damn phone to stop boot looping but my finger kept double tapping or screwing up the pressure to hold down power!
Click to expand...
Click to collapse
Seems that I have no luck. The provided boot.img in the spreadsheet is for US unlocked variant, while I have the european version. Maybe it's the same, but the point is that when I open the AFH page to download, it says "for HTC U11".
Did you try extracting the boot image from the RUU that corresponds your current firmware version? The needed decryption tool is linked in the same thread in which you found the spreadsheet.
Flashing a US RUU on a European phone without S-OFF isn't possible, btw. That's why you faced those errors, earlier.
Sent from my HTC U12+ using XDA Labs
The U11 is just a typo, it is the right stuff. You have a couple options since there is no signed stock boot available on the spreadsheet. Simply download the RUU and decrypt the payload using the instructions in the OP of the post I already provided or go to here and find yours (It is there, I checked )
Tachi91 said:
Easy fix. Flash the RUU and be on your marry way.
Thatll flash EVERYTHING back to stock. Then restore your data via TWRP that you had saved on a USB or microsdcard.
I also updated to the latest magisk, but everything is working just fine for me. (64Gig US unlocked version)
---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------
https://www.htc.com/us/support/updates.aspx
Click to expand...
Click to collapse
Good news and bad news.
The good news is that I managed to flash the RUU through TWRP. That flashed everything to stock, as you said.
This is particularly good because it also fixed the USB problem.
I have now a working stock device.
The bad news is: I can't flash Magisk any more.
I did just the same I did two days ago, when everything worked perfectly.
This time I keep getting the same error (photo: https://s8.postimg.cc/b6plbphx1/20180902_182259.jpg).
If I try to restore a NAND back up, I always get the /vendor error and I can't restore. The device then bootloops (meaning that I have to flash the RUU again to make it work).
So the main problem is now this one:
how can I deal with this /vendor error and install Magisk?
Thank you (to Mnoisy as well, of course, for his help in the previous post!).
sbiricuda said:
Good news and bad news.
The good news is that I managed to flash the RUU through TWRP. That flashed everything to stock, as you said.
This is particularly good because it also fixed the USB problem.
I have now a working stock device.
The bad news is: I can't flash Magisk any more.
I did just the same I did two days ago, when everything worked perfectly.
This time I keep getting the same error (photo: https://s8.postimg.cc/b6plbphx1/20180902_182259.jpg).
If I try to restore a NAND back up, I always get the /vendor error and I can't restore. The device then bootloops (meaning that I have to flash the RUU again to make it work).
So the main problem is now this one:
how can I deal with this /vendor error and install Magisk?
Thank you (to Mnoisy as well, of course, for his help in the previous post!).
Click to expand...
Click to collapse
Have you tried switching to slot A in TWRP? Since it can't mount /system_B maybe it'll mount system A?
Flippy498 said:
Did you try extracting the boot image from the RUU that corresponds your current firmware version? The needed decryption tool is linked in the same thread in which you found the spreadsheet.
Flashing a US RUU on a European phone without S-OFF isn't possible, btw. That's why you faced those errors, earlier.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Since I was facing USB issues (no communication via USB betwenn the device and the PC), I flashed the whole RUU. I'm now completely stock 1.21.
As I mentioned, the problem is now that I can't root again.
Tachi91 said:
Have you tried switching to slot A in TWRP? Since it can't mount /system_B maybe it'll mount system A?
Click to expand...
Click to collapse
I have read that this is very dangerous, and in fact I have no clue about what the consequences may be.
Do you suggest to switch to slot A and flash magisk?
You might want to try going through my steps to ensure you have a stock signed boot image on there and proceed through the steps listed.
sbiricuda said:
I have read that this is very dangerous, and in fact I have no clue about what the consequences may be.
Do you suggest to switch to slot A and flash magisk?
Click to expand...
Click to collapse
It's not dangerous. You'll get stuck on a bootloop since more often than not most phones don't have anything on there. If you did have an OTA you end up on the older system. Which would cause issues since your data partition would be cached to newer software.
Either way you have an RUU that will fix the phone. S-OFF isn't permanent and I'm assuming you don't have it. With S-ON the odds of a bricking is minimal.
MNoisy said:
You might want to try going through my steps to ensure you have a stock signed boot image on there and proceed through the steps listed.
Click to expand...
Click to collapse
I'm not sure TWRP does a good job since RUU when done correctly puts the phone in OEM RUU mode. TWRP possibly doesn't flash all the partitions since it might not have access to them. I'm surprised the zip worked in TWRP.
Full RUU zip is about 2gigs. (Single Sim)
MNoisy said:
You might want to try going through my steps to ensure you have a stock signed boot image on there and proceed through the steps listed.
Click to expand...
Click to collapse
Tachi91 said:
It's not dangerous. You'll get stuck on a bootloop since more often than not most phones don't have anything on there. If you did have an OTA you end up on the older system. Which would cause issues since your data partition would be cached to newer software.
Either way you have an RUU that will fix the phone. S-OFF isn't permanent and I'm assuming you don't have it. With S-ON the odds of a bricking is minimal.
I'm not sure TWRP does a good job since RUU when done correctly puts the phone in OEM RUU mode. TWRP possibly doesn't flash all the partitions since it might not have access to them. I'm surprised the zip worked in TWRP.
Full RUU zip is about 2gigs. (Single Sim)
Click to expand...
Click to collapse
I have installed the RUU through TWRP. I had to use the 1.15 because the 1.21 gave me an error about the CID that was not coincident (but I'm sure I picked the right RUU in the spreadsheet, for my CID, the HTC__034).
So i restored the 1.15, and then installed the OTA update to 1.21. This is my current situation. And yes, I'm S-ON.
What I could do is either:
- I try to decrypt the boot.img from the RUU in the spreadsheet (but using the tool seems sooo complicated, I'm reading the thread over and over not understanding much), or
- I use the .exe version of the 1.21 RUU, from the HTC official website. If I do that, can we be sure that I have a signed boot.img? And can this work around the TWRP limits about partitions?
Oh, something I forgot to mention: I did try the switching trick MNoisy suggested (switching the slots and then switiching back), but it didn't work.