Hi!
Can somebody flash following ZIP in the FACTORY recovery?
https://docs.google.com/file/d/0Bwt_FvteRPD7WkN1YlVXYlFwbmM/edit?usp=sharing
I just want to know whether it works.
Maybe I can create a "Root.zip" package using this but first I need to know the thing above.
Information:
This ZIP was extracted from an original GT-I8190 firmware, namely from the I8190XXAMA2_I8190OXXAMA2_XEO.
Package contains multi CSC definitions, you can check the country codes in the package's /system/csc folder.
Flashing this will not brick your device just refreshes the CSC.
Would you like to elaborate a bit more people like to know a bit more about these things before they flash and test..
Sent from my GT-I8190 using xda premium
Whats in it? 55mb?
Info
First post updated.
CSC carrier codes and no it will not work in a stock recovery.
Benzonat0r said:
CSC carrier codes and no it will not work in a stock recovery.
Click to expand...
Click to collapse
Have you tried or you just simple wrote here a response?
Do we even need root zip now? We can just flash cwm in odin and reset counter
tys0n said:
Do we even need root zip now? We can just flash cwm in odin and reset counter
Click to expand...
Click to collapse
No, of course we don't. But what about alternative, working, and easier methods?
ladislav.heller said:
Have you tried or you just simple wrote here a response?
Click to expand...
Click to collapse
No I haven't tried cause I simply know it will not work.
But this script will.
Code:
show_progress(0.100000, 0);
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
package_extract_dir("system", "/system");
show_progress(0.500000, 0);
unmount("/system");
Benzonat0r said:
No I haven't tried cause I simply know it will not work.
Click to expand...
Click to collapse
OK, so please explain a little bit deeper why then Samsung puts a flashable package (sec_csc.zip) into its own firmware? I extracted it from an original firmware! Who will then execute the script inside the package?
ladislav.heller said:
No, of course we don't. But what about alternative, working, and easier methods?
Click to expand...
Click to collapse
I agree. It was more like a joke, just because I was happy about it
ladislav.heller said:
OK, so please explain a little bit deeper why then Samsung puts a flashable package (sec_csc.zip) into its own firmware? I extracted it from an original firmware! Who will then execute the script inside the package?
Click to expand...
Click to collapse
I've been thinking bout that csc.zip also, as it installs upon boot right after flash...
tys0n said:
I agree. It was more like a joke, just because I was happy about it
I've been thinking bout that csc.zip also, as it installs upon boot right after flash...
Click to expand...
Click to collapse
Exactly. Right after flashing the whole firmware. Like on other Samsung devices (Galaxy Ace for example).
Finding update package...
Opening update package...
Verifying update package...
Installing update...
The install meter moves about a cm, then stops.
Dont know if it installs right, but no errors
tys0n said:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
The install meter moves about a cm, then stops.
Dont know if it installs right, but no errors
Click to expand...
Click to collapse
What do you mean by "then stops" ? What happened? The progressbar stopped?
Whatever, it seems that this package's signature is correct and maybe we can use it for some tricks.
ladislav.heller said:
What do you mean by "then stops" ? What happened? The progressbar stopped?
Whatever, it seems that this package's signature is correct and maybe we can use it for some tricks.
Click to expand...
Click to collapse
Yes the progressbar stopped.
When looking at the file-dates in csc-folder, they're all from yesterday, so no updates done in there as far as I can see.
However, there is no errors on screen..so you are probably right about signature.
tys0n said:
Yes the progressbar stopped.
When looking at the file-dates in csc-folder, they're all from yesterday, so no updates done in there as far as I can see.
However, there is no errors on screen..so you are probably right about signature.
Click to expand...
Click to collapse
Thanks for your help, dude! The most important, that we have a package with correct signature and it works from factory recovery!
ladislav.heller said:
Thanks for your help, dude! The most important, that we have a package with correct signature and it works from factory recovery!
Click to expand...
Click to collapse
No problems. Just load it with some porn and give it to me, and we'll se how funny things get
tys0n said:
No problems. Just load it with some porn and give it to me, and we'll se how funny things get
Click to expand...
Click to collapse
Tried to modify original package (sec_csc.zip) following way:
- Removed system folder
- Replaced script to my own, which only prints some info about device
- Everything other untouched
Result in recovery:
"Signature verification failed"
What did I say?
Hmm, maybe it's not only a signature but also some checksum implementation
Related
Hey guys, i don't usually make posts for every question i have, unless i absolutely don't find an answer searching or googling. I find myself in the position where i want to customize my Hyperdroid ROM and i can't manage to install DOC's Surgeon.
I think maybe the file i find in AndroidMeda Rom Tool is just an update, and not a full release, but being a noob is difficult, and i really didn't managed to pass this!
So, long story short, how can i flash a surgeon that is on androidmeda rom tool? I tried the Surgeon_Lucid_v5.0.zip and i can't get through, it fails to install under recovery mode.
I would very much appreciate a solution to my dumb question, hope i don't irritate somebody.
mightyvenom said:
Hey guys, i don't usually make posts for every question i have, unless i absolutely don't find an answer searching or googling. I find myself in the position where i want to customize my Hyperdroid ROM and i can't manage to install DOC's Surgeon.
I think maybe the file i find in AndroidMeda Rom Tool is just an update, and not a full release, but being a noob is difficult, and i really didn't managed to pass this!
So, long story short, how can i flash a surgeon that is on androidmeda rom tool? I tried the Surgeon_Lucid_v5.0.zip and i can't get through, it fails to install under recovery mode.
I would very much appreciate a solution to my dumb question, hope i don't irritate somebody.
Click to expand...
Click to collapse
You should download again, and apply the surgeon in the rom tool!
sonyz7 said:
You should download again, and apply the surgeon in the rom tool!
Click to expand...
Click to collapse
I have already done that...
Have you asked on the Hyperdroid thread. I think you may have more luck.
Sent from my GT-I9100
sxi200 said:
Have you asked on the Hyperdroid thread. I think you may have more luck.
Sent from my GT-I9100
Click to expand...
Click to collapse
Unfortunately i can't post there, i don't got the minimum 10 posts...ridiculous i know :-<
Quote from Android system recovery <3e>:
"E: missing bitmap password_retry_45 (Code -1)
E: missing bitmap password_notmatched_45 (Code -1)
E: missing bitmap password_max16_45 (Code -1)"
When installing multi-csc it says the following (also in android system recovery):
"-- Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/KOR/system/'.
Successfully applied multi-CSC."
Have you changed the kernel from the one that comes with Hyperdroid? As the OTA tool will only work automatically with the kernel the rom comes with.
If so you will need to download the file via the OTA tool, find where it saves, should be somewhere in the SD card (Hint /sdcard/Hyperdroid_Androidmedia)
Reboot into CWM recovery
Flash the zip manually.
veyka said:
Have you changed the kernel from the one that comes with Hyperdroid? As the OTA tool will only work automatically with the kernel the rom comes with.
If so you will need to download the file via the OTA tool, find where it saves, should be somewhere in the SD card (Hint /sdcard/Hyperdroid_Androidmedia)
Reboot into CWM recovery
Flash the zip manually.
Click to expand...
Click to collapse
Thanks, i will try that right away and report back
mightyvenom said:
Thanks, i will try that right away and report back
Click to expand...
Click to collapse
even if you changed kernels you can still flash stuff that you download from the OTA tool. So say you want to download Docs surgeon. Download it through the OTA app and then rather than apply now press apply later. Then try and get into recovery..there install zip and go through the folder were it says hyperdroid androidmeda...there you have all the files you have downloaded and just flash like you would normally do something...But only use this if you want to change kernels..My advice is the same as the guy above posted..Use the kernel provided by the team and you should not have any problems flashing stuff through the OTA app...
It worked fine, thank you again. Now i figured, indeed the change of my kernel led to that conflict.
Cheers guys!
mightyvenom said:
It worked fine, thank you again. Now i figured, indeed the change of my kernel led to that conflict.
Cheers guys!
Click to expand...
Click to collapse
Huh, I didn't think about you changed the kernel. Pongster's HDK kernel is very good, don't change that in my opinion.
So, Im glad that your problem solved.
Tapatalk
So I rooted my phone (2.3.4) and put the MiUi on my SD storage. I have CWM installed and when I go to install the ROM this pops up:
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installing aborted.
So this happens when I try to install the file from the CWM app while on the phone, but it also does this when I just try to boot into CWM.
Any help???
Chubby_Skunk said:
So I rooted my phone (2.3.4) and put the MiUi on my SD storage. I have CWM installed and when I go to install the ROM this pops up:
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installing aborted.
So this happens when I try to install the file from the CWM app while on the phone, but it also does this when I just try to boot into CWM.
Any help???
Click to expand...
Click to collapse
What kernel are you running? Your not using the cwm from rom manager right? Using one from a kernel? You could try and shut off your signature verification setting in cwm that should let you flash it. You'll find the option under the install from sdcard option then just toggle off your signature verifications.
Gutterball said:
What kernel are you running? Your not using the cwm from rom manager right? Using one from a kernel? You could try and shut off your signature verification setting in cwm that should let you flash it.
Click to expand...
Click to collapse
Yeah im using Clock Work Mod... :/
Where is the one that i'm suppose to use? I just want MiUi :/
Chubby_Skunk said:
Yeah im using Clock Work Mod... :/
Where is the one that i'm suppose to use? I just want MiUi :/
Click to expand...
Click to collapse
Like I said you could actually probably flash it with that but you just gotta shut off your signature verification option. Though people have said its not advisable. If you wanna do it the right way? Flash a kernel from development it has the correct cwm built into it.
Gutterball said:
Like I said you could actually probably flash it with that but you just gotta shut off your signature verification option. Though people have said its not advisable. If you wanna do it the right way? Flash a kernel from development it has the correct cwm built into it.
Click to expand...
Click to collapse
I'm still confused. So all I have to is flash a kernel and then it'll work???
Chubby_Skunk said:
I'm still confused. So all I have to is flash a kernel and then it'll work???
Click to expand...
Click to collapse
The correct kernel you need to flash is the siyaah kernel when you do this it will automatically install the correct cwm then you should be able to flash miui no problem.
Wow....................... I tried to install the Kernel in CWM like the dev said, and I get the same error message.... this is getting really annoying. The Atrix was less painful than this is being :/
Chubby_Skunk said:
Wow....................... I tried to install the Kernel in CWM like the dev said, and I get the same error message.... this is getting really annoying. The Atrix was less painful than this is being :/
Click to expand...
Click to collapse
Its just a little different then the atrix was but definetly better! Just gotta get used to some new stuff a little bit. I love this phone! Did you try toggling off the signature verification option??
Gutterball said:
Its just a little different then the atrix was but definetly better! Just gotta get used to some new stuff a little bit. I love this phone! Did you try toggling off the signature verification option??
Click to expand...
Click to collapse
uh, no. how do i do that? I just used Odin3 to flash the .tar file for that kernel.
Chubby_Skunk said:
uh, no. how do i do that? I just used Odin3 to flash the .tar file for that kernel.
Click to expand...
Click to collapse
Odins fine didnt realize you knew how to flash it that way. That'll work!
Gutterball said:
Odins fine didnt realize you knew how to flash it that way. That'll work!
Click to expand...
Click to collapse
Just tried it and i didn't change. it was still the same -_-
This is frustrating. The Captivate was 1000000000000000000000x easier to root and flash.
Gutterball said:
The correct kernel you need to flash is the siyaah kernel when you do this it will automatically install the correct cwm then you should be able to flash miui no problem.
Click to expand...
Click to collapse
SiyahKernel's included CWM has had a lot of problems lately.
The reference CWM kernel to use is codeworkx's CWM kernel - there is a thread on it in Development.
Chubby_Skunk said:
Just tried it and i didn't change. it was still the same -_-
This is frustrating. The Captivate was 1000000000000000000000x easier to root and flash.
Click to expand...
Click to collapse
When you flashed it in odin? you flash it as a pda in download mode right? If you did then you should have the right cwm now and miui should install through cwm.
Gutterball said:
When you flashed it in odin? you flash it as a pda in download mode right? If you did then you should have the right cwm now and miui should install through cwm.
Click to expand...
Click to collapse
well ill try it again.....
Chubby_Skunk said:
well ill try it again.....
Click to expand...
Click to collapse
If that doesn't work then use entropys kernel found here http://forum.xda-developers.com/showthread.php?t=1289460. It kicks ass but you cant use it with miui or cm7. but this will give you the proper cwm then install miui.
This is just f***ing ridiculous. So I tried it and when it works, when the phone boots up it shows:
Samsung Galaxy S II
GT-I9100
under than it shows an yellow triangle with a explanation point inside it. The phone boots up and CMW is nowhere to be seen.....
Chubby_Skunk said:
This is just f***ing ridiculous. So I tried it and when it works, when the phone boots up it shows:
Samsung Galaxy S II
GT-I9100
under than it shows an yellow triangle with a explanation point inside it. The phone boots up and CMW is nowhere to be seen.....
Click to expand...
Click to collapse
Heres the cwm link that entropy said to use http://forum.xda-developers.com/showthread.php?t=1285823 You gotta calm down and do a little research lol relax. That exclamation thing is nothing dont worry about it. Its perfectly normal!
Gutterball said:
Heres the cwm link that entropy said to use http://forum.xda-developers.com/showthread.php?t=1285823 You gotta calm down and do a little research lol relax
Click to expand...
Click to collapse
Thats the one i did and when the phone is back up and running, there is no Rom Manager anywhere on my phone. -_-
Chubby_Skunk said:
Thats the one i did and when the phone is back up and running, there is no Rom Manager anywhere on my phone. -_-
Click to expand...
Click to collapse
It doesnt need rom manager. You boot into cwm by holding your power button and volume up and down when the phone boots up. Thats your cwm.
Gutterball said:
It doesnt need rom manager. You boot into cwm by holding your power button and volume up and down when the phone boots up. Thats your cwm.
Click to expand...
Click to collapse
tried that too and nothing happened :/
it just waits a second and then goes to the AT&T splash screen and goes to the lock screen....
http://www.mediafire.com/?wkhvh91lp7792yr
Requirements:
1. A custom recovery.
2. A nandroid backup.
3. Stock files, sans root.
4. Optional, but recommended that you use this to backup root access first:
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en
It shouldnt hurt root either, but make a nandroid to be safe.
If you lose root, try flashing this:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
Updated: Removed tz.img because I don't think its needed.
So this is the OTA minus the new bootloader? So basically the new radios and the kernel patch only?
Trying this out but back up to two different locations just in case.
SeanPlunk said:
So this is the OTA minus the new bootloader? So basically the new radios and the kernel patch only?
Click to expand...
Click to collapse
Yep, and whatever else it patches.
So I can just make a nandroid and flash it over Beans v6 and it should install the radios just fine right?
nnnnr14 said:
So I can just make a nandroid and flash it over Beans v6 and it should install the radios just fine right?
Click to expand...
Click to collapse
Nope. Check requirements
I added a third one in anticipation of that question.
1) Will this work for the Verizon version of CleanRom?
2) Do I have to unroot? The directions aren't clear to me. Sorry about that.
3) If I do have to unroot, can I just use OTA rootkeeper to root again afterwards?
SeanPlunk said:
1) Will this work for the Verizon version of CleanRom?
2) Do I have to unroot? The directions aren't clear to me. Sorry about that.
3) If I do have to unroot, can I just use OTA rootkeeper to root again afterwards?
Click to expand...
Click to collapse
All answered in first post (requirements).
Thanks
1. No
2. No
3. If you lose root.
So ill have to be on stock rom...
nnnnr14 said:
So ill have to be on stock rom...
Click to expand...
Click to collapse
Yes. There is no safe way (that I know of) to force patch files on a custom rom.
When I get home, I can make a deodexed patch file, but it will overwrite any custom changes you have.
adrynalyne said:
Yes. There is no safe way (that I know of) to force patch files on a custom rom.
When I get home, I can make a deodexed patch file, but it will overwrite any custom changes you have.
Click to expand...
Click to collapse
Custom change? As in rom or themes cause I could always flash beans or another rom afterwards right?
nnnnr14 said:
Custom change? As in rom or themes cause I could always flash beans or another rom afterwards right?
Click to expand...
Click to collapse
Sure but if you flash a rom after, you just overwrite the OTA anyway.
Hey adrynalyne, thanks for all the work!
I'm about to apply this now and I have a quick question. I "Deferred" the initial update for a few days, so if apply this, will my phone still try to do the update after the deferred time? Or will it do a check on the version and see its already updated?
Thanks,
Niko49 said:
Hey adrynalyne, thanks for all the work!
I'm about to apply this now and I have a quick question. I "Deferred" the initial update for a few days, so if apply this, will my phone still try to do the update after the deferred time? Or will it do a check on the version and see its already updated?
Thanks,
Click to expand...
Click to collapse
It will stop annoying you if you apply this.
adrynalyne said:
Sure but if you flash a rom after, you just overwrite the OTA anyway.
Click to expand...
Click to collapse
Ohhh... :/
Everytime I try to apply this I get "assert failed: apply_patch_check("/system/app/SystemUI.apk", "<insert some hash>", "<insert different hash>")"
I am running CWM v6.0.2.5, and I am running the stock Verizon ROM with a few mods applied.
Yeah you have modified SystemUI.apk. You will need to put it back to stock. The original files must be in place.
Also, this might not remove an update if its been deferred. But the new one can't install over this one so... make sure you have a custom reovery flashed, run it and it won't be deferred anymore.
adrynalyne said:
Yeah you have modified SystemUI.apk. You will need to put it back to stock. The original files must be in place.
Also, this might not remove an update if its been deferred. But the new one can't install over this one so... make sure you have a custom reovery flashed, run it and it won't be deferred anymore.
Click to expand...
Click to collapse
Thanks, My "Wifi-Toggle" mod had modified it. It looks like we will also loose "All apps to Multi-Window mode" too, as the services.odex file has to be restored as well.
Niko49 said:
Everytime I try to apply this I get "assert failed: apply_patch_check("/system/app/SystemUI.apk", "<insert some hash>", "<insert different hash>")"
I am running CWM v6.0.2.5, and I am running the stock Verizon ROM with a few mods applied.
Click to expand...
Click to collapse
I am running TWRP and getting an error message as well:
assert failed: getprop("ro.product.device") == "getprop("ro.build.product") == "t0ltevzw"
E: error in /sdcard/safe_update.zip
(Status 7)
Error flashing zip '/sdcard/safe_update.zip'
cphastings said:
I am running TWRP and getting an error message as well:
assert failed: getprop("ro.product.device") == "getprop("ro.build.product") == "t0ltevzw"
E: error in /sdcard/safe_update.zip
(Status 7)
Error flashing zip '/sdcard/safe_update.zip'
Click to expand...
Click to collapse
Old versions of twrp have broken asserts. You will need to update twrp to the latest version.
Hey guys,
I rooted with an AIO tool. Everything went smoothly except for the fact that I cannot flash roms or any zip file without it failing due to signature verification. Can anyone help point me in the right direction? Thanks in advance!
Probably either bad downloads or you are downloading ROMs for the wrong phone.
mbh87 said:
Probably either bad downloads or you are downloading ROMs for the wrong phone.
Click to expand...
Click to collapse
The downloads are fine and I used the Verizon all in one tool posted on the forum. I even ran the tool again and it still will fail when trying to flash anything.
Try cwm. Never used twrp myself
bhp090808 said:
Try cwm. Never used twrp myself
Click to expand...
Click to collapse
Thanks bhp090808 for the awesome tool! This corrected the issue. I have no explanation but I guess twrp did not want to play nice.
After running the last step of the just released bootloader unlock, I get this.
Cannot open for read, no such file or directory
I'm copying and pasting, so I'm not sure what's wrong.
Edit- I got it! Making a backup, now. Bring on those ROMs, boys! Woohoo!
Just a thought but for other folks who might run into this issue, you could describe what you did to fix it - i.e., did you make a typo, did you put the file in the wrong directory...
phobos512 said:
Just a thought but for other folks who might run into this issue, you could describe what you did to fix it - i.e., did you make a typo, did you put the file in the wrong directory...
Click to expand...
Click to collapse
Re-installed the drivers. Don't know if that was it, but it finally went.
spotmark said:
After running the last step of the just released bootloader unlock, I get this.
Cannot open for read, no such file or directory
I'm copying and pasting, so I'm not sure what's wrong.
Edit- I got it! Making a backup, now. Bring on those ROMs, boys! Woohoo!
Click to expand...
Click to collapse
What you did to make this work?
android-incredible said:
What you did to make this work?
Click to expand...
Click to collapse
Don't know. Like I said, I re-installed the drivers, and just kept running the commands, and eventually it took.
android-incredible said:
What you did to make this work?
Click to expand...
Click to collapse
For me, my mistake was it got downloaded to the downloads folder and that's not the director being accessed. I didn't move it to just sit in the sdcard directory outside of a folder. So, when I ran the second command, I'd get your error. Moving the file solves the problem.
img
I flashed the image with flashify real easy
deathsquad737 said:
I flashed the image with flashify real easy
Click to expand...
Click to collapse
Was that all you needed to do to install the bump unlock and recovery is to flash the IMG file?
jlokos said:
Was that all you needed to do to install the bump unlock and recovery is to flash the IMG file?
Click to expand...
Click to collapse
Yes
WHATSAMATTA U ALUMNI
jlokos said:
Was that all you needed to do to install the bump unlock and recovery is to flash the IMG file?
Click to expand...
Click to collapse
Yes because it's the actual Recovery Image ( TWRP ) that's been Bump'd to work on our phones.
Bump isn't an app, it's a modified TWRP.