Well I was looking for an Honami Rom days ago,
and I flashed THIS: http://forum.xda-developers.com/showpost.php?p=47112717&postcount=74
Then when I tried installing CM11 or AOKP it fails, only STOCK based ROMS work
I reflashed the firmware with flashtool and repaired with PC Companion
but when I go to CWM I still get status 7 error when flashing CM11
Can anyone help?
I'm on Xperia V with unlocked bootloader
Allen Hu said:
Well I was looking for an Honami Rom days ago,
and I flashed THIS: http://forum.xda-developers.com/showpost.php?p=47112717&postcount=74
Then when I tried installing CM11 or AOKP it fails, only STOCK based ROMS work
I reflashed the firmware with flashtool and repaired with PC Companion
but when I go to CWM I still get status 7 error when flashing CM11
Can anyone help?
I'm on Xperia V with unlocked bootloader
Click to expand...
Click to collapse
Umm, that's odd..... Try to install TWRP and flash CM11 or whatever with it
St.Jimmy90 said:
Umm, that's odd..... Try to install TWRP and flash CM11 or whatever with it
Click to expand...
Click to collapse
TWRP not working too :silly::crying:
Allen Hu said:
TWRP not working too :silly::crying:
Click to expand...
Click to collapse
Same problem. Have you find any solution?
zaize said:
Same problem. Have you find any solution?
Click to expand...
Click to collapse
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Allen Hu said:
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Click to expand...
Click to collapse
Man thats crazy - but it worked! Thank you :victory:
zaize said:
Man thats crazy - but it worked! Thank you :victory:
Click to expand...
Click to collapse
Allen Hu said:
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Click to expand...
Click to collapse
St.Jimmy90 said:
Umm, that's odd..... Try to install TWRP and flash CM11 or whatever with it
Click to expand...
Click to collapse
First flash kernel of ROM that you're going to install via fastboot, then reboot to recovery and flash ROM :laugh:
Allen Hu said:
Well I was looking for an Honami Rom days ago,
and I flashed THIS: http://forum.xda-developers.com/showpost.php?p=47112717&postcount=74
Then when I tried installing CM11 or AOKP it fails, only STOCK based ROMS work
I reflashed the firmware with flashtool and repaired with PC Companion
but when I go to CWM I still get status 7 error when flashing CM11
Can anyone help?
I'm on Xperia V with unlocked bootloader
Click to expand...
Click to collapse
Does the error say only "status 7", or does it say anything else also, such as "this device is xxxx, etc."?
Antiga Prime said:
Does the error say only "status 7", or does it say anything else also, such as "this device is xxxx, etc."?
Click to expand...
Click to collapse
The problem is already solved here...
it showed the " this device is "mint"" or something like that
Allen Hu said:
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Click to expand...
Click to collapse
St.Jimmy90 said:
Umm, that's odd..... Try to install TWRP and flash CM11 or whatever with it
Click to expand...
Click to collapse
Aria.A97 said:
First flash kernel of ROM that you're going to install via fastboot, then reboot to recovery and flash ROM :laugh:
Click to expand...
Click to collapse
Allen Hu said:
The problem is already solved here...
it showed the " this device is "mint"" or something like that
Click to expand...
Click to collapse
Ok, I know the problem is "solved", but it's not really solved if you don't know what is going on; this problem is not odd. In order for you to flash a file, there is a file in the zip named "updater-script" in the "/Meta-inf/com/google/android/" folder which has the commands that are run when you flash it, be it with CWM or TWRP. The first two lines of that file read the device identification from the "build.prop" file that comes with the ROM you currently have installed, so, if that ROM is identifying your device incorrectly, or using strings that aren't exactly like the ones contained in the "updater-script", it won't work.
Now, flashing a different ROM before flashing the ROM you're going to use without wiping /system and /data is a dumb thing to do, IMO, because the "updater-script" files don't always erase everything and leave behind remnants of the previous ROM, which is why tons of people complain about little bugs and problems with their ROMs, when other people who do in fact flash properly don't have these problems and therefore can't help them, and then these people blame it on the ROM, saying it has bugs and other stuff when in fact they don't know what they are doing.
All this to say, instead of having to flash an entire different ROM as per what @Allen Hu suggested, what I do is extract the "updater-script" file and delete the first two lines that say:
assert(getprop("ro.product.device") == "LT29i" || getprop("ro.build.product") == "LT29i" ||
getprop("ro.product.device") == "hayabusa" || getprop("ro.build.product") == "hayabusa" || abort("This package is for \"LT29i,hayabusa\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Click to expand...
Click to collapse
In my case, the ROM is made for an LT29I, not an LT25, but you get the point.
After deleting that line (with Notepad++, not Windows notepad), just add the script file back, and you can flash it on any device you like, and that would be a proper solution.
Many thanks
Antiga Prime said:
Ok, I know the problem is "solved", but it's not really solved if you don't know what is going on; this problem is not odd. In order for you to flash a file, there is a file in the zip named "updater-script" in the "/Meta-inf/com/google/android/" folder which has the commands that are run when you flash it, be it with CWM or TWRP. The first two lines of that file read the device identification from the "build.prop" file that comes with the ROM you currently have installed, so, if that ROM is identifying your device incorrectly, or using strings that aren't exactly like the ones contained in the "updater-script", it won't work.
Now, flashing a different ROM before flashing the ROM you're going to use without wiping /system and /data is a dumb thing to do, IMO, because the "updater-script" files don't always erase everything and leave behind remnants of the previous ROM, which is why tons of people complain about little bugs and problems with their ROMs, when other people who do in fact flash properly don't have these problems and therefore can't help them, and then these people blame it on the ROM, saying it has bugs and other stuff when in fact they don't know what they are doing.
All this to say, instead of having to flash an entire different ROM as per what @Allen Hu suggested, what I do is extract the "updater-script" file and delete the first two lines that say:
In my case, the ROM is made for an LT29I, not an LT25, but you get the point.
After deleting that line (with Notepad++, not Windows notepad), just add the script file back, and you can flash it on any device you like, and that would be a proper solution.
Click to expand...
Click to collapse
Thank you for solving this properly, it worked perfectly for me!
worked for me
Antiga Prime said:
Ok, I know the problem is "solved", but it's not really solved if you don't know what is going on; this problem is not odd. In order for you to flash a file, there is a file in the zip named "updater-script" in the "/Meta-inf/com/google/android/" folder which has the commands that are run when you flash it, be it with CWM or TWRP. The first two lines of that file read the device identification from the "build.prop" file that comes with the ROM you currently have installed, so, if that ROM is identifying your device incorrectly, or using strings that aren't exactly like the ones contained in the "updater-script", it won't work.
Now, flashing a different ROM before flashing the ROM you're going to use without wiping /system and /data is a dumb thing to do, IMO, because the "updater-script" files don't always erase everything and leave behind remnants of the previous ROM, which is why tons of people complain about little bugs and problems with their ROMs, when other people who do in fact flash properly don't have these problems and therefore can't help them, and then these people blame it on the ROM, saying it has bugs and other stuff when in fact they don't know what they are doing.
All this to say, instead of having to flash an entire different ROM as per what @Allen Hu suggested, what I do is extract the "updater-script" file and delete the first two lines that say:
In my case, the ROM is made for an LT29I, not an LT25, but you get the point.
After deleting that line (with Notepad++, not Windows notepad), just add the script file back, and you can flash it on any device you like, and that would be a proper solution.
Click to expand...
Click to collapse
works fine
Allen Hu said:
Flash AOKP mr2 every time when you switch Roms, IDK why but you should be able to flash other roms after doing this
Click to expand...
Click to collapse
Hi, i have the same problem, but i don't know were i can find the AOKP, can you please help with this?
Thank you
celupapas said:
Hi, i have the same problem, but i don't know were i can find the AOKP, can you please help with this?
Thank you
Click to expand...
Click to collapse
http://xfer.aokp.co/get.php?p=AOKP/tsubasa/aokp_tsubasa_jb-mr2_milestone-1.zip
Here you go
Well if this doesn't work you can try deleting some lines in updater-script as the method provided above?
Allen Hu said:
Here you go
Well if this doesn't work you can try deleting some lines in updater-script as the method provided above?
Click to expand...
Click to collapse
Thanks a lot, I flash AOKP and this work, everything is normal again.
Never happen but I read that the problem was the rom and some problems with the recovery.
Hello,
I have tried to install CM12 using CWM but I got this error.
After deleting the first line on updater-script file I got another error:
Creating symlinks....
symlink: some symlinks filederror in /storage/...
(Status 7)
installation aborded.
I have tried to delete also the second line and the third and the 4th but every time the same error.
Do you have any idea of what is happening?
Can you please provide some basic instructions on how to install this custom ROM with Flashtool?
Thank you
nicu.s said:
Hello,
I have tried to install CM12 using CWM but I got this error.
After deleting the first line on updater-script file I got another error:
Creating symlinks....
symlink: some symlinks filederror in /storage/...
(Status 7)
installation aborded.
I have tried to delete also the second line and the third and the 4th but every time the same error.
Do you have any idea of what is happening?
Can you please provide some basic instructions on how to install this custom ROM with Flashtool?
Thank you
Click to expand...
Click to collapse
First, you can't just go deleting lines; if they are there, it's for a reason. Second, I'm pretty sure your CWM version isn't up to date in order to flash a CM12 ROM. And, you can't flash a Custom ROM with Flashtools.
What you can do, however, is extract the boot.img from the ZIP file, flash that kernel with Flashtool, and then Flash the ROM in what most likely would now be TWRP recovery.
Related
Hello all,
I have an I9000B model. Volume keys do not work.
So far I've managed to install everything through ROM Manager. But now, while trying to update from some CM10 nightly to the stable version, the installation is aborted with the message:
============================================
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
============================================
I understand that if I just rolled the menu down to perform installation again it would work, but I'm unable to do that! My question is: can I modify updater.sh to install again without requiring me to explicitly selecting the menu?
Is there any alternative option?
regards,
Never mind! I just opened updater.sh and modified it to not check for the file.
regards,
wsteel said:
Never mind! I just opened updater.sh and modified it to not check for the file.
regards,
Click to expand...
Click to collapse
Nice! But what the hell does it mean? Where the file is? How to update that?
The updater.sh -Skript you can find in the zip-file for example when you opening it with winrar, 7zip or something else ...
Look in the zipfile of your CM nightly ..
I think wsteel edit the file and removed the request for the partition layout or he set it "true" in the skript so he would not ask while flashing ...
mess18 said:
Nice! But what the hell does it mean? Where the file is? How to update that?
Click to expand...
Click to collapse
mess18 said:
Nice! But what the hell does it mean? Where the file is? How to update that?
Click to expand...
Click to collapse
You don't need to worry about that file.When the warning comes, just check "install zip" again and it will be flashed. It is just a warning. Anybody who reads opening post can find that info there.
tetakpatak said:
You don't need to worry about that file.When the warning comes, just check "install zip" again and it will be flashed. It is just a warning. Anybody who reads opening post can find that info there.
Click to expand...
Click to collapse
Thanks guys!
Meantime I have dug in forums and found another solution, which I have implemented and it worked: I have started from the beginning installing safe stock ROM, then I've rooted with Overcome 4, and then I've installed a 10.1 custom ROM. After that I could install any ROM without this interruption and message.
...and it's all about the SG Tab P1000...
Thanks for the info ...so now you can flash your ROM which you wanted ...
mess18 said:
Thanks guys!
Meantime I have dug in forums and found another solution, which I have implemented and it worked: I have started from the beginning installing safe stock ROM, then I've rooted with Overcome 4, and then I've installed a 10.1 custom ROM. After that I could install any ROM without this interruption and message.
...and it's all about the SG Tab P1000...
Click to expand...
Click to collapse
mess18 said:
Thanks guys!
Meantime I have dug in forums and found another solution, which I have implemented and it worked: I have started from the beginning installing safe stock ROM, then I've rooted with Overcome 4, and then I've installed a 10.1 custom ROM. After that I could install any ROM without this interruption and message.
...and it's all about the SG Tab P1000...
Click to expand...
Click to collapse
Once you take off for upgrading to CM10.2 the partition warning will appear again, as CM10.2 uses now different system partition size than the CM10.1x does. Don't care about that, just choose again "install zip".
Just don't forget to backup all your data (contacts, sms, app data etc). Once upgraded, you should be able to restore /data from your nandroid backup done by CM10.1x (under "advanced restore") Titanium backup can restore app data.
Hi,
I would need some help , I got the 4.3 update on my htc one unlocked international today, First small update completed fine but the main one fails with this error message :
assert failed apply_patch_check ("system/xbin/nc"
( there is 2 quite long GUIDs after the message )
have anybody encountered this issue ?
Thanks
mystborn said:
Hi,
I would need some help , I got the 4.3 update on my htc one unlocked international today, First small update completed fine but the main one fails with this error message :
assert failed apply_patch_check ("system/xbin/nc"
( there is 2 quite long GUIDs after the message )
have anybody encountered this issue ?
Thanks
Click to expand...
Click to collapse
found that the file its referring to is most likely NetCat from busybox. ( I have also the sense 5 toolbox installed but not the Xposed framework, someone said that might cause issues )
have uninstalled both and re-downloading the update , will report back the result
mystborn said:
found that the file its referring to is most likely NetCat from busybox. ( I have also the sense 5 toolbox installed but not the Xposed framework, someone said that might cause issues )
have uninstalled both and re-downloading the update , will report back the result
Click to expand...
Click to collapse
for an OTA to work, you need to be on stock recovery and complete stock rom; cause the OTA checks the most/if not all of the files on the current rom, and if it sees a discrepancy (either missing file or different version), it won't (actually can't) update, cause the OTA is just a diff between two version.
nkk71 said:
for an OTA to work, you need to be on stock recovery and complete stock rom; cause the OTA checks the most/if not all of the files on the current rom, and if it sees a discrepancy (either missing file or different version), it won't (actually can't) update, cause the OTA is just a diff between two version.
Click to expand...
Click to collapse
I have the original stock rom with stock recovery relocked bootloader, s-off, rooted.
i havent modified other stuff, as far as i remember,
you think its best to wipe and reinstall stock ?
mystborn said:
I have the original stock rom with stock recovery relocked bootloader, s-off, rooted.
i havent modified other stuff, as far as i remember,
you think its best to wipe and reinstall stock ?
Click to expand...
Click to collapse
well the "assert failed apply_patch_check ("system/xbin/nc"" means that file (/system/xbin/nc) is not the version the OTA expected (ie 100% stock ROM), and therefore cannot update.
nkk71 said:
well the "assert failed apply_patch_check ("system/xbin/nc"" means that file (/system/xbin/nc) is not the version the OTA expected (ie 100% stock ROM), and therefore cannot update.
Click to expand...
Click to collapse
and the 2 long strings are hashes, one is the expected and the other is which I have...
so far I have found that file is NetCat, and quite possibly BusyBox modified it as it is included in it...
do you think it would be possible just to replace that file with an original ?
mystborn said:
and the 2 long strings are hashes, one is the expected and the other is which I have...
so far I have found that file is NetCat, and quite possibly BusyBox modified it as it is included in it...
do you think it would be possible just to replace that file with an original ?
Click to expand...
Click to collapse
I guess so, you could extract it from the stock rom.zip and adb push it to the correct location, since you have SU privileges.
nkk71 said:
I guess so, you could extract it from the stock rom.zip and adb push it to the correct location, since you have SU privileges.
Click to expand...
Click to collapse
I have tried via root explorers ( mounted the system RW ) but couldnt copy out for backup , also the file looks like 0
byte..
Bit the bullet and overwrote the file, the update proceeded past the issue , will report back
mystborn said:
I have tried via root explorers ( mounted the system RW ) but couldnt copy out for backup , also the file looks like 0
byte..
Bit the bullet and overwrote the file, the update proceeded past the issue , will report back
Click to expand...
Click to collapse
That did the job, now I am running 4.3
mystborn said:
That did the job, now I am running 4.3
Click to expand...
Click to collapse
Congrats mate, I thought I saw an earlier post with something like "OTA Check Tool"? What's that?
Anyway, glad it worked out :good::good:
You may want to change the main thread title to include [SOLVED] for other to know
It was the "ota verify tool" from scary alien it is in beta, gave me a bit of bollocks but should be something of a nice tool when it fleshes out properly
I will mark the thread solved , thanks for the note.
Although according to google I am the only one who cocked his phone up this way hehe
Sent from my HTC One using xda app-developers app
mystborn said:
It was the "ota verify tool" from scary alien it is in beta, gave me a bit of bollocks but should be something of a nice tool when it fleshes out properly
I will mark the thread solved , thanks for the note.
Although according to google I am the only one who cocked his phone up this way hehe
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hmm thanks, I'll check that tool out when I get a chance, but like you said, it doesn't seem very accurate (at least yet).
And yes, I do believe you had an interesting approach at flashing an OTA
Hey guys,
Every time I try to flash a 4.4 rom whether it was Beanstalk or pure cyanogen 11 I got the same error while it I was flashing.
set_metadata_recursive: some changes failed
Then it says error in the file (status 7) installation aborted.
The only thing i could think of is that I am not s-off and I didn't see any requirements for that or anything else.
Thanks for any help.
jerham2010 said:
Hey guys,
Every time I try to flash a 4.4 rom whether it was Beanstalk or pure cyanogen 11 I got the same error while it I was flashing.
set_metadata_recursive: some changes failed
Then it says error in the file (status 7) installation aborted.
The only thing i could think of is that I am not s-off and I didn't see any requirements for that or anything else.
Thanks for any help.
Click to expand...
Click to collapse
I am afraid it's because of the recovery. It needs 2.6.3.3 recovery which isn't available for Sprint yet
Sent from my HTCONE using Tapatalk
elvisypi said:
I am afraid it's because of the recovery. It needs 2.6.3.3 recovery which isn't available for Sprint yet
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Well i looked up status 7 error and got a fix for deleting some of the script for the rom, but that didn't even start the installation of the rom so I guess i'll give up for now.
Also, if that recovery isn't available then how are people flashing these roms? I would assume because they are developers.
Hardly a definitive answer (because I don't use the ROM in question), but you could consider using a different recovery such as CWM. That said, I'm running the GE 4.4 port, so take with a grain of salt.
jerham2010 said:
Hey guys,
Every time I try to flash a 4.4 rom whether it was Beanstalk or pure cyanogen 11 I got the same error while it I was flashing.
set_metadata_recursive: some changes failed
Then it says error in the file (status 7) installation aborted.
The only thing i could think of is that I am not s-off and I didn't see any requirements for that or anything else.
Thanks for any help.
Click to expand...
Click to collapse
I have flashed all the 4.4 ROMs in developmental except Beanstalk on TWRP 2.6.3.0.
I'm running beanstalk without any problems, update TWRP to the last version
Terramoto said:
I'm running beanstalk without any problems, update TWRP to the last version
Click to expand...
Click to collapse
is the only way to switch to twrp through the bootloader? i'm running cwm right now. I know there is a way to go through goo manager but the file never downloads to install twrp to begin with. I'm just not destined to run 4.4 i guess!
Anyways, Thanks for all your guys help.
jerham2010 said:
is the only way to switch to twrp through the bootloader? i'm running cwm right now. I know there is a way to go through goo manager but the file never downloads to install twrp to begin with. I'm just not destined to run 4.4 i guess!
Anyways, Thanks for all your guys help.
Click to expand...
Click to collapse
I read somewhere you cant use goomanager now to flash TWRP, bootloader seems to be the only option unless there's a way to flash it through CWM...
Terramoto said:
I read somewhere you cant use goomanager now to flash TWRP, bootloader seems to be the only option unless there's a way to flash it through CWM...
Click to expand...
Click to collapse
Why not use a terminal emulator app? Although I have ran quite a bit of Kitkat roms and they all work for me.
Try this:
http://www.hasoon2000.info/?developer=One (M7,T-Mobile,ATT,Sprint)
Get the latest update of TWRP:
http://forum.xda-developers.com/showthread.php?t=2236620
Take that .img, rename it one word and put in the recoveries file in the AIO folder. Then use the tool to flash your updated recovery. It's what I did.
Hello!
Could someone port the latest TWRP to our Xperia V, please please please? ))
The latest 2.8.5 FOTAKernel Image for mint is working almost perfectly on our tsubasa, the only issue is it does not allow to flash serious zips, like ROM zips, because of the device check (it says I have mint and the flashable zip is only for tsubasa ). So could someone modify this device check to tsubasa somehow? And after that I guess it would good to go, since the 2 device, mint and tsubasa is almost the same in everything. :fingers-crossed:
Best regards,
Zalan
banciii said:
Hello!
Could someone port the latest TWRP to our Xperia V, please please please? ))
The latest 2.8.5 FOTAKernel Image for mint is working almost perfectly on our tsubasa, the only issue is it does not allow to flash serious zips, like ROM zips, because of the device check (it says I have mint and the flashable zip is only for tsubasa ). So could someone modify this device check to tsubasa somehow? And after that I guess it would good to go, since the 2 device, mint and tsubasa is almost the same in everything. :fingers-crossed:
Best regards,
Zalan
Click to expand...
Click to collapse
You might try the attached one.
I've unpacked the image and modified the default.prop file.. replaced every occurence of "mint" by "tsubasa"
However, I haven't tested it yet.
By the way, this is no flashable zip.. I had to compress the file because of XDA's file size limitation for .img files.
banciii said:
Hello!
Could someone port the latest TWRP to our Xperia V, please please please? ))
The latest 2.8.5 FOTAKernel Image for mint is working almost perfectly on our tsubasa, the only issue is it does not allow to flash serious zips, like ROM zips, because of the device check (it says I have mint and the flashable zip is only for tsubasa ). So could someone modify this device check to tsubasa somehow? And after that I guess it would good to go, since the 2 device, mint and tsubasa is almost the same in everything. :fingers-crossed:
Best regards,
Zalan
Click to expand...
Click to collapse
It has nothing to do with "serious zips". Read this if you like.
WhiteNeo said:
You might try the attached one.
I've unpacked the image and modified the default.prop file.. replaced every occurence of "mint" by "tsubasa"
However, I haven't tested it yet.
By the way, this is no flashable zip.. I had to compress the file because of XDA's file size limitation for .img files.
Click to expand...
Click to collapse
Thanks again, almost. With your img I can flash CM zip again, but gapps buggy. It installs without error, but after boot, every single google apps force close and can't use the ROM. Can't figure it out why, I made full clean install. Other features looks fine so far. But huge thanks for the try anyway.
banciii said:
Thanks again, almost. With your img I can flash CM zip again, but gapps buggy. It installs without error, but after boot, every single google apps force close and can't use the ROM. Can't figure it out why, I made full clean install. Other features looks fine so far. But huge thanks for the try anyway.
Click to expand...
Click to collapse
Wanna send a logcat of the fc? ^^
Maybe it's an issue with a recovery binary or something..
WhiteNeo said:
Wanna send a logcat of the fc? ^^
Maybe it's an issue with a recovery binary or something..
Click to expand...
Click to collapse
Ohh, did not think u would take care of it beside your other tons of work thanks, will try tomorrow ))
banciii said:
Ohh, did not think u would take care of it beside your other tons of work thanks, will try tomorrow ))
Click to expand...
Click to collapse
If it's easy to fix I'll try it. But I can't promise anything.
WhiteNeo said:
If it's easy to fix I'll try it. But I can't promise anything.
Click to expand...
Click to collapse
Just tried the backup-restore option with every partitions (dalvik, cache, system, data, secure). Dunno what exactly, but something is very buggy. I don't get any error during the backup, but after the restore, my phone does not start. When I choose system reboot after the restore I only get black blank screen after the sony kernel logo, then I get a reboot after about half minute and back into the recovery automatically.
So after that, I tried the install which I mentioned earlier. I wiped everything again and installed only 0214 nightly CM12 build. Booted, worked fine. Then installed the latest stock (PA) gapps, reboot and the gapps force closes started. Here is the logcat, but I guess it's not that case anymore since the buggy backup/restore function.
https://www.dropbox.com/s/b5lgn60s2l5xp8b/twrp-gapps.txt
I went to codeworks page:
There are 4 files for the x522 in firmware and 4 in modems. I am assuming the "19s" firmware is for India so is the "20s" for the US?
But the 4 files in the modem section is confusing, which one/one's are for the US model x522? here is the link for the modems https://host.llamasweet.tech/codeworkx/lineage/s2/
Thanks
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
leo221 said:
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
Click to expand...
Click to collapse
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
veda1 said:
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
Click to expand...
Click to collapse
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
leo221 said:
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
Click to expand...
Click to collapse
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
veda1 said:
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
Click to expand...
Click to collapse
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now?
Click to expand...
Click to collapse
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
Click to expand...
Click to collapse
Yep its still happening. Tried to flash it right now and it says "can't read" error.
veda1 said:
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
Click to expand...
Click to collapse
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
leo221 said:
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
Click to expand...
Click to collapse
Updated script according to the video, still not flashing, says "cannot read error"
veda1 said:
Updated script according to the video, still not flashing, says "cannot read error"
Click to expand...
Click to collapse
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
leo221 said:
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
Click to expand...
Click to collapse
Unbelievable! It actually worked after the 2nd attempt. Even got the 21s update. Thanks :good:
The original question is still unanswered about which one is the correct firmware for the US model amng the firmware provided by codeworks, hopefully someone knows that and will share in interest of others that might have the same problem.
Thanks again @leo221 for providing a clear and easy solution.