[Q] Do you need ROM Manager to flash ICS 4.0.3? - General Questions and Answers

Hey this is my first time posting - I have a rooted Rogers Samsung Captivate i897 that I upgraded to Gingerbread 2.3.4 in November (with an AT&T based ROM). I am trying to upgrade the firmware to the new ICS 4.0.3 that is now available for this model as I am looking for something new.
So, I did some research and followed the directions that were posted (got ROM Manager, downloaded nightly .zip files & GApps). I then tried to back up my ROM using ROM manager (didn't work but thats OK I have the ROM file on my PC). And did the factory restore/cache wipe and tried to flash the .zip files from my SD and it didn't work.
Here is what it says when I try to flash:
"E: failed to verify whole-file signature"
"E: signature verification failed"
Question 1) What could be causing this error?
Question 2) Should I try to flash a stock ROM first before attempting to flash ICS?
Question 3) do I really need to use ROM Manager?? Is there another method available (flashing from PC from Odin)?
I am hesitant about doing this on the fly because when I updated to Gingerbread in November I had a good scare with my phone - soft bricked it, fixed that, and then got it stuck in a boot loop, then had issues with boot logo conflict between Rogers a AT&T. I was out of a phone for about a day working madly to fix it. I would like to avoid it again at all cost.
Phone Information:
Firmware Version: 2.3.4
Baseband Version: I897UCKH3
Kernel Version: 2.6.35.7-I897UCKH3-CL461307
Build Number: GINGERBREAD.UCKH3
Please help I appreciate it!!

Related

[Q] I need some answers about Nexus S

So I bought Nexus S from second hand recently mostly because it will get official ICS support from Google.
So because it's second hand buy, I really don't know if I'm using original bootloader, kernel, radio etc.
It's rooted (because I have Superuser app), I think it has stock 2.3.6 android (build number GRK39F) and kernel version 2.6.35.7-gf5f63ef, [email protected]#1.
Can someone who use stock android and original kernels confrime to me that this is right version?
I really want to update to ICS using incremental update which I found here (http://forum.xda-developers.com/showthread.php?t=1445635) but I'm affraid to don't screw something because of bad experience when I radio bricked my desire
Can I update it to ICS or I need to do unroot or something?
Just download the correct stock ICS rom for your device (if it is I9020T or I9023) ,put it on the SD root and then flash it using the stock or CWM recovery and be done with it (if you need the ICS)
most likely you won't be update by OTA because you are rooted (system file verification will fail)
just download stock ICS ROM and flash it ...
Ota will install fine if its a stock rom with just root. The update script basically checks that everything that should be there is there . If there is something else in there like su it don't matter.
flashing a new rom is the best way to go if you have cwm installed already
I succesfuly flashed ICS and first impressions are very good.
But I think I lost recovery...
jurvyx said:
I succesfuly flashed ICS and first impressions are very good.
But I think I lost recovery...
Click to expand...
Click to collapse
flash a CWM recovery via adb , or there is TWRP recovery in DEV section , which is very good .

[Q] getting back to GB

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

Error Status 7 (device name doesn't match) in Custom Rec when trying to install zips

Hello! Recently purchased a used (but like new) S Relay off of Ebay. It came with 4.1.2 already installed.
Basically let me tell you a brief backstory: I started off by installing Custom Recovery (CWM PhilZ 6.07) using ODIN and backing a NANDroid Backup. Then flashed KitKat CM 11 from CWM (wanted to try it out but didn't like it more than Jellybean). So I restored my backup via custom recovery.
Then I tried unlocking the sim network from T-mobile so I can use this phone when I travel abroad (using the method in http://forum.xda-developers.com/showthread.php?t=2255892 ). But apparently I found this doesn't work except on the stock Ice Cream Sandwich rom. So I flashed the LH1 stock rom using ODIN. Then I did the unlock method and it appeared successful. (it recognized an AT&T sim I have without asking for an unlock code)
So long story short, I used the custom recovery again to restore to my stock version of 4.1.2 Jellybean. But my baseband version is still LH1. I want to update it to UVMA2. I tried using a zip to update it from LH1 to UVMA2. But it always fails and aborts. It gives me Error Status 7. Which from google apparently means the device name doesn't match the one on the zip package.
I also try installing other minor packages. Which all incur the same error 7. So I'm not really sure if I'm just a really stupid beginner. Or if I've messed something up when I went to Kitkat and back. Or perhaps when I downgraded to 4.0 to unlock the network....
I tried using this ( http://forum.xda-developers.com/showthread.php?t=2302599 ) guide to fix the packages by removing the initial device name check. Yet it still fails/aborts before trying to install.
Any help or insights for this beginner would be greatly appreciated, thank you
Edit: The device name should be "apexqtmo" apparently...
Was able to flash to UVBMC5 baseband. Is that perhaps the latest version? It appears to be one of the most recent from google.

Help Rooting/flashing GT-S7562

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??

[Q] TWRP: AutoRec: cant flash roms

ive had this phone for a year and a half. i used ioroot, and autorec, and whenever i try to flash, its fails. how can i flash roms without fully restoring my phone back to jelly bean? (going back to rom version d80010d)
Current Version
Android: 4.4.2 Kitkat
ROM version: Stock D80020k
TWRP: 2.7.0.0
EDIT: i forgot to mention that i have the d800 variant.
1. re-download the rom, to make sure you don't have a corrupt download
2. what message is it saying when "fails to flash".........Ex. Does it say something like "error executing update binary"
3. You can adb sideload the rom (and push) (which will most like not work since twrp can't do it normally)

Categories

Resources