I now have superuser permissions on my Samsung Showcase From Cellular South When i go to the rom manager it only seems to let me flash the clockworkmod recov under galaxy s facinate can i use the others ????? also when i go to BACK UP CURRENT ROM it tells me that its ganna do it it roboots then it starts to install package and i receive this
finding update package
opening update package
verifing update package
and then in red i get
E failed to verify whole-file signature
E Signature verification failed
Installation aborted
Show how do i creat a back up befor i go bricking my phone since its no no longer under warrenty
I bricked my fitst galaxy and it was rooted, but manufactures warranty covered the brick. Cellular South
You need the zImage and redbend_ua files to flash your nand to enable backups. I will get link and send you
Sent from my Galaxy Showcase via Tapatalk
Related
so my phone is rooted and have downloaded the darkey Rom and next Rom manager but when i go to recovery mode and try to update the zip file its giving error saying "signature verification failed" so what's the reason and how to solve it my galaxy s is running on 2.3.3 firmware xxjvk
Hi,
I'm have trouble installing Cyanogen on my Galaxy S, i keep getting
-E: failed to verify whole-file signature
Ok so this is what i did.
1. i rooted my phone with z4root.apk
2. i downloaded rom manager off the market and installed the recovery mode
3.i put update.zip on the sd (the cyanogen rom zip)
4. cleared cach/factory reset
5. install from zip..... then
E: failed to verify whole-file signature
Im using clockwork mod v5.0.0.6
clockwork recovery v2.5.1.2
Phone details:
model: gt-i9000
firmware 2.2
baseband i9000dtjp3
kernal 2.6.32.9 [email protected] #7
build froyo.dtjp5
Can anyone tell me what is happening?
Hi Here I have a BIG problem with understanding whats going on. This is forth week how i'm trying to push update for GB 2.3.1.
a little story:
I had ICS based MIUI rom installed for around 1.5 year and was extremely happy with its UI and performance and regular weekly updates - since it become more and more lagy after every update. my phone was to week for its software and I decided go back stock.
My phones current details
nexus S
gingerbred 2.3.1
baseband : I9020XXKB3 (under battery GT-I9020T)
kernel : 2.6.35.7-g7f1638a
[email protected]#1
build number : GRH78
So what I done next i downloaded Odin and flashed stock gb 2.3.1 and now i can not update it in any way. System tryes to push OTA 4.0.1 but it ends up with following
______________________________
ClockworkMod Recovery v6.0.1.0
Finding update...
Opening update package..
Verifying update package..
E:failed to verify whole-file signature
E:signature verification failed
installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:radio:12583040:a32c1a32c13af21c32fa13af2c13a2f1a32fc12f31c2a3f1")
E:Error in /chache/odDgDain.zip
(status7)
Installation aborted
_________________________________
when i Rooted it i also noticed my outdated SU binary version 2.3.1 -ef
it also fails on update.
yesterday i tried to flash glados kernel through ROM manager and the phone crashed.
I have tried coupe different radios as well but ota update wont install Even with 'ota surviva'l and 'temp unroot' ticked in SuperUser
What should I do?
what causing all this?
should i install a different kernel or different gb version rom? In this case can U refer links pleas as Im TOTTALY LOST HERE guys
Thanx
smoke1 said:
Hi Here I have a BIG problem with understanding whats going on. This is forth week how i'm trying to push update for GB 2.3.1.
a little story:
I had ICS based MIUI rom installed for around 1.5 year and was extremely happy with its UI and performance and regular weekly updates - since it become more and more lagy after every update. my phone was to week for its software and I decided go back stock.
My phones current details
nexus S
gingerbred 2.3.1
baseband : I9020XXKB3 (under battery GT-I9020T)
kernel : 2.6.35.7-g7f1638a
[email protected]#1
build number : GRH78
So what I done next i downloaded Odin and flashed stock gb 2.3.1 and now i can not update it in any way. System tryes to push OTA 4.0.1 but it ends up with following
______________________________
ClockworkMod Recovery v6.0.1.0
Finding update...
Opening update package..
Verifying update package..
E:failed to verify whole-file signature
E:signature verification failed
installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:radio:12583040:a32c1a32c13af21c32fa13af2c13a2f1a32fc12f31c2a3f1")
E:Error in /chache/odDgDain.zip
(status7)
Installation aborted
_________________________________
when i Rooted it i also noticed my outdated SU binary version 2.3.1 -ef
it also fails on update.
yesterday i tried to flash glados kernel through ROM manager and the phone crashed.
I have tried coupe different radios as well but ota update wont install Even with 'ota surviva'l and 'temp unroot' ticked in SuperUser
What should I do?
what causing all this?
should i install a different kernel or different gb version rom? In this case can U refer links pleas as Im TOTTALY LOST HERE guys
Thanx
Click to expand...
Click to collapse
It's normal you can't flash OTA because you have a custom recovery. You need stock recovery for that. You can download a factory image from Google, extract it and flash the recovery inside using fastboot.
https://developers.google.com/android/nexus/images#soju
ALSO, stop using Odin. There's no need to use Odin or nearly on Nexus S. This thing is nearly unbreakable and you have more chances of breaking stuff with Odin than anything else.
thanx for quick replay
flashed factory GB 2.3.6 straight away using sdk tools
now will root it and install custom clockwork recovery to prevent from automatic OTA updating to lagy ICS
Use FOTAKill instead,
http://forum.xda-developers.com/showthread.php?t=1579154
Thanx for good advice. Installed it allready.
Sent from my Nexus S using xda premium
Hi everyone,
I am trying to flash a custom ROM that I created (Android 4.2.2 downloaded from google repo and kernel downloaded from samsung opensource) to my SAMSUNG Galaxy S3 mini SM-g730a (AT&T). The problem is that this phone seems impossible to flash with unsigned or non-samsung roms!
I tried to upload boot.img and system.img through heimdall and it gives me an error (ERROR: Failed to confirm end of file transfer sequence!).
I tried to upload it with ODIN but gives me an error (Security check error)
I tried to create a zip with Android Kitchen and install it from the recovery mode and this time the error is about the sign of the zip. I tried to look for a customized version of recovery mode but I could not find one compatible with this phone. So, I cannot install it from the zip since I cannot sign the zip as samsung.
At this point I am tempted to take the phone and flush it in the toilet!!!
Any suggestion or anyone that could install a custom ROM?
Thanks
Marco
Your phone needs to be unlocked.
This is a little late but safestrap was just ported to the g730a.
I find Root
Hi, so i ran in to some problems and questions while fixing my girlfriends galaxy s duos (GT-S7562).
I wanted to install a debloated firmware/root the device to uninstall bloatware because it got dead slowly in the last few weaks.
some info:
AP: S7562XXALJ4
CP: S7562XXLJ3
CSC: S7562ATOALH1
free handset bought in Austria
First of all I followed this guide.
I installed the clockwork recovery first, but when booting into it I don't get the usual backup option I normaly found on my older android devices.
When I try to root it i get error "failed to verify whole-file signature" and "signature verification failed".
Last I wanted to ask what roms are possible to install on my device,
fyi: KyleOPEN ROM says it needs XXBMD6 Base rom
but how can I get this Base rom? or is it impossible for me to flash this rom?
any help/explanation would be appreciated!
orso7 said:
Hi, so i ran in to some problems and questions while fixing my girlfriends galaxy s duos (GT-S7562).
I wanted to install a debloated firmware/root the device to uninstall bloatware because it got dead slowly in the last few weaks.
some info:
AP: S7562XXALJ4
CP: S7562XXLJ3
CSC: S7562ATOALH1
free handset bought in Austria
First of all I followed this guide.
I installed the clockwork recovery first, but when booting into it I don't get the usual backup option I normaly found on my older android devices.
When I try to root it i get error "failed to verify whole-file signature" and "signature verification failed".
Last I wanted to ask what roms are possible to install on my device,
fyi: KyleOPEN ROM says it needs XXBMD6 Base rom
but how can I get this Base rom? or is it impossible for me to flash this rom?
any help/explanation would be appreciated!
Click to expand...
Click to collapse
The XXBMD6 base ROM is available here: http://www.sammobile.com/firmwares/
Just input your phones model number into the device search and download the one with the matching PDA file end.
For the recovery issues, some recoveries are different based on the devices capabilities but overall most options like install.zip and nandroid backups should be available.
To flash the base ROM use odin and flash as if you're returning to stock then follow the guide.
And there are many ROMs available for your device, there's a list in the thread you posted
thanks for your answer, so I just have to flash any of the XXBMD6 roms over my XXALJ4 (I guess this is the PDA file end you're talking about)?
after this I am able to install mentioned KyleOPEN ROM?
sorry I'm almost new in this topic (last android phone was a htc legend, forgot everything)
edit: the problem with the recovery was that it switched back to stock recovery itself, found the workaround with renaming the install_recovery
hi
https://mega.co.nz/#!Tdx1SJ7J!nN5xrGqgvYfVANpz9bbSUJ5Ps_7pO_d3q95W8_djkHQ
Please forgive me English is very bad，Use odin brush into recovery, then root
Changing Baseband
orso7 said:
thanks for your answer, so I just have to flash any of the XXBMD6 roms over my XXALJ4 (I guess this is the PDA file end you're talking about)?
after this I am able to install mentioned KyleOPEN ROM?
sorry I'm almost new in this topic (last android phone was a htc legend, forgot everything)
edit: the problem with the recovery was that it switched back to stock recovery itself, found the workaround with renaming the install_recovery
Click to expand...
Click to collapse
I am in the same situation. I'm interested in what you have done on this issue??