Related
I've deodexed my rom and now i cant OTA update. so now i want to ODEX again. hopefully without flashing new rom so i wont loose my data.
i found this to odex but im not sure what are the commands i should run
http://forum.xda-developers.com/showthread.php?p=44228706
so can someone help me with this?
dont waste your time, use flashtool or update service
cachanilla86 said:
dont waste your time, use flashtool or update service
Click to expand...
Click to collapse
i have a problem with downloading the whole rom, trying to avoid that
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
Hello all. I'm sorta new here.
I have rooted my XPERIA TL (LT30at) before, and flashed the XperimenT ROM for my first rom. I then went back to stock using Spectre51's AT&T FTF.
I'm now back to rooting it, rooted it just fine using Flashtool, but upon flashing any ROM I have lost WiFi and it just flat out doesn't work. Can anyone point me in the direction of what I can do?
lucar.ixuu said:
Hello all. I'm sorta new here.
I have rooted my XPERIA TL (LT30at) before, and flashed the XperimenT ROM for my first rom. I then went back to stock using Spectre51's AT&T FTF.
I'm now back to rooting it, rooted it just fine using Flashtool, but upon flashing any ROM I have lost WiFi and it just flat out doesn't work. Can anyone point me in the direction of what I can do?
Click to expand...
Click to collapse
flash the wifi modules.
You can find them in doomlords kernel thread.
gregbradley said:
flash the wifi modules.
You can find them in doomlords kernel thread.
Click to expand...
Click to collapse
Thanks very much for responding. Every time I try to flash the zip, I end up with a red triangle with an exclamation point on the Android, text saying Error in [file name], (Status 0) installation aborted.
...what's going on
EDIT: Nevermind...I was using something made for the PLAY. Now I find the actual thread you were referring to and now I can't find any standalone zip's to flash because the only thing there is the kernel itself (to flash). I don't believe DoomKernel is able to be flashed with the TL, so I don't think that's something I need to flash just to get the WiFi modules...or is it?
I really appreciate your patience.
lucar.ixuu said:
Thanks very much for responding. Every time I try to flash the zip, I end up with a red triangle with an exclamation point on the Android, text saying Error in [file name], (Status 0) installation aborted.
...what's going on
EDIT: Nevermind...I was using something made for the PLAY. Now I find the actual thread you were referring to and now I can't find any standalone zip's to flash because the only thing there is the kernel itself (to flash). I don't believe DoomKernel is able to be flashed with the TL, so I don't think that's something I need to flash just to get the WiFi modules...or is it?
I really appreciate your patience.
Click to expand...
Click to collapse
Look inside the .zip, I think the wifi modules are in there.
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.
Hi folks, I have an Xperia Z and its still stuck at 4.1.2
It's a prototype model, I've used the phone now for months and its been working great despite the lack of updates but I'm hoping it can have the latest software like the rest of the phones out there.
The bottom of the phone has C6606 written on it but the image on the screen shows C6616. Any suggestions would be appreciated.
tinodevoe said:
Hi folks, I have an Xperia Z and its still stuck at 4.1.2
It's a prototype model, I've used the phone now for months and its been working great despite the lack of updates but I'm hoping it can have the latest software like the rest of the phones out there.
The bottom of the phone has C6606 written on it but the image on the screen shows C6616. Any suggestions would be appreciated.
Click to expand...
Click to collapse
can you take a screenshot of the 6616 screen? and can you go to the firmware by customization thread and follow the instructions? what is your cust.# ?
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
tinodevoe said:
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
Click to expand...
Click to collapse
I think you can flash c6606 Software without problems... Maybe even of C6603 via Flashtool.
tinodevoe said:
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
Click to expand...
Click to collapse
OK, that is really very strange. You could try to contact DoomLord or Apollo89, they have knowledge of such things.
Are you rooted? Can you do a CWM Backup? I suggest having a full backup before flashing another rom. So in case you need it, you can flash it back.
I am not sure if you have the same kernel as the rest of us. If you can not do a CWM backup, and are not rooted, you need to find a way to extract the file "boot.img" from the phone. This is the kernel, which you can easily flash back. But for this operation, a bootloader unlock will most probably be necessary.
If you can get no help from Doom or Apollo and can not extract boot.img, you might need to flash hoping for luck, or stay on the firmware you have.
Disclaimer: I might be much too paranoid, after all your phone seems to have the same hardware as the normal one, and a flash of a 10.4.B.0.569 ROM should be no problem. I just don't want to be the one that did not warn you and be responsable for a broken phone...
===============================================================
EDIT: Just had a look at the thread, C6616 is bell Canada, if you had found that, you could have reported back and told us that you solved the problem.
===============================================================
thanks for the advice. I still haven't tried anything with the phone. I've unlocked and flashed the firmware on my old Galaxy Nexus which for some reason also never updated (bought directly from Bell) but this one trying to read through all the information I'm having some trouble deciding on which method to use and where to really start.
If someone has a simple tutorial on flashing these phones please do share, otherwise I might just leave it as is and by the latest Nexus when this phone's done.
tinodevoe said:
thanks for the advice. I still haven't tried anything with the phone. I've unlocked and flashed the firmware on my old Galaxy Nexus which for some reason also never updated (bought directly from Bell) but this one trying to read through all the information I'm having some trouble deciding on which method to use and where to really start.
If someone has a simple tutorial on flashing these phones please do share, otherwise I might just leave it as is and by the latest Nexus when this phone's done.
Click to expand...
Click to collapse
Here is the link where its all explained http://forum.xda-developers.com/showthread.php?t=2275632
Also there is this video http://www.youtube.com/watch?v=j8EQmufr0lw
You need to download latest flashtool and latest firmware FTF for your model and follow instructions, really not hard, hardest part is to w8 untill all that downloads from internet
N1k0la89 said:
Here is the link where its all explained http://forum.xda-developers.com/showthread.php?t=2275632
Also there is this video http://www.youtube.com/watch?v=j8EQmufr0lw
You need to download latest flashtool and latest firmware FTF for your model and follow instructions, really not hard, hardest part is to w8 untill all that downloads from internet
Click to expand...
Click to collapse
sorry to sound dumb, but I can't figure out which firmware to select for my phone. Can someone please recommend a link for the correct file to flash this with? Also does it matter which generic firmware I use? I don't want to get the Bell firmware and end up with all the bloatware they have on there. I'd prefer as close to a clean firmware as possible so I can start getting the latest updates onto this phone.
tinodevoe said:
sorry to sound dumb, but I can't figure out which firmware to select for my phone. Can someone please recommend a link for the correct file to flash this with? Also does it matter which generic firmware I use? I don't want to get the Bell firmware and end up with all the bloatware they have on there. I'd prefer as close to a clean firmware as possible so I can start getting the latest updates onto this phone.
Click to expand...
Click to collapse
I think all Generic firmwares have the same "bloatware" app in common and all carrier branded firmwares have their carrier specific apps, so just choose a generic firmware and then remove all unuseful bloatware apps (if you go root).
akisg said:
I think all Generic firmwares have the same "bloatware" app in common and all carrier branded firmwares have their carrier specific apps, so just choose a generic firmware and then remove all unuseful bloatware apps (if you go root).
Click to expand...
Click to collapse
I finally just tried one method, following the guide here; http://forum.xda-developers.com/showthread.php?t=2240614
I installed flashtool and installed the stock Bell software, http://forum.xda-developers.com/showthread.php?t=2390178
It looked like everything went fine and when checking system updates it showed 4.3 was finally available!
but then after it downloaded the file I tried to install and it just gave me an error message :crying:
So what would be the next step for me?
tinodevoe said:
I finally just tried one method, following the guide here; http://forum.xda-developers.com/showthread.php?t=2240614
I installed flashtool and installed the stock Bell software, http://forum.xda-developers.com/showthread.php?t=2390178
It looked like everything went fine and when checking system updates it showed 4.3 was finally available!
but then after it downloaded the file I tried to install and it just gave me an error message :crying:
So what would be the next step for me?
Click to expand...
Click to collapse
Any info about that error??
Why not flash to 4.3 directly with flashtool or to 4.2 and then upgrade to 4.3?
Also try a fresh install by wiping data (if you have already a backup of them of course) it maybe helps..
akisg said:
Any info about that error??
Why not flash to 4.3 directly with flashtool or to 4.2 and then upgrade to 4.3?
Also try a fresh install by wiping data (if you have already a backup of them of course) it maybe helps..
Click to expand...
Click to collapse
I've tried a couple times now to update that system update, its 10.4.B.0.569, once it starts to install it goes to the robot install logo at the startup for a second then starts the phone right away without doing the full install. The message on screen is simply "could not install".
i'll try a factory reset then directly to 4.3. I'm assuming I can use the same method as before or do I need to look into rooting the phone now?
tinodevoe said:
I've tried a couple times now to update that system update, its 10.4.B.0.569, once it starts to install it goes to the robot install logo at the startup for a second then starts the phone right away without doing the full install. The message on screen is simply "could not install".
i'll try a factory reset then directly to 4.3. I'm assuming I can use the same method as before or do I need to look into rooting the phone now?
Click to expand...
Click to collapse
As soon you are installing a stock rom, you don't have to worry about root.
But if you wanna root, your only choice is to flash a 4.2 rom, root it with a method of your choice and then upgrade to a prerooted 4.3.
Can someone please point me in the right direction to a FW that works with my phone? the only one that I seem to be able to use with flashtool is this one here which is 4.1.2. http://forum.xda-developers.com/showthread.php?t=2390178
however it won't let me update the system!
I'm guessing that I need a C6616 firmware to make this work, but I also tried this one, http://forum.xda-developers.com/showthread.php?t=2612159 and I get an error in flashtools, in red writing 'ERROR - error flashing. Aborted'.
I've been searching on here and all the other firmwares are 6603 which I tried a couple and again errors in flashtools.
trying again with that 4.1.2 its flashing it but its not the firmware I need!
ok, finally got one of them to work! I'm not sure what it was but I downloaded a bunch of firmwares until one of them finally updated me to 4.3.
thanks for all the help!