Related
Went through the whole process to get an unlocked phone working on verizon - unlock bootloader, TWRP, s-off, etc.
Went back and flashed stock 1.21 recovery since that's what my phone was on, did a factory reset after getting this error the first time.
Still getting the error -
Code:
Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance.
Before flashing the stock recovery I did try to restore the recovery/system image from TWRP's system backup, not sure if that has anything to do with it.
noahjk said:
Went through the whole process to get an unlocked phone working on verizon - unlock bootloader, TWRP, s-off, etc.
Went back and flashed stock 1.21 recovery since that's what my phone was on, did a factory reset after getting this error the first time.
Still getting the error -
Code:
Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance.
Before flashing the stock recovery I did try to restore the recovery/system image from TWRP's system backup, not sure if that has anything to do with it.
Click to expand...
Click to collapse
Try flashing this zip in download mode (fastboot flash zip pathtozip.zip)
https://drive.google.com/file/d/0B8OH6sFjVE1ld1ptNTFEaEc3Rms/view?usp=docslist_api
Reboot and try ota again.
This will flash the unlocked radio though, so you'll need to reperform the steps from the Verizon thread after you do this. please report back if it works.
jollywhitefoot said:
Try flashing this zip in download mode (fastboot flash zip pathtozip.zip)
https://drive.google.com/file/d/0B8OH6sFjVE1ld1ptNTFEaEc3Rms/view?usp=docslist_api
Reboot and try ota again.
This will flash the unlocked radio though, so you'll need to reperform the steps from the Verizon thread after you do this. please report back if it works.
Click to expand...
Click to collapse
Worked great. Thanks!
For anyone else following this thread, if you're flashing the zip and see this:
Code:
remote: 90 hboot pre-update! please flush image again immediately
Just flash again right away and it'll work fine.
noahjk said:
Worked great. Thanks!
For anyone else following this thread, if you're flashing the zip and see this:
Code:
remote: 90 hboot pre-update! please flush image again immediately
Just flash again right away and it'll work fine.
Click to expand...
Click to collapse
I'm glad that worked for you. I went ahead and wrote a guide in case anyone else has trouble. It includes the message about reflashing.
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
international version
jollywhitefoot said:
Try flashing this zip in download mode (fastboot flash zip pathtozip.zip)
Reboot and try ota again.
This will flash the unlocked radio though, so you'll need to reperform the steps from the Verizon thread after you do this. please report back if it works.
Click to expand...
Click to collapse
Hey there, Ive come across your post after experiencing the same problem on a HTC10 international version. Can I ask if the file that you've provided work on the international version? Also do I have to restore my twrp backup as well? Thanks a lot!
Hi there, same problem: "Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance."
Htc 10 unlocked, v. 1.90.401.5
I followed post #2 without success.
Some idea please?
Help, please! ?
I gave up with the same problem and switched to a custom rom - Leedroid.
Thank you Simplici. So no chance with official stock to solve this problem?
last_nooby said:
Thank you Simplici. So no chance with official stock to solve this problem?
Click to expand...
Click to collapse
There is. You could flash an appropriate RUU if available. Although it'll wipe all you're data, it should restore the phone to a status, making an OTA update possible again. Those errors could be caused by a once r/w mounted system partition, or a tripped dm-verity flag. You'll find more on this issues and help of how to properly restore over at the Guides section of this forum.
Edit: here's the link regarding the corrupt system partition error: http://forum.xda-developers.com/htc...o-ota-receive-corrupt-message-t3378187/page43
Sent from my htc_pmeuhl using XDA Labs
jollywhitefoot said:
Try flashing this zip in download mode (fastboot flash zip pathtozip.zip)
https://drive.google.com/file/d/0B8OH6sFjVE1ld1ptNTFEaEc3Rms/view?usp=docslist_api
Reboot and try ota again.
This will flash the unlocked radio though, so you'll need to reperform the steps from the Verizon thread after you do this. please report back if it works.
Click to expand...
Click to collapse
can some one reload the file again? there's no file in google drive
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
So I restored my phone to stock, by flashing the whole firmware with RSD Lite. When I try to update, the installation starts but after some time I get an error.
Was anyone able to restore to stock and flash the OTAs?
turkobr said:
So I restored my phone to stock, by flashing the whole firmware with RSD Lite. When I try to update, the installation starts but after some time I get an error.
Was anyone able to restore to stock and flash the OTAs?
Click to expand...
Click to collapse
It's probably preventing a mismatched bootloader from flashing, which would hard bricking your device.
RSD lite is easy to use but can ultimately cause issues later on, you're flashing the entire firmware package , bootloaders and all which isn't always the best thing to do under certain circumstances.
It's always better to just flash the system images such as the 10 sparsechunks, OEM image, recovery and boot image only.
These can be easily flashed through fastboot.
IMO leave it alone , otherwise you may end up hard bricking your device
Sent from my XT1635-02 using XDA-Developers Legacy app
Good news! I flashed the latest firmware available and the OTA worked. I'm now on the december security patch.
hi can you share step by step how to flash using rsdlite?
nabilhashriq said:
hi can you share step by step how to flash using rsdlite?
Click to expand...
Click to collapse
First you have to install fastboot. I did this a long time ago, but I believe I got it from here: https://forum.xda-developers.com/showthread.php?t=2588979
Then install RSD Lite: http://rsdlite.com/rsd-lite-download/ (the link for 6.1.6 is broken, so just get the 6.1.5)
Then download the right firmware for your phone from here https://mirrors.lolinet.com/ or here http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100&page=1
Be really careful, a lot of people lost theis IMEI when flashing the firmware and be sure you're using the right one for you model and region.
Now just boot you phone on Bootloader mode (hold the power and volume down buttons together ultil the bootloader screen shows up). Select flashfile.xml and hit start.
As flashallthetime said, this could cause you trouble, as it did at first for me. The safest thing you should do is just flash the system images such as the 10 sparsechunks, OEM image, recovery and boot image that comes with the firmware.
I'm not responsible for any damage to your phone, do it at your own risk.
After updating my bootloader to NE2 using odin, by phone just keeps and booting up to the Samsung Galaxy logo and restarting. The logo appears for a second or so before restarting. I can access download mode, but receive the following:
ODIN MODE
PRODUCT NAME: GT-N7100
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
AP SWREV: A2
RPMB: INVALID RPMB DATA
( the last three lines have appeared, and were not there previously before updating the bootloader). The phone was working fine with stock 4.4.2, before installing the bootloader. I cannot access recovery mode, and have flashed TWRP with odin (reported success in odin), but cannot access the TWRP recovery menu on my phone. I have tried to flash stock 4.4.2 again with odin, I do not receive any errors and receive a success 1 in odin where a blue bar is visible (when flashing) on the screen of my phone. But after the phone restarts, i experience the same bootloop problem. Help would be greatly appreciated.
Open Odin, uncheck everything, flash latest stock ROM from sammobile (https://www.sammobile.com/firmwares/database/GT-N7100/), you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
audit13 said:
Open Odin, uncheck everything, flash latest stock ROM from sammobile, you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
Click to expand...
Click to collapse
Before proceeding, I'd like to ask:
1 - I have a motherboard that I've obtained from China. Would it be ok for me to flash as you've recommended with this motherboard, taking into account the "RPMB: INVALID RPMB DATA" message that appears in download mode ?
2 - Can I install any of the latest firmwares available on sammobile for my galaxy note 2 ?
3 - Would I be able to install TWRP and custom roms after ?
Thanks
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
audit13 said:
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
Click to expand...
Click to collapse
After flashing the N7100XXUFOC2 firmware with all boxes unchecked in odin, i still receive a bootloop, and the phone is not entering recovery :-/. The messages that appear in download mode have remained unchanged.
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
audit13 said:
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
Click to expand...
Click to collapse
Yes it flashes with no errors. When turning the phone on, the samsung galaxy note 2 logo appears for just under a second, and the phone restarts and repeats until i remove the battery. Nothing happens when I try to enter the recovery menu, the same behaviour is observed (phone restarting constantly after showing SGnote2 logo). I have been reading around, and i suspect (just a guess, not sure) that the "RPMB: INVALID RPMB DATA" message that I observe in download mode may have something to do with this.
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
audit13 said:
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
Click to expand...
Click to collapse
Is there anything else that i could try ? I used an app to check the bootloader version when it was working on stock 4.4.2, and it stated that it was at LJ7. After updating the bootloader to NE1, I've experienced this problem. Would it be possible to revert back to the previous bootloader ( and would this help ?). I've flashed custom roms with no problems, beforehand using TWRP.
How did you update the bootloader? Did you update the bootlaoder without updating anything else?
audit13 said:
How did you update the bootloader?
Click to expand...
Click to collapse
I downloaded the NE1 bootloader from a user here who has a list of bootloaders on his profile (user: Androidwizzard), and flashed it using Odin v3.09 with the default boxes checked. I did not update anything else ( just clicked the "BL" field and selected the bootloader, then flashed).
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
audit13 said:
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
Click to expand...
Click to collapse
Yeah. Would it be possible to revert the bootloader back to what it was previously ? Also, is there anything else that you may suggest that i could do ? I'm still not sure what is causing this issue exactly. It seems strange that I can flash all files with no errors using Odin. By flashing a later firmware, is the bootloader automatically updated ? ( if yes, then I'm not sure why the app stated that my bootloader version was at LJ7, given that I've flashed stock 4.4.2 with odin beforehand.)
Do you have a link for the bootloader?
Did the phone work properly before flashing the new NE1 bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
audit13 said:
Do you have a link for the bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
Click to expand...
Click to collapse
I have not tried flashing the latest rom ( I could try, if that may help). I can not provide the direct link to the bootloader, since i will have to produce 10 posts ( new user here lol ). You can find the bootloader by searching google: [bootloader/modem/rom][tw kitkat][4.4.2][pf1 + pc1 + oe1 + od4 + nl1 +], then going to Androidwizzard second post.
The phone was working great before flashing the NE1 bootloader. As mentioned previously, I've flashed the N7100XXUFOC2 firmware resulting in no change.
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
audit13 said:
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
Click to expand...
Click to collapse
I will give it a go right now. Would you be able to guide me to where I could obtain the appropriate pit file for the phone ? The firmwares with PF1 have (orange) carrier. Would this affect things ?
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
audit13 said:
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
Click to expand...
Click to collapse
16 GB model. Alright, I'll try to flash the latest rom.
Whats the process to flashing a custom rom on the pixel devices? i read something about having to flash stock first?
xSpartacusx said:
Whats the process to flashing a custom rom on the pixel devices? i read something about having to flash stock first?
Click to expand...
Click to collapse
Your bootloader, radio and vendor should match whatever ROM you want to flash.
Basically you should flash and boot March stock first, set up and set pin
Download rom, twrp installer zip
Remove screen lock pin
Fastboot boot (twrp.img)
Factory reset
Flash rom + twrp installer
Reboot system
If you want to flash a 9 based ROM like carbonrom you'll have to format userdata and flash and boot August factory image then repeat the steps above
Either way you should learn the fastboot commands and do things manually, it comes in handy updating both slots if needed.
oh yea i got it figured out! now, if i go back to stock from a custom rom, using the stock March image, will i still get OTA updates or will i need to flash through the OTA images that are provided?
xSpartacusx said:
oh yea i got it figured out! now, if i go back to stock from a custom rom, using the stock March image, will i still get OTA updates or will i need to flash through the OTA images that are provided?
Click to expand...
Click to collapse
You'll need to relock your bootloader, just make sure you're full stock on both slots or you will brick your phone. I personally don't think it's worth the risk and just update through twrp or fastboot