Related
Hi everyone, my XT925 is stuck in fastboot, and whenerver I try to flash it everything just fails; RSD shows this when I try to flash:
Failed flashing process. 1/20 flash partition "partition signed" -> Phone returned FAIL
I tried to flash this stock rom: XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-26 1359487946
I had already rooted the phone and unlocked the bootloader too, and when I did an OTA update all hell broke loose, the phone now goes directly to fastboot mode, and shows this:
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
It also says Phone is LOCKED, Status Code:0
I think this means that somehow the bootloader is locked but I have already unlocked it; I don't know what to do, please help
Some Help
Hi, the same thing happened to me when I tried a ROM from a VFR on my LATAM RAZR HD. The OTA messed everything up.
You can check how I solved it on the thread I created asking for help:
http://forum.xda-developers.com/showthread.php?t=2273574
Basically you need to treat your phone as LOCKED bootloader, meaning only flashing of a version that belongs to the region of your phone and newer or same version as the failed OTA will allow you to flash. Since this is the only way LOCKED bootloader phones will flash.
Rokwenelenya said:
Hi everyone, my XT925 is stuck in fastboot, and whenerver I try to flash it everything just fails; RSD shows this when I try to flash:
Failed flashing process. 1/20 flash partition "partition signed" -> Phone returned FAIL
I tried to flash this stock rom: XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-26 1359487946
I had already rooted the phone and unlocked the bootloader too, and when I did an OTA update all hell broke loose, the phone now goes directly to fastboot mode, and shows this:
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
It also says Phone is LOCKED, Status Code:0
I think this means that somehow the bootloader is locked but I have already unlocked it; I don't know what to do, please help
Click to expand...
Click to collapse
still cannot flash
I tried to flash this firmware, it's the more recent from telcel: 9.8.2Q-50-XT925_VQLM-21_AmericaMovil_MX_SIGNED_S12_USAVANQUTELMXLA020.0R_VANQJBTELMXLA_P009_A013_S1FF_v2_CFCv2_fb.xml
it didn't work
what can I do????
Is your phone from Telcel Mexico originally?
I ask because on my case it is. The firmware you need to flash has to be the latest one based on your phone region, on my case I flashed the Brasil Retail. Because my phone is from Latin America. So it will depend on were your phone is from. This is all because your phone is acting up as LOCKED bootloader so flashing a version from another region is not possible.
Also because your phone got stuck on an OTA you need to make sure the version you flash is at least the same one as the OTA, newer if possible.
Rokwenelenya said:
I tried to flash this firmware, it's the more recent from telcel: 9.8.2Q-50-XT925_VQLM-21_AmericaMovil_MX_SIGNED_S12_USAVANQUTELMXLA020.0R_VANQJBTELMXLA_P009_A013_S1FF_v2_CFCv2_fb.xml
it didn't work
what can I do????
Click to expand...
Click to collapse
Worked but not completely
Ok, I flashed the rom that you recomended, the phone finally boots into android, but now is always on "emergency calls only" mode, with or without Sim card any suggestions?
Phone should be back as unlocked bootloader
If you flashed a version fine now, I'm sure that at least you should be able to go into fastboot and see your bootloader as unlocked.
If this is true, then you can go ahead and flash any version available, either being an older Stock version (downgrade) or any custom ROM of your liking, like CM 10.1. You should try them and see if you get a proper signal.
Also in your case, if your bootloader is unlocked again, I recommend you installing the version that you know worked fine for you. It won't matter that it's older than the one you flashed right now. It's just a matter of following the guide for unlocked bootloaders to downgrade versions.
Good luck! :fingers-crossed:
Phone almost repaired
Ok, I flashed the latest stock rom from telcel, the phone is no longer on emergency call mode, the wifi and data connection works fine, but it always shows that there is no reception from my carrier, I can't make calls or send sms because when I try it the phone shows "mobile network not available", the funny thing is that I can connect to de data network from my carrier. What can be causing this trouble?
Honestly I have not faced this before it sounds very weird!
I can think of two possibilities, one your phone lost it's IMEI. You should check if it's still there, either by going through configuration and Phone Information or by the "secret code" on the dialer: *#*#4636#*#*
And in the following menu go into Phone Information. The first thing you should see is your IMEI. If it's not there, look for the how to restore your IMEI thread on here. I know it's there somewhere.
The second thing I can think of is to try to force your phone into your carrier, go into Cellular Networks area and manually choose your provider, this could force the registration.
Hopefully this will be of help!
Rokwenelenya said:
Ok, I flashed the latest stock rom from telcel, the phone is no longer on emergency call mode, the wifi and data connection works fine, but it always shows that there is no reception from my carrier, I can't make calls or send sms because when I try it the phone shows "mobile network not available", the funny thing is that I can connect to de data network from my carrier. What can be causing this trouble?
Click to expand...
Click to collapse
Fastboot Error / Invalid GPT
Rokwenelenya said:
Hi everyone, my XT925 is stuck in fastboot, and whenerver I try to flash it everything just fails; RSD shows this when I try to flash:
Failed flashing process. 1/20 flash partition "partition signed" -> Phone returned FAIL
I tried to flash this stock rom: XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-26 1359487946
I had already rooted the phone and unlocked the bootloader too, and when I did an OTA update all hell broke loose, the phone now goes directly to fastboot mode, and shows this:
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
It also says Phone is LOCKED, Status Code:0
I think this means that somehow the bootloader is locked but I have already unlocked it; I don't know what to do, please help
Click to expand...
Click to collapse
adolfovm said:
Hi, the same thing happened to me when I tried a ROM from a VFR on my LATAM RAZR HD. The OTA messed everything up.
You can check how I solved it on the thread I created asking for help:
http://forum.xda-developers.com/showthread.php?t=2273574
Basically you need to treat your phone as LOCKED bootloader, meaning only flashing of a version that belongs to the region of your phone and newer or same version as the failed OTA will allow you to flash. Since this is the only way LOCKED bootloader phones will flash.
Click to expand...
Click to collapse
Hello,
I have an xt926 and I tried to take the latest OTA upgrade.
My bootloader was unlocked, and I temporarily un-rooted with Voodoo OTA Rootkeeper.
My phone then got stuck in Fastboot with the same errors:
Phone is LOCKED, Status Code:0
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
I can't get the phone out of fastboot with the error messages.
The Windows Utility returned <remote access failure>
RSD returned <getvar errors>
(I tried deleting the 2 <getvar> lines in the .xml files, but then RSD said phone returned failure "sbl1.mbn".
I downloaded & installed the adb package, and I got the phone to respond to fastboot commands, but it still ended up in Fastboot with the above list of errors.
Any suggestions?
Thanks
doctorwho2 said:
Hello,
I have an xt926 and I tried to take the latest OTA upgrade.
My bootloader was unlocked, and I temporarily un-rooted with Voodoo OTA Rootkeeper.
My phone then got stuck in Fastboot with the same errors:
Phone is LOCKED, Status Code:0
Downgraded secutiry version
Update gpt_main version failed
Failed to hab check for gpt_backup:0x35
failed to load GPT
CID read failure
Invalid CID status 0x69
No SP partition found
Fastboot reason: Invalid GPT
I can't get the phone out of fastboot with the error messages.
The Windows Utility returned <remote access failure>
RSD returned <getvar errors>
(I tried deleting the 2 <getvar> lines in the .xml files, but then RSD said phone returned failure "sbl1.mbn".
I downloaded & installed the adb package, and I got the phone to respond to fastboot commands, but it still ended up in Fastboot with the above list of errors.
Any suggestions?
Thanks
Click to expand...
Click to collapse
try this and let me know if it works please. its a test build to fix this issue.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Thanks
bweN diorD said:
try this and let me know if it works please. its a test build to fix this issue.
link
thanks
Click to expand...
Click to collapse
Thanks to you, it really work for me. My Motorola RAZR HD its now alive.
other possible solution that worked for me is
flashing this
http://sbf.droid-developers.org/download.php?device=6&file=119 (CLARO PR Jelly Bean)
Thanks!
suggestions for XT 925 please?
bweN diorD said:
try this and let me know if it works please. its a test build to fix this issue.
http://www.mediafire.com/download/987490ykl14j4t8/DROID_RAZR_HD_Utility_1.3.gpt_fix.rar
thanks
Click to expand...
Click to collapse
hbenz2008 said:
suggestions for XT 925 please?
Click to expand...
Click to collapse
replace the files in the tool with the files for your region. delete all the files for the 926 if any are left in there before flashing, so they arent flashed by mistake. also if any of your file names are not exactly the same as the current files inside, you will need to edit the batch file and fix the names.
if you dont want to do all that, you can get Mfastboot and flash your files to the phone manually one at a time starting with the partition file.
unable to flash partition signed
Hi.
I downloaded the SBF from sbf.droid-developers.org/phone.php?device=6 for my region(canada).
I proceeded to try to do universal through the RSD:
Filename: UNIVERSAL.xml
Creation Date: 11/23/2014 09:11:58
File size: 1589
Sofware Version: XT925_rcica-user 4.1.2 9.8.2Q-8-XT925_VQL-12.2 1356031681 release-keysVANQUISH_U_BP_100700.220.65.33P
For Phone Model: VANQUISH_U
I got failed flash process 1/18 flash partition "partition_signed"
Before this, my phone was working fine. Got the kitkat update pushed to me and after update it was working fine. I was using it until my battery ran out so i turned it off. Afterwards, it just got stuck at the motorola logo. I tried to update it with xt926 didn't realize that my phone is xt925. Anyways, i got the bootloader unlocked. Tried the above but failed.
Any help is appreciated!
Thanks!
what did you have on your phone before flashing it the first time? you can try reflash and edit xml before doing that, delete "getvar" line from it.
hbenz2008 said:
what did you have on your phone before flashing it the first time? you can try reflash and edit xml before doing that, delete "getvar" line from it.
Click to expand...
Click to collapse
I just got help from another thread. Followed it and it worked!!
http://forum.xda-developers.com/showthread.php?t=2760840&page=72
bweN diorD said:
replace the files in the tool with the files for your region. delete all the files for the 926 if any are left in there before flashing, so they arent flashed by mistake. also if any of your file names are not exactly the same as the current files inside, you will need to edit the batch file and fix the names.
if you dont want to do all that, you can get Mfastboot and flash your files to the phone manually one at a time starting with the partition file.
Click to expand...
Click to collapse
Originally had my RAZR HD firmware Telstra Australia, having unlocked bootloader I pass Retail Retail France and then to Brazil to upgrade to KitKat, where brick. I you explain how serious the replace files.
I have the Firmware Jelly bean in all regions, but are replaced with files jelly bean? and addresses of the partitions also be accommodated to those that are in the XML file jelly bean?
edwint290 said:
Originally had my RAZR HD firmware Telstra Australia, having unlocked bootloader I pass Retail Retail France and then to Brazil to upgrade to KitKat, where brick. I you explain how serious the replace files.
I have the Firmware Jelly bean in all regions, but are replaced with files jelly bean? and addresses of the partitions also be accommodated to those that are in the XML file jelly bean?
Click to expand...
Click to collapse
i dont really understand what you are asking.
you need to figure out which is the most recent partition table you have put on the phone successfully and flash that first. nothing will work correctly until you do. after you get a successful partition flash, you can flash whatever you want, just DO NOT flash the partition file again from any other version. old builds will work on the newer partition table.
So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Saw the probable solution on another post.
mdecaminop said:
So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Click to expand...
Click to collapse
In these forums somewhere I read that the unroot was done using Super su's full unroot option. However it apparently left behind a few files that caused the OTA to fail. So what he did was to uninstall Supersu, reinstall Supersu and update the binary. Then use full unroot function... Maybe it will work for you if you have unrooted using SUpersu...
Unrooting, locking the bootloader, and flashing the stock recovery doesn't allow you to take OTA's.
There is THIS thread, providing OTA files that can be flashed in TWRP or CWM. And are official files from Nvidia.
You have to flash these every time there's an OTA, or just flash a full stock image through fastboot, and never root or flash a recovery.
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
mycologik said:
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
Click to expand...
Click to collapse
Well it seems my second hand tablet has been rooted as well ... I've got the exact same problem that yours ...
Is there a way to go back as out of the box ?
I bought a China set of OPO last month. I thought this phone originally installed Color Os rom and then re-installed to CM11s 44s version when it selling. When I turned on the phone for the first time, I already get the update notification for the 05q version. So, I tried to update it but it failed to update it for many times that I tried. My phone rebooted when I clicked "flash updates" and loading for a while then failed in cyanogen recovery. I also tried with manually update with downloaded zip file and installed it in cyanogen recovery. It still failed with mentioned "system 7..." message. Is there any way to fix this problem if I want to flash cm11s latest update firmware, rather than use other custom roms? ??
It's impossible to know what the seller did to the phone before you got it so it's probably a good idea to flash the stock images and start from scratch. Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
If your bootloader is locked you'll need to unlock it, but be aware that doing so wipes all user data. Install TWRP recovery and make a nandroid backup of your current setup just in case. Then flash the stock images using fastboot.
Transmitted via Bacon
Actually, what does "system error 7" means when installation?
Here you go
johnsin5393 said:
Actually, what does "system error 7" means when installation?
Click to expand...
Click to collapse
Here you will find what is System 7 error and how to fix it.
http://forum.xda-developers.com/showthread.php?t=2522762
I bought a Nexus 5 (refurbished) from Freedom Pop. I can't remember what version is came with, maybe 4.4.4. First thing I did with it was install CWM (6.0.4.7) and flash the Google Nexus 5 factory image (5.1.1 / LMY48B) and root the device. Now that LMY48I is out, I got a OTA notification about a system update. When I try to do the OTA update, it fails. So I downloaded the update zip to take LMY48B->LMY48I from http://www.droid-life.com/2015/08/10/download-nexus-4-5-6-7-9-10-ota-stagefright-patches/ . I boot into CWM and install zip, but it fails with:
Package expects build fingerprint of google/hammerhead/hammerhead:5.1.1/LMY48B/1863243:user/release-keys; this device has google/hammerhead/hammerhead:4.4.2/KOT49H/937116 Instllation aborted.
When I go to Settings, System, it shows I have LMY48B. Why does the install think I have KOT49H? When I flashed the factory image it did it not update some file somewhere and if so, how can I get that file to accurately report what I'm running?
Thanks,
exhibit679 said:
I bought a Nexus 5 (refurbished) from Freedom Pop. I can't remember what version is came with, maybe 4.4.4. First thing I did with it was install CWM (6.0.4.7) and flash the Google Nexus 5 factory image (5.1.1 / LMY48B) and root the device. Now that LMY48I is out, I got a OTA notification about a system update. When I try to do the OTA update, it fails. So I downloaded the update zip to take LMY48B->LMY48I from http://www.droid-life.com/2015/08/10/download-nexus-4-5-6-7-9-10-ota-stagefright-patches/ . I boot into CWM and install zip, but it fails with:
Package expects build fingerprint of google/hammerhead/hammerhead:5.1.1/LMY48B/1863243:user/release-keys; this device has google/hammerhead/hammerhead:4.4.2/KOT49H/937116 Instllation aborted.
When I go to Settings, System, it shows I have LMY48B. Why does the install think I have KOT49H? When I flashed the factory image it did it not update some file somewhere and if so, how can I get that file to accurately report what I'm running?
Thanks,
Click to expand...
Click to collapse
You must return to stock before you attempt to install that zip. That means you cannot be rooted or have custom recovery in place
I've got a stock N5 I bought from Google on LMY48B and there's still no update for me.
Does anyone know what the roll-out timeline is for the LMY48I?
When should I conclude that I'm not going to get it OTA and resign myself to factory wipe and flashing the image?
I have a stock Nexus 5, rooted w/ cf-auto-root, re-locked , no custom recovery or bootloaders, and all i see is Error when trying to install this OTA. I'm stuck at the moment myself. Installing the OTA should just unroot my phone, but it won't install. Currently running on 5.1.1 (LMY48B) myself.
Nemesis02 said:
I have a stock Nexus 5, rooted w/ cf-auto-root, re-locked , no custom recovery or bootloaders, and all i see is Error when trying to install this OTA. I'm stuck at the moment myself. Installing the OTA should just unroot my phone, but it won't install. Currently running on 5.1.1 (LMY48B) myself.
Click to expand...
Click to collapse
Mine is stock, un-rooted, but I too keep getting an Error when trying to install the OTA. Stuck on LMY48B at the moment.
moeREM said:
Mine is stock, un-rooted, but I too keep getting an Error when trying to install the OTA. Stuck on LMY48B at the moment.
Click to expand...
Click to collapse
I have the same problem her as well with my nexus 5 it keeps saying error with little droid I've tried side loading manually but it didn't work also tried hard reset and wiping cache but nothing solved the problem so i just figured out the problem is the package it self
Same problem here
Same thing here, error with little droid picture on rooted android 5.1.1.
Has anyone found the reason for this ?
Try flashing system image directly
Sent from my Nexus 5 using Tapatalk
lpganesh said:
Try flashing system image directly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This possibility makes me spend a lot of time, becouse i have lcd_density changed and all apps when i restore a backup are not in the main screen.
walt disney said:
Same thing here, error with little droid picture on rooted android 5.1.1.
Has anyone found the reason for this ?
Click to expand...
Click to collapse
This method is for anyone with lmy48b that's rooted or has a radio, kernel or recovery custom flashed.
Condensed version but here's the important pieces. You will lose root if you are unrooted. You will not lose any data or settings if done this way.
Step 1. Download lmy48b from google
Step 2. Unzip lmy48b package
Step 3. Copy bootloader, radio and system.img from lmy48b package (unzip zipped file for bootloader and system.img)
Step 4. Connect phone and boot into bootloader
Step 5. Type in fastboot flash recovery [recovery].img replace [recovery] with the actual file name
Step 6. Type in fastboot flash radio [radio].img
Step 7. Type in fastboot flash system [system].img
Step 8. Reboot
Step 9. Update via OTA
Working - confirmed
cloney said:
This method is for anyone with lmy48b that's rooted or has a radio, kernel or recovery custom flashed.
Condensed version but here's the important pieces. You will lose root if you are unrooted. You will not lose any data or settings if done this way.
Step 1. Download lmy48b from google
Step 2. Unzip lmy48b package
Step 3. Copy bootloader, radio and system.img from lmy48b package (unzip zipped file for bootloader and system.img)
Step 4. Connect phone and boot into bootloader
Step 5. Type in fastboot flash recovery [recovery].img replace [recovery] with the actual file name
Step 6. Type in fastboot flash radio [radio].img
Step 7. Type in fastboot flash system [system].img
Step 8. Reboot
Step 9. Update via OTA
Click to expand...
Click to collapse
Thanks, confirmed that this method worked. Managed to update my rooted nexus 5 to LMY48I
Tried to install ota update after reverting to stock recovery using Simple Recovery Switcher app. However, also the error message, with little Android picture also appears. Please help
I assume this removed your root, though.
It seems we are getting a new factory image en september to properly solve the stagefright bug
"A second patch has been sent out. "We’ve already sent the fix to our partners to protect users, and Nexus 4/5/6/7/9/10 and Nexus Player will get the OTA update in the September monthly security update"
I have decided i will stay at 5.1.1 untill Android M maybe september also. In the meanwhile i have disabled MmsService and OTA.
Pastorelli's said:
It seems we are getting a new factory image en september to properly solve the stagefright bug
"A second patch has been sent out. "We’ve already sent the fix to our partners to protect users, and Nexus 4/5/6/7/9/10 and Nexus Player will get the OTA update in the September monthly security update"
I have decided i will stay at 5.1.1 untill Android M maybe september also. In the meanwhile i have disabled MmsService and OTA.
Click to expand...
Click to collapse
I'm with you, not going to try to flash these things, there are a few zip files out there dated a couple days ago, apparently the zips aren't tested prior to release since everyone is getting failure when flashing the zip file.
Is there really no method to apply OTA updates on rooted/modified devices (e.g. modify the update.zip itself to bypass whatever checks it performs)?
Same problem here- only had a custom recovery and root. brought back the stock recovery and did full unroot from SuperSu.
OTA update installtion stops with "Error".
Just flash the system image from the update.
Sent from my Nexus 5 using Tapatalk
Thanks, I ended up doing this http://forum.xda-developers.com/showpost.php?p=62288667&postcount=196
(flashing stock system, boot and recovery from my current version, letting OTA update install and re-rooting according to http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905)
I guess i could have flashed the new version just the same.
Hi,
I got my Moto G 2015 XT1541 running with Android 5.1.1 official rom and TWRP Osprey 3.0.0 R2. I just got the official message to upgrade to Marshmallow, but when I to upgrade TWRP comes with the following error: Updater process ended with ERROR: 7
I've placed a full log here: recovery.log
I also tried installing an other OTA file - (2GB Retail EU OTA): Download - thanks to @Osid - from here, but got the same error.
Also, the official update is version 24.41.33.en.EU, and the above file 23.41.47 and is already on my phone, according to "About Phone".
Anyway: Can someone please help me to get past this error and update to the official 24.41.33.en.EU? I've read about changing an updater-script file in the zip if you have one, but this is a block.map.
Thanks allot!
robert1010 said:
Hi,
I got my Moto G 2015 XT1541 running with Android 5.1.1 official rom and TWRP Osprey 3.0.0 R2. I just got the official message to upgrade to Marshmallow, but when I to upgrade TWRP comes with the following error: Updater process ended with ERROR: 7
I've placed a full log here: recovery.log
I also tried installing an other OTA file - (2GB Retail EU OTA): Download - thanks to @Osid - from here, but got the same error.
Also, the official update is version 24.41.33.en.EU, and the above file 23.41.47 and is already on my phone, according to "About Phone".
Anyway: Can someone please help me to get past this error and update to the official 24.41.33.en.EU? I've read about changing an updater-script file in the zip if you have one, but this is a block.map.
Thanks allot!
Click to expand...
Click to collapse
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
nobreak1970 said:
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
Click to expand...
Click to collapse
Both update methods, as described above, fail. Method 1: using the phone's system updater, method 2: using the official(?) OTA upgrade files provided on this site.
But it looks like the OTA file is of a version I already have. See attachment.
Sorry, I misread your reply. I am looking for the stock recovery now keep you posted.
nobreak1970 said:
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
Click to expand...
Click to collapse
Ok, I took the recovery.img from "XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7_subsidy-DEFAULT_CFC.xml", my version was 23.72-47. Hope that doesn't really matter. But is was the only 2GB European ROM I could find here.
So I used fastboot to flash that and tried the system update again. At the beginning it looked hopeful; It was showing the Installing System Update with the progress bar, but then briefly the error icon and rebooted without making any changes.
If I need to re-lock and/or un-root to fix this, can it be don without wiping everything?
Thanks again!
robert1010 said:
Ok, I took the recovery.img from "XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7_subsidy-DEFAULT_CFC.xml", my version was 23.72-47. Hope that doesn't really matter. But is was the only 2GB European ROM I could find here.
So I used fastboot to flash that and tried the system update again. At the beginning it looked hopeful; It was showing the Installing System Update with the progress bar, but then briefly the error icon and rebooted without making any changes.
If I need to re-lock and/or un-root to fix this, can it be don without wiping everything?
Thanks again!
Click to expand...
Click to collapse
Anyone who can help me with this please?