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
Related
I have the T-Mobile HTC 10. I never converted it to US unlocked or anything. When I got it, I unlocked the bootloader, installed custom recovery (TWRP) rooted it, and slapped on a custom ROM (LeeDroid). I have a nandroid backup of my stock rom. I'm still S-ON.
Now I find out that T-Mobile has FINALLY pushed the firmware update. How I can easily upgrade the firmware on my phone?
What I tried was to backup my leedroid, restore my stock rom, and then take the update. But I got the corrupt file error.
No idea what to do now. I saw someone had a file of the OTA update (downloaded it), but I don't know what to do with that, or even if I can as I have S-ON.
How can I easily get to rocking the new firmware on my T-Mobile HTC 10?
Thanks!!
pappy97 said:
I have the T-Mobile HTC 10. I never converted it to US unlocked or anything. When I got it, I unlocked the bootloader, installed custom recovery (TWRP) rooted it, and slapped on a custom ROM (LeeDroid). I have a nandroid backup of my stock rom. I'm still S-ON.
Now I find out that T-Mobile has FINALLY pushed the firmware update. How I can easily upgrade the firmware on my phone?
What I tried was to backup my leedroid, restore my stock rom, and then take the update. But I got the corrupt file error.
No idea what to do now. I saw someone had a file of the OTA update (downloaded it), but I don't know what to do with that, or even if I can as I have S-ON.
How can I easily get to rocking the new firmware on my T-Mobile HTC 10?
Thanks!!
Click to expand...
Click to collapse
I flashed the untouched system image and boot img then I fastboot flash stock 1.21.206.4_rec.img I used this because I couldn't get a T-Mobile stock recovery
Then rebooted to recovery and adb sideloaded the ota zip
That's it job done
twinnfamous said:
I flashed the untouched system image and boot img then I fastboot flash stock 1.21.206.4_rec.img I used this because I couldn't get a T-Mobile stock recovery
Then rebooted to recovery and adb sideloaded the ota zip
That's it job done
Click to expand...
Click to collapse
Is that the command you actually ran?
"fastboot flash stock 1.21.206.4_rec.img" ?
Thanks
pappy97 said:
Is that the command you actually ran?
"fastboot flash stock 1.21.206.4_rec.img" ?
Thanks
Click to expand...
Click to collapse
Nope I changed the name to 1.21.img
So my command was.
fastboot flash recovery 1.21.img
I had downloaded a few I was gonna try them all.
twinnfamous said:
Nope I changed the name to 1.21.img
So my command was.
fastboot flash recovery 1.21.img
I had downloaded a few I was gonna try them all.
Click to expand...
Click to collapse
Thanks, very helpful!
Everything worked great until actually applying the OTA update in recovery. It wouldn't do it, saying the update was for PMEWL devices, and mine is PMEUHL. I definitely tried to use your OTA update file that you posted in another thread. Any idea what this is all about? (Seems WL is a reference to another phone, maybe US unlocked. So perhaps this is the OTA for US unlocked, not T-Mobile US? Or it's really for TMO DE?).
pappy97 said:
Everything worked great until actually applying the OTA update in recovery. It wouldn't do it, saying the update was for PMEWL devices, and mine is PMEUHL. I definitely tried to use your OTA update file that you posted in another thread. Any idea what this is all about? (Seems WL is a reference to another phone, maybe US unlocked. So perhaps this is the OTA for US unlocked, not T-Mobile US? Or it's really for TMO DE?).
Click to expand...
Click to collapse
I'm getting the same error unfortunately. I have USA T-mobile HTC 10. Does anyone have a solution for this or are we USA T-mobile folks doomed to wait for an RUU?
pappy97 said:
Everything worked great until actually applying the OTA update in recovery. It wouldn't do it, saying the update was for PMEWL devices, and mine is PMEUHL. I definitely tried to use your OTA update file that you posted in another thread. Any idea what this is all about? (Seems WL is a reference to another phone, maybe US unlocked. So perhaps this is the OTA for US unlocked, not T-Mobile US? Or it's really for TMO DE?).
Click to expand...
Click to collapse
So you don't have a T-Mobile is phone.?
twinnfamous said:
So you don't have a T-Mobile is phone.?
Click to expand...
Click to collapse
what's the exact stock image that you flashed?
twinnfamous said:
So you don't have a T-Mobile is phone.?
Click to expand...
Click to collapse
This is what my info reads.
I have 2 both from T-Mobile stores in US
max05xiii said:
what's the exact stock image that you flashed?
Click to expand...
Click to collapse
Recovery 1.21.206.4
System.img from 1.21.531.1
twinnfamous said:
Recovery 1.21.206.4
System.img from 1.21.531.1
Click to expand...
Click to collapse
Well, you're S-OFF and I'm S-ON. I don't know if that makes a difference or not. Thanks for your help by the way
max05xiii said:
I'm getting the same error unfortunately. I have USA T-mobile HTC 10. Does anyone have a solution for this or are we USA T-mobile folks doomed to wait for an RUU?
Click to expand...
Click to collapse
I have a untouched system.img and boot.img twrp backup from the new 1.81.531.1 update. I just need to upload it and share the link.
---------- Post added at 07:55 AM ---------- Previous post was at 07:50 AM ----------
max05xiii said:
Well, you're S-OFF and I'm S-ON. I don't know if that makes a difference or not. Thanks for your help by the way
Click to expand...
Click to collapse
Yea I was gonna ask.
It might make a difference being s-on but wondering if u tried to update firmware from the signed firmware?
I was running into issues flashing the Ota but eventually managed to to get it to work. Here's exactly what I did.
Place the Ota file on the root of an SD card.
On your PC, Pull the recovery image from the firmware zip within the t-mobile OTA file and place in the ADB folder.
In twrp, go to Mount, and mount system as read only.
Then, select Restore and go to your untouched system backup. The only two options that should be checked are System IMAGE and Boot.
Reboot to Download
Flash the stock recovery pulled from the OTA.
Reboot to Bootloader, then boot to Recovery
Select install from SD card and select the Ota file.
For me, it did seem to hang at "patching system" or something like that, but be patient. It did complete loading.
Hope this works for you
Sent from my HTC 10 using XDA-Developers mobile app
bsims85 said:
I was running into issues flashing the Ota but eventually managed to to get it to work. Here's exactly what I did.
Place the Ota file on the root of an SD card.
On your PC, Pull the recovery image from the firmware zip within the t-mobile OTA file and place in the ADB folder.
In twrp, go to Mount, and mount system as read only.
Then, select Restore and go to your untouched system backup. The only two options that should be checked are System IMAGE and Boot.
Reboot to Download
Flash the stock recovery pulled from the OTA.
Reboot to Bootloader, then boot to Recovery
Select install from SD card and select the Ota file.
For me, it did seem to hang at "patching system" or something like that, but be patient. It did complete loading.
Hope this works for you
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
Wish I saw this post before I just flashed the zip and completely lost root.
Sent from my HTC 10 using XDA-Developers mobile app
Hi guys. I need ur help on this one .
I've had the m8 since new and first things I did was unlock bootloader to install custom roms. The phone was never s-off !
So, I've been having connectivity problems and I have to bring it in to have it looked at. But my current provider(Eastlink) won't support rooted phones or phones with custom roms. So since last night I decided to put it right back to stock and update it. This is where I ran into problems and the problems I've found are most likely what is causing the initial connectivity problems.
So I restored my original nandroid backup, flashed original recovery and went to do the ota update which will update the phone to MM. But when it flashes the OTA it always comes up with a (status 7) installation aborted with this message ... (see pic) something about was expecting build fingerprint of htc/Rogers_wwe but mine has htc_europe.
Also, there is no OS version in bootloader(see pic).
Any help would greatly appreciated.
Thanks
You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).
redpoint73 said:
You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).
Click to expand...
Click to collapse
Thanks for the reply. I was thinking that it could be a wrong stock recovery but the stock rom is a nandroid backup I had taken when I bought the phone.
THe version of twrp I've been using is twrp-3.0.2-0-m8.img
rogerrulez said:
THe version of twrp I've been using is twrp-3.0.2-0-m8.img
Click to expand...
Click to collapse
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Oh, ok thanks for clearing that up. Makes sense.
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
http://forum.xda-developers.com/showthread.php?t=2694297
redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Also I wanted to mention was that I'm pretty sure I had the stock recovery which was on my computer with the htc m8 stuff since Jan, 2015. But that one doesn't seem to be working. But I could be wrong on that. It could be from a different phone now that I look at that folder more closely.
rogerrulez said:
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
Click to expand...
Click to collapse
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?
redpoint73 said:
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?
Click to expand...
Click to collapse
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...
rogerrulez said:
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...
Click to expand...
Click to collapse
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.
rogerrulez said:
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.
Click to expand...
Click to collapse
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2
ckpv5 said:
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2
Click to expand...
Click to collapse
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...
rogerrulez said:
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...
Click to expand...
Click to collapse
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?
rogerrulez said:
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?
Click to expand...
Click to collapse
Check the backup thread linked in my signature. Everything you need are there.
ckpv5 said:
Check the backup thread linked in my signature. Everything you need are there.
Click to expand...
Click to collapse
Hi ckpv5,
I installed one of ur stock recoveries 4.20.631.3_recovery from ur collection, and now I am getting this error while doing the OTA.(see attached pic).
Any ideas ?
Update ...
I decided to go and flash the firmware.zip file from within the OTA file. It flashed ok and I now have an OS version in the bootloder.
But now it won't go any further then going to the bootloader, which I have to force into. Goes to black screen.
I then tried to flash the OTA file the same way "fastboot flash zip RUU.zip(renamed) and it fails to flash. So now I am soft bricked.
Never been in this situation before and need some advice please !
Solved!
After flashing the firmware from the OTA zip file I forgot that everything would be wiped. So here's what I did ...
1. Unlock bootloader.
2. Flash recovery.
3. Restore nandroid backup.
4. Boot up then shut down and flash proper version of stock recovery.
5. Relock bootloader.
6. Install OTA !
Thanks guys for all ur help
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)
Solved my problem by flashing the FULL firmware and not only the boot.img !
Could a mod delete the thread please ? Thanks !
Pouni said:
Solved my problem by flashing the FULL firmware and not only the boot.img !
Could a mod delete the thread please ? Thanks !
Click to expand...
Click to collapse
How did you accomplish this? I can't get RSD Lite to detect my phone (although fastboot devices shows it listed) and I can't flash the full firmware via adb because I keep getting "Image not signed or corrupt". I'm really confused.
Pouni said:
Solved my problem by flashing the FULL firmware and not only the boot.img !
Could a mod delete the thread please ? Thanks !
Click to expand...
Click to collapse
Please don't ask mods to delete threads because of successful outcomes - post your solution instead. Leave the threads up as they are a useful resource for others (at least those who search before posting! )
Thanks
Sent from my SAMSUNG-SM-G920A using Tapatalk
joesee said:
How did you accomplish this? I can't get RSD Lite to detect my phone (although fastboot devices shows it listed) and I can't flash the full firmware via adb because I keep getting "Image not signed or corrupt". I'm really confused.
Click to expand...
Click to collapse
I kept getting the "Image not signed or corrupt" whenever I had to flash the boot.img but I ignored the error once to try and see if it had any positive outcome, and it worked fine !
Can't flash stock ROM, can you do a detail installation log?
Pouni said:
I kept getting the "Image not signed or corrupt" whenever I had to flash the boot.img but I ignored the error once to try and see if it had any positive outcome, and it worked fine !
Click to expand...
Click to collapse
Is ur bootloader unlocked or not??
If not try unlock ur bootloader than try it ll work
From what I can tell you will always get the "Image not signed or corrupt" error, but it works anyways. Idk why but it doesnt matter as long as it works . Motorola(Lenovo) has the instructions to flash stock firmware on your device, just download the firmware for your device and follow those instructions.
jon7701 said:
From what I can tell you will always get the "Image not signed or corrupt" error, but it works anyways. Idk why but it doesnt matter as long as it works . Motorola(Lenovo) has the instructions to flash stock firmware on your device, just download the firmware for your device and follow those instructions.
Click to expand...
Click to collapse
Jon, can you help me? already tried to flash stock rom in fastboot but it doesn't flash.... i'm tired of this
Vitxlss said:
Jon, can you help me? already tried to flash stock rom in fastboot but it doesn't flash.... i'm tired of this
Click to expand...
Click to collapse
Did you only flash the stock rom or did you try to flash everything? If you didnt try to flash everything I would try that and make sure you have the correct stock firmware for your device before you do that. Theres not really much else you can do other than try flashing in twrp, but idk if twrp supports space chunks, but it does support images. If it really comes down to it, you can force flash the system partition in twrp, but you would need the whole system image and not space chunks.
My phone is stuck on bootscreen. My bootloader is unlocked and I have root. I was trying to uninstall the preloaded Amazon apps and one ''Root Uninstaller' app rebooted my phone and ive been stuck on the bootscreen. The phone just tries rebooting over and over. I formatted data in stock recovery, but the issue still persists. Help please
Ebizza said:
My phone is stuck on bootscreen. My bootloader is unlocked and I have root. I was trying to uninstall the preloaded Amazon apps and one ''Root Uninstaller' app rebooted my phone and ive been stuck on the bootscreen. The phone just tries rebooting over and over. I formatted data in stock recovery, but the issue still persists. Help please
Click to expand...
Click to collapse
Restoring STock boot image fixed this.
Ebizza said:
Restoring STock boot image fixed this.
Click to expand...
Click to collapse
How did you restore stock? I flashed kernel but was on custom rom. Phone got stuck on bootloop. I can't enter recovery or fastboot. LGUP fails because i can't cross flash my Sprint to any other KDZ. Any suggestions on what i can try? thanks
Eljay227 said:
How did you restore stock? I flashed kernel but was on custom rom. Phone got stuck on bootloop. I can't enter recovery or fastboot. LGUP fails because i can't cross flash my Sprint to any other KDZ. Any suggestions on what i can try? thanks
Click to expand...
Click to collapse
Did you root your phone? If you did, you can use Qfil to restore your stock boot img (if you made a backup). If you didn't, you'd have to get someone to send you their boot image. I would have sent mine, but I cross flashed from Sprint to Open US. I doubt mine would work for you.
Why can't you cross flash?
Ebizza said:
Did you root your phone? If you did, you can use Qfil to restore your stock boot img (if you made a backup). If you didn't, you'd have to get someone to send you their boot image. I would have sent mine, but I cross flashed from Sprint to Open US. I doubt mine would work for you.
Why can't you cross flash?
Click to expand...
Click to collapse
Can you please guide me on how to cross flash? Because i am getting the error 0x5319, Not allow to change the device.(SPR_US->OPEN_CA). I am using LG UP CMD method. using LG UP and UPPERCUT, it crashes at 4%. Maybe i am missing something? how did you cross flash?
Eljay227 said:
Can you please guide me on how to cross flash? Because i am getting the error 0x5319, Not allow to change the device.(SPR_US->OPEN_CA). I am using LG UP CMD method. using LG UP and UPPERCUT, it crashes at 4%. Maybe i am missing something? how did you cross flash?
Click to expand...
Click to collapse
There's a post on the site. Did you follow all the steps?
Eljay227 said:
Can you please guide me on how to cross flash? Because i am getting the error 0x5319, Not allow to change the device.(SPR_US->OPEN_CA). I am using LG UP CMD method. using LG UP and UPPERCUT, it crashes at 4%. Maybe i am missing something? how did you cross flash?
Click to expand...
Click to collapse
[Tutorial] Crossflash, Bypass OPID Mismatched Error
Hi there ;) Thanks to all other guys here who have made helpful development to tame this beautiful =) To crossflash models other than LG G8 please read post 3. Before asking any question please read the troubleshooting section at the bottom of...
forum.xda-developers.com
Here.
Ebizza said:
There's a post on the site. Did you follow all the steps?
Click to expand...
Click to collapse
To cross flash? Yes i found one, but it's via TWRP. Right now all i get is logo, "your device software can not be checked for corruption.." and screen off. I can only enter Download mode. If i can at least restore recovery i can cross flash or install custom.
Eljay227 said:
To cross flash? Yes i found one, but it's via TWRP. Right now all i get is logo, "your device software can not be checked for corruption.." and screen off. I can only enter Download mode. If i can at least restore recovery i can cross flash or install custom.
Click to expand...
Click to collapse
No. You don't need TWRP. Just read that post and follow the steps
Ebizza said:
No. You don't need TWRP. Just read that post and follow the steps
Click to expand...
Click to collapse
thanks, i crossed flashed to open. but now i cant make calls. sim service blocked. maybe i have to flash a different modem file? did you come across such errors when flashing?
Eljay227 said:
thanks, i crossed flashed to open. but now i cant make calls. sim service blocked. maybe i have to flash a different modem file? did you come across such errors when flashing?
Click to expand...
Click to collapse
No I didn't. Did you clear stock modem file from QFIL?
You should clear modem and some other files stated in that post. Then you select all partitions in LGUP except one file also stated in the post. (I can't remember the name of the file)
Ebizza said:
No I didn't. Did you clear stock modem file from QFIL?
You should clear modem and some other files stated in that post. Then you select all partitions in LGUP except one file also stated in the post. (I can't remember the name of the file)
Click to expand...
Click to collapse
yea i cleared the files mentioned in that post. and also cleared modem. Any kdz i flash, the first message i get is: this phone is permanently locked. it can not be unlocked. before this i tried some guy's backup from TWRP of his lg g8 sprint. i got lots of errors popping up when it booted. i think that's where my sim whatever got messed up.
From my research, i think a file called fsg has something to do with sim working. Also my IMEI is 0. any suggestions would be highly appreciated.
Eljay227 said:
yea i cleared the files mentioned in that post. and also cleared modem. Any kdz i flash, the first message i get is: this phone is permanently locked. it can not be unlocked. before this i tried some guy's backup from TWRP of his lg g8 sprint. i got lots of errors popping up when it booted. i think that's where my sim whatever got messed up.
From my research, i think a file called fsg has something to do with sim working. Also my IMEI is 0. any suggestions would be highly appreciated.
Click to expand...
Click to collapse
Try to restore stock modem and stock fsg. Did you backup those partitions?
Ebizza said:
Try to restore stock modem and stock fsg. Did you backup those partitions?
Click to expand...
Click to collapse
No didn’t back up. If you have can you please send me? I’m out of ideas at this point. Thanks
Eljay227 said:
No didn’t back up. If you have can you please send me? I’m out of ideas at this point. Tha
Click to expand...
Click to collapse
You should have made a backup na.
Text me on Telegram +2347018132403. I'll send you my files.