[Q] Nexus S: any Herring roms (instead of Crespo)? - General Questions and Answers

Apparently there are two distinct hardware versions of the Nexus S I9020T. One is called "Crespo" and one is called "Herring". Almost everything out there available to download is compatible with the crespo devices and not the herring devices.
According to my bootloader page, my Nexus S is herring.
I had some problems with trying to mod the phone, and now I really need to flash back to stock.
I tried flashing the Android 2.3.4/GRJ22 ROM that was linked to in this post: http://forum.xda-developers.com/showthread.php?t=1063664, but it failed with the error:
assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") == "crespo" || getprop("ro.product.board") == "crespo"
which leads me to believe that the ROM is only compatible with crespo builds of the Nexus S.
The only herring-specific thing I can find out there is an old version (2.5.1.8) of Clockwork Recovery
Is there a stock ROM for herring out there anywhere???

Anybody???

busyba said:
I tried flashing the Android 2.3.4/GRJ22 ROM that was linked to in this post: http://forum.xda-developers.com/showthread.php?t=1063664, but it failed with the error:
assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") == "crespo" || getprop("ro.product.board") == "crespo"
which leads me to believe that the ROM is only compatible with crespo builds of the Nexus S.
The only herring-specific thing I can find out there is an old version (2.5.1.8) of Clockwork Recovery
Is there a stock ROM for herring out there anywhere???
Click to expand...
Click to collapse
I also have a herring device and encountered this exact problem with the herring build of 2.5.1.8. I switched to the crespo build of 3.0.2.4 and was able to flash CM7.1 RC1 to the herring device without any issues.
Based on this I don't think ROMs are specific to either crespo or herring, and I have not encountered any adverse issues with Clockwork 3.0.2.4 crespo on my herring Nexus S.

yeah, apparently my issue with the crespo 3.0.2.4 recovery was just a matter of me assuming that it was hanging when in fact it was just taking a really long time to load for some reason. It took almot a full minute. In the past, I would just pull battery before giving it the full minute.
The weird thing is that since that first time that it started after the minute, it now starts up quickly, even after I reflashed it.
Anyway, I got CM7.1 RC1 flashed and running now. Thanks for your help!

I've got a herring device as well. I wonder what other differences exist between the two. I've seen a few strange flashing issues with some mods as well even though I've got CWM working fine (or so it seems).

i've got herring product and i don't see any differences..
i flashed literary all ROMs available and latest recoveries (CWM and TWRP i tried both)..

Crespo vs. Herring
Those names refers to different aspects:
Herring is the board, which should fit to the kernel build.
Crespo is the device codename, which should fit to the Android build.
http://forum.xda-developers.com/showthread.php?t=1242609

Related

[Q] Samsung Fascinate Vanilla GB help...

Do not have access to posting replies yet... so Im posting here
I was working on installing Vanilla GB (http://forum.xda-developers.com/showthread.php?t=1195355)
and i get this when installing zip from sdcard:
Installing update...
assert failed:getprop("ro.product.device")== "
aries l l getprop("ro.build.product") == "aries"
l l getprop("ro.product.board") == "aries"
it then repeats that message but instead of "aries" it says "fascinate" then "SCH-I500"
E:Error in/sdcard/full_fascinatemtd-ota-eng.jt1
134-0731.zip
(Status 7)
Installation aborted.
Help with where I may have messed up?
I flashed back to COMPLETE stock from MIUI. Did not flash cwm recovery again until tonight.
I have no idea about Vanilla GB.But I think MIUI is better.
-i'm new to this phone!! help me guys;.!!
-hope it work on CWR.!! huhuh.
Got it to work! Thanks goes to the guys on the FASCINATE Thread..great job!
and what was the solution? Having the same issues
leetercola said:
and what was the solution? Having the same issues
Click to expand...
Click to collapse
Same here!!!!!!!!!!

Any way to reinstall the OS from scratch on the phone????

So I was trying to get Wallet on my phone, complete mess, the phone went fubar, I can get the phone to work on stock 2.3.4 but can't update to 2.3.6 nor I can install any ROM, and yes, the phone is rooted.
If I try on updating to 2.3.6 I get >>>
assert failed: less_than_int(1303507835,getprop("ro.build.date.utc")
Status 7
If I try to install any Rom I get >>>
assert failed: getprop("ro.product.device") == "crespo" ll
getprop("ro.build.product") == "crespo"
And trying to restore will simply give me system.img not found.......
So if nothing works towards, then I will simply and rather prefer to do a clean install so it will wipe everything, but, is there a way to "Wipe" everything and reinstall?
And yes, I already tried the "Wipe data/factory reset", no good at all.
Upd: I can install kernels.....go figure.....
If this is a NS4G you can use OneClickStock
tylerwatt12 said:
If this is a NS4G you can use OneClickStock
Click to expand...
Click to collapse
Thx Mate but I have a i9023 (NS 3G+ if u can say), I was able to downgrade using the guide from TheUnlockr and it was a PITA since the file somehow is not really the best to work on the NS but I was able to update to 2.3.6.
And since now I'm updated and found a way to mess the phone even more it is time to try the Wallet again!!!

Crespo or Crespo4G?

Finally bought a Nexus S so that I could run CM. I've activated the phone with sprint, and loaded a few other ROMs just fine (running JRO03R - Stock 4.1.1 currently). I've got a SPH-D720, and I've tried loading both the cm-10-20121024-NIGHTLY-crespo.img and cm-10-20121024-NIGHTLY-crespo4g.img using CWM 6.0.1.0.
The "crespo" one will load without problems, boot up, and no network (baseband unknown, phone number unknown, etc.). I Can't load the "crespo4g" img as it returns with an error in CWM status 7.
What am I doing wrong?
datag0d said:
Finally bought a Nexus S so that I could run CM. I've activated the phone with sprint, and loaded a few other ROMs just fine (running JRO03R - Stock 4.1.1 currently). I've got a SPH-D720, and I've tried loading both the cm-10-20121024-NIGHTLY-crespo.img and cm-10-20121024-NIGHTLY-crespo4g.img using CWM 6.0.1.0.
The "crespo" one will load without problems, boot up, and no network (baseband unknown, phone number unknown, etc.). I Can't load the "crespo4g" img as it returns with an error in CWM status 7.
What am I doing wrong?
Click to expand...
Click to collapse
Crespo4G represents the Sprint version of the Nexus S (Nexus S 4G). Crespo = All other variants of the Nexus S. Crespo and crespo4g are the identifying names Google gave the devices. So basically, Crespo4G roms aren't for your phone, only Crespo.
datag0d said:
Finally bought a Nexus S so that I could run CM. I've activated the phone with sprint, and loaded a few other ROMs just fine (running JRO03R - Stock 4.1.1 currently). I've got a SPH-D720, and I've tried loading both the cm-10-20121024-NIGHTLY-crespo.img and cm-10-20121024-NIGHTLY-crespo4g.img using CWM 6.0.1.0.
The "crespo" one will load without problems, boot up, and no network (baseband unknown, phone number unknown, etc.). I Can't load the "crespo4g" img as it returns with an error in CWM status 7.
What am I doing wrong?
Click to expand...
Click to collapse
If you activated the phone with sprint then you have crespo 4g which is d720 model if your not on sprint then you have crespo . The reason there's no data is because those img where for crespo so there's no radio to get signal . You should get the stock img for cresop 4g from Google AOSP site & install them
Sent from my Nexus 7 using xda premium
When i try to use Crespo4g, I get:
assert failed: getprop("ro.product.device") == "crespo4g" || getprop("ro.build.product") == "crespo4g"
E:Error in /sdcard/cm-10-20121028-NIGHTLY-crespo4g.zip
(status 7)
Installation aborted.
Again, Sprint phone, SPH-D720.
datag0d said:
When i try to use Crespo4g, I get:
assert failed: getprop("ro.product.device") == "crespo4g" || getprop("ro.build.product") == "crespo4g"
E:Error in /sdcard/cm-10-20121028-NIGHTLY-crespo4g.zip
(status 7)
Installation aborted.
Again, Sprint phone, SPH-D720.
Click to expand...
Click to collapse
Install a newer version of ClockworkMod recovery: http://forum.xda-developers.com/showthread.php?t=1782240
But I think it might be because your zip file is corrupt and you need to re-download it.
I'm already running 6.0.1.0....
I thought about the corruption thing, downloaded it multiple times on home desktop and school laptop, both sources don't work. Verified md5sum on downloaded file.
Try the version 5.8.0.2, it works for me: http://forum.xda-developers.com/showthread.php?t=1242947
Or try TWRP recovery instead, though I have no experience with it: http://forum.xda-developers.com/showthread.php?t=1196500
Otherwise I good luck. Then skip CM10 and go directly to SlimRoms.
Found out what I did wrong. Followed the wrong guide, downloaded the wrong CWM.
My device is a Nexus S 4G, and I followed the guide for the Nexus S, and used the download link in that guide.
Making sure everything you use that says crespo anywhere reads "crespo4g"
So make sure that the CWM that you download is for crespo4g. Crespo will work, but not for ROMS that check the device name before installing (such as cyanogen)
Thanks for the help.

Problems with safestrap

So,
I spent the last days trying to learn how to port a rom to a new device,
so I could manage to compile a rom, doesn't matter witch to xoom 2 ME.
I've been trying to make a /device folder and extract the /vendor, out of the one from AOSP rom for
the motorola spyder device ( droid RAZR), especially because they have similar hardware.
So I finally got a .zip rom, made out of the ICS vanila source code, so then I could use the same kernel it already has.
even though I'm pretty sure it won't work pretty well, maybe it won't even boot.
But then I tryed to flash it over the safestrap, and it didn't flash I got the following message:
asser failed: getprop("ro.product.device") == "fleming" || getprop("ro.build.product") == "fleming"
error in /sdcard/full_fleming.zip (status 7)
I also tryed to flash a kernel I compiled, and then the original kernel of it repacked,
the kernels flashed alright, but then when I restarted the phone, the kernel was still the original one,
so it didn't actually flashed.
Please if anyone can give some help I'd be really glad!
Maybe the safestrap is not able to flash a kernel or a rom, maybe it's blocked or maybe I have do something espcial to pack a .zip for a safestrap.
Please help me.
by the way, the safestrap is the 3.12 from hashcode

[Q] Error installing Roms

I just achieved S-OFF yesterday via Facepalm and everything was fine until i tried to install a new rom. I get the same error with illusion or CM nightly and I may have done something wrong....idk. It says something about the bootloader. Here it is :
Installing update...
assert failed: getprop("ro. bootloader") == "2.15.4444" | | get prop("ro. boootloader") == "2.13.0000"
E: Error in /sdcard/ .....(my folders)..../cm-10.1-20130807-nightly-ville.zip
(Status 7)
Installation aborted.
I know they both have the 3.4 kernel but I didnt see anyone that actually couldnt install the rom. And in the PACman development thread it says the kernel isnt working only if you are on a lower hboot than 1.14, and i am exactly on 1.14. I dont know if this has anything to do with it....
Edit: right after i wrote this i flashed elementalx and now the phone reboots 1 time and then it stops at the white htc screen with the red sentences. Same thing for recovery, after few seconds the screen turns black and it reboots..

Categories

Resources