[Q] Trouble flashing ROMs - Nexus S Q&A, Help & Troubleshooting

So I've been doing a lot of searching and have tried several different "fixes" and ROMs but I still cant get my Nexus S to flash. since I'm still somewhat of a noob and cant figure out how to logcat I'll just type out what it says on my screen:
assert failed: getprop("ro.product.device") == "
crespo" || getprop(ro.build.product") == "cresp
o" || getprop("ro.product.board") == "crespo"
E:Error in /sdcard/update-cm-7.0.3-NS-signed.zip
(Status 7)
Installation aborted.
Thats what came up after I started flashing the ROM. I hope thats enough info for you guys to help me out. Sorry if this is the wrong forum. I'm desperate guys please help!

Rabbit_2.5 said:
Sorry if this is the wrong forum.
Click to expand...
Click to collapse
Yes it is, indeed.

Glad you could be such help. Thanks I figured it out
Sent from my Nexus S using XDA App

Related

gooapple v5 3g...any rom i try i get this error message

-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature length doesn't match EOCD marker
E:signature verifciation failed
Installation Aborted.
what can i do?
thanx
p.s.
when hold +key and power key for 10 secs I get Android system recovery <3e> in english
is the same to me I'm navigate in lot of forums but not find any info hey somebody can give us a hand with this?
Enviado desde mi GT-I9100 usando Tapatalk 2
Hey Guys,
The answers is really given more than once, reading is verry difficult sometimes i think...
You have to put the Chinese CWM installer back to the phone and than update your phone without problems. Use the searchbar and read de big Gooapple tread fully, and you will find the answer.
You can ask Anexonel13 as well, he did a lot of work on these phones. You could try to send a PM to him.
Regards Tom

[Q] Can't flash ROM - (BAD) error

I have been trying and reading over the past 2 days and I can't get this figured out. I got a Skyrocket on Friday and have been trying to get it rooted and flash a new ROM on it. I finally got it rooted and for the life of me I cannot get a ROM flashed. Every time I try, this is what it reads:
"ClockworkMod Recovery v5.0.2.6
-- Installing: /sdcard/{ROM file name}.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/{ROM file name}.zip
(bad)
Installation aborted."
I have tried flashing 3 different ROMs. I have downloaded 1 of them 3 times and the other 2 twice. This seems like a very easy process and I haven't had this much trouble in the past, but for some reason this phone doesn't seem to like the ROM files.
Any suggestions?
THIS ISNT THE SKYROCKET FORUM
Please look at the section you're in
Sent from my SGH-I777 using Tapatalk 2
its not working cause u flashing the wrong roms.....need to go to the skyrocket section.....then u can turn into a flashaholic like the rest of us

"Assert failed" while installing CyanogenMod through CWM

While attempting to install CyanogenMod 10.2 through CWM (6.0.4.6, from dasunsrule32), I got the following error:
assert failed: getprop("ro.product.device") == "tf700t" || getprop("ro.build.product") == "tf700t"
Click to expand...
Click to collapse
It may be worth noting that my device was already running Android 4.2, since the CM wiki instructions seem to assume an older version.
Installing TWRP and installing CM through that instead worked. I don't have enough posts to comment on the original CM thread in the Dev forum, but I wanted to report this bug and leave the note so other users might find the fix later. If someone with enough posts would like to cross-post this in the appropriate Dev forum thread (or otherwise make dasunsrule32 aware of the issue), it'd be much appreciated.
CWM
jschuster said:
While attempting to install CyanogenMod 10.2 through CWM (6.0.4.6, from dasunsrule32), I got the following error:
It may be worth noting that my device was already running Android 4.2, since the CM wiki instructions seem to assume an older version.
Installing TWRP and installing CM through that instead worked. I don't have enough posts to comment on the original CM thread in the Dev forum, but I wanted to report this bug and leave the note so other users might find the fix later. If someone with enough posts would like to cross-post this in the appropriate Dev forum thread (or otherwise make dasunsrule32 aware of the issue), it'd be much appreciated.
Click to expand...
Click to collapse
Im sure that recovery, is only for KitKat Roms, you need a different version of CWM to install JellyBean Roms.. This recovery will install CM10.2
TF700T-CWM6.0.3.1
Ahh, I was probably mistaken then. Still, some better labeling on these utilities would prevent further issues. Other than knowing that "kk" stands for "this only works on KitKat", there's nothing in the initial post in the thread for that version of CWM indicating what's supported and what isn't (there's a mention of "now compatible with KitKat", which sounds like it's still compatible with older things).

Bootloader version discrepancy

I have an issue that prevents me from flashing new CM roms - when ever i try to flash one i get an error that includes:
assert failed: getprop ("ro bootloader") == "HHZ11k"
i have gotten around this by editing the updatescript of the rom .zip to match my bootloader version: HHZ11d
So...whats going on here? Why did my bootloader change, or did I miss an update somewhere along the way? I would like to fix this so I dont have to keep editing update scripts. Any help is greatly appreciated.
EDIT: I found this page: http://www.randomphantasmagoria.com/firmware/nexus-5/hammerhead/
so i know im behind 1 update on my bootloader
is this a big deal? should I bother updating?
if i should update, is there any way to do so without going completely back to stock?
crackmulah said:
I have an issue that prevents me from flashing new CM roms - when ever i try to flash one i get an error that includes:
assert failed: getprop ("ro bootloader") == "HHZ11k"
i have gotten around this by editing the updatescript of the rom .zip to match my bootloader version: HHZ11d
So...whats going on here? Why did my bootloader change, or did I miss an update somewhere along the way? I would like to fix this so I dont have to keep editing update scripts. Any help is greatly appreciated.
EDIT: I found this page: http://www.randomphantasmagoria.com/firmware/nexus-5/hammerhead/
so i know im behind 1 update on my bootloader
is this a big deal? should I bother updating?
if i should update, is there any way to do so without going completely back to stock?
Click to expand...
Click to collapse
http://forum.xda-developers.com/google-nexus-5/help/error-flashing-cyanogen-mod-m5-t2708788
crackmulah said:
I have an issue that prevents me from flashing new CM roms - when ever i try to flash one i get an error that includes:
assert failed: getprop ("ro bootloader") == "HHZ11k"
i have gotten around this by editing the updatescript of the rom .zip to match my bootloader version: HHZ11d
So...whats going on here? Why did my bootloader change, or did I miss an update somewhere along the way? I would like to fix this so I dont have to keep editing update scripts. Any help is greatly appreciated.
EDIT: I found this page: http://www.randomphantasmagoria.com/firmware/nexus-5/hammerhead/
so i know im behind 1 update on my bootloader
is this a big deal? should I bother updating?
if i should update, is there any way to do so without going completely back to stock?
Click to expand...
Click to collapse
No idea why your new new bootloader cannot be installed mate, i`d reflash the complete stock rom from here http://forum.xda-developers.com/goo...-android-4-4-2-kot49h-rooted-busybox-t2557523. Just flash in recovery and after reboot check if the new BL is installed and flash CM11
thanks guys
im not sure why i didnt think that a bootload can just be flashed as normal - doiiiii (its been about 4 months since ive flashed anything on my device though, in my defense, so im a bit rusty)
i also had an extremely difficult time trying to find the updated bootloader and ended up using the link from @TheAtheistOtaku even though it seemed kinda sketchy to me
id expect all phones, especially the N5 to have an XDA downloads section/page with explicity labeled updates for all aspects of the phone. i think ive seen similar xda pages for other phones...
anyways i seem to be good to go now! thanks again!

[Completed] my note2 is dead.. pls help

i tried to install new rom to my note2 but if failed. it says "set_metadata_recursive: some changes failed E:Error in /external_sd/DN4_BY_ELECTRON_TEAM.zip (status 7) installation aborted."
im not sure whether I done any mistake while installing and now my phone cant load at all.. anyone can help me pls..
XDA Visitor said:
i tried to install new rom to my note2 but if failed. it says "set_metadata_recursive: some changes failed E:Error in /external_sd/DN4_BY_ELECTRON_TEAM.zip (status 7) installation aborted."
im not sure whether I done any mistake while installing and now my phone cant load at all.. anyone can help me pls..
Click to expand...
Click to collapse
Maybe you can still boot into download mode, then it's just a softbrick which can be fixed.
Check these threads about unbricking your device:
How to Unbrick Galaxy Note 2(GT-N7100)
[GUIDE] Fix an unflashable or soft bricked N7100!
Especially the second thread is a nice guide on how to do it.
If you have further questions, please register on xda (it's free), and post in the [NOOB FRIENDLY] Ask the question! [N7100 and other variants] thread.
Good luck !

Categories

Resources