Database Users

[Q] aosp froyo for g1 dream stuck on g1 logo

Hello, I've built an aosp froyo rom for a rooted g1. I've extracted proprietary files from a cyanogen 6 rom and build process went fine. After installing the rom either through fastboot or recovery the phone won't boot. It's stuck on g1 logo and adb does not start.
I can remove the battery and start fastboot, so I can reinstall an old rom, but I cannot access recovery.
I would like to know what kind of problem I'm facing and how to bypass it.
I'm building aosp from froyo branch as full_dream-userdebug.
Can the proprietary drivers be the problem?
I'm using G1-radio-2_22_23_02 and HardSpl.
Is there a boot log I can access to have an Idea on what's going on?
Thanks.
Valerio

There were some kernel compatibility problems found with respect to the 0.95 series of SPLs. I suggest you upgrade to 1.33.2003. This is NOT the deathspl and you won't brick by installing it.
vale_arna84 said:
Hello, I've built an aosp froyo rom for a rooted g1. I've extracted proprietary files from a cyanogen 6 rom and build process went fine. After installing the rom either through fastboot or recovery the phone won't boot. It's stuck on g1 logo and adb does not start.
I can remove the battery and start fastboot, so I can reinstall an old rom, but I cannot access recovery.
I would like to know what kind of problem I'm facing and how to bypass it.
I'm building aosp from froyo branch as full_dream-userdebug.
Can the proprietary drivers be the problem?
I'm using G1-radio-2_22_23_02 and HardSpl.
Is there a boot log I can access to have an Idea on what's going on?
Thanks.
Valerio
Click to expand...
Click to collapse

lbcoder said:
There were some kernel compatibility problems found with respect to the 0.95 series of SPLs. I suggest you upgrade to 1.33.2003. This is NOT the deathspl and you won't brick by installing it.
Click to expand...
Click to collapse
It's true. I have an HBOOT-0-95.3000. I'll upgrade to the 1.33.2003. I'm glad this is a safe upgrade. I'll give a try and let you know.
Thanks.

I've just installed spl 1.33.2003. Now I'm trying to install aosp froyo build from recovery. I receive this error:
Installing Update:
assert failed: getprop("ro.bootloader") == "1.33.2004" ||
getprop("ro.bootloader") == "1.33.0004" ||
getprop("ro.bootloader") == "0.95.3000" ||
getprop("ro.bootloader") == "0.95.0000" ||
E:Error in /sdcard/full_dream-ota-eng.valerio.zip
(Status 7)
Installation aborted.
I've also tried to install the rom using fastboot. The result is the device stuck on g1 logo as before the spl upgrade.
Any suggestion is appreciated.
Valerio

You should use Firerat's cutom mtd-patch and fake your SPL (in my signature you can find a link to that thread).
Sent from my Htcclay's Superfly G1 BTX using XDA App

You should use Firerat's cutom mtd-patch and fake your SPL (in my signature you can find a link to that thread).
Click to expand...
Click to collapse
Sorry, but I can't find a precise guide on how to fake the spl following the links in your signature. Can you show me the right place?
Thanks

Put the following into the mtdpartmap file
mtd 90 2
spl 1.33.2005
especially the second line, then patch your recovery using Firerats recovery patcher.
(Klick on the link starting with MTD and you will be in the right thead)
Sent from my Htcclay's Superfly G1 BTX using XDA App

I've followed the instruction in Fierat's thread
But nothing changed. I've done the following steps:
download FR-recovery-v1.5.3-CustomMTD_S.zip and FR-boot-v1.5.3-CustomMTD_S.zip
create a mtdpartmap.txt with this lines:
mtd 90 2
spl 1.33.2005​
reboot into recovery
wipe cache + data
flash FR-recovery-v1.5.3-CustomMTD_S.zip
reboot to recovery
flash FR-boot-v1.5.3-CustomMTD_S.zip
reboot
flash my custom rom via recovery (fails the same way as described in a previous post) or via fastboot (device stuck on g1 logo)
Am I missing something?
Valerio

Did you read carefully?
You have to flash the boot-patcher after(!) you flashed the ROM, but before booting.
Sent from my Htcclay's Superfly G1 BTX using XDA App

I can't flash my froyo rom from recovery neither before nor after the boot-patcher. The error is always the one posted before.
I've also tried to use fastboot instead of recovery to flash the rom, but without success.

Where did you put your mtdpartmap file? It must be located in the root of your sdcard.
Please read the OP in Firerat's mtd-thread carefully and follow the instructions, then there will be no problem in flashing CM6 on your phone.
Sent from my Htcclay's Superfly G1 BTX using XDA App

The problem is that I'm not flashing a CM6 rom. I've just tried with CM6 and it worked.
My rom is a custom one built from froyo branch on aosp. Is there a way to compile the kernel telling it to accept a specific spl version?
Has anyone successfully built an aosp froyo for dream?
For the moment I'm enjoying CM6, but I need to use my own APIs, so I definitely need to flash my rom.
Maybe the best choice is to modify and compile CM6 code?

The boot-patcher is exactly doing that! But how big is your /system? Did you check wether 90MB will be sufficient? Probably you will need more?
Sent from my Htcclay's Superfly G1 BTX using XDA App

Here is the device partition layout.
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 47.7M 0 47.7M 0% /dev
tmpfs 47.7M 0 47.7M 0% /mnt/asec
/dev/block/mtdblock3 90.0M 75.7M 14.3M 84% /system
/dev/block/mtdblock5 117.8M 25.1M 92.7M 21% /data
/dev/block/loop0 4.0M 4.0M 0 100% /system/xbin
/dev/block/mtdblock5 117.8M 25.1M 92.7M 21% /cache
/dev/block/mtdblock4 2.0M 776.0K 1.2M 38% /dev/cache
/dev/block/vold/179:1
966.6M 106.8M 859.8M 11% /mnt/sdcard
/dev/block/vold/179:1
966.6M 106.8M 859.8M 11% /mnt/secure/asec​
I don't think aosp system is bigger than 90M. In fact the system folder inside my rom is 49.1M.

Your partition layout looks good so far. It seems that the mtd-patch is working, so flashing should not be a problem, but when you use the mtd-patch you have to flash the ROM from recovery, otherwise the modified partition layout is not known!

Yes, of course, I did it. In fact it worked for CM6 rom. The problem is with aosp froyo rom. Maybe the kernel is different? I've built the rom with the original kernel found on the froyo branch. I can try using a different one. Which kernel does CM6 for dream uses?
Thanks

vale_arna84 said:
Yes, of course, I did it. In fact it worked for CM6 rom. The problem is with aosp froyo rom. Maybe the kernel is different? I've built the rom with the original kernel found on the froyo branch. I can try using a different one. Which kernel does CM6 for dream uses?
Thanks
Click to expand...
Click to collapse
You have problems in flashing, don't you? While you are flashing, the kernel does not matter, except that boot.img is too big and does not fit into the boot partition. Most likely your updater-script is not correct and all your errors are due to that ... (only guessing).

Yes, you are right. My problem was in the updater-script. I've added
getprop("ro.bootloader") == "1.33.2005" ||​and I've successfully flashed the rom.
The problem is that the rom does not boot and I'm stuck on g1 logo.
The updater-script part related to bootloader (before adding 1.33.2005) was as follows:
assert(getprop("ro.bootloader") == "1.33.2004" ||
getprop("ro.bootloader") == "1.33.0004" ||
getprop("ro.bootloader") == "0.95.3000" ||
getprop("ro.bootloader") == "0.95.0000");​
Should I use a different bootloader?

I don't think, that using a different bootloader will help to solve your problem. Most likely the kernel itself has some problems. Could be a linking problem, a missing library, ... Did you try to logcat using adb while booting? If you are lucky, the kernel is crashing after the intialization of adb and you can locate the problem.
Sent from my Htcclay's Superfly G1 BTX using XDA App

Unfortunately adb does not start. I have no idea on what's going on. Probably nothing. I'll try to use a different kernel and let you know. Thanks

[KERNEL][OC] custom kernel for Motoroi rom + Dexter's rom

News:
fjfalcon has compiled kernel for Milestone XT720 roms.
Kernel booting instruction:
Here are the steps needed to boot custom boot.img(kernel). It is safe to do this way it will only boot the boot.img and not flash it.
Code:
adb reboot bootloader
Code:
fastboot boot boot.img
If your phone's rom is based on Dexter's rom download fjfalcon_xt720_boot.7z attachment
WARNING DO NOT FLASH THIS BOOT.IMG IN ANY WAY. THIS VERSION IS CONFIRMED TO WORK ON DEXTER'S ROM.
Changes:
Enabled swap
enabled ext2
enabled ext2
enabled ext4
If your phone's rom is based on Motoroi 2.2 rom download raser_motoroi_boot.7z attachment
WARNING DO NOT FLASH THIS KERNEL IN ANY WAY. THIS VERSION IS CONFIRMED TO WORK ON STKT_N_79.33.50R.
Changes:
Overclocked to 1GHz(stock voltage)
ThumbEE
GCC 4.4.3
Added ext3
Added ext4
cpu governer enabled: powersave conservative
Thanks:
fjfalcon
XVilka
yakk
Skrilax_CZ
Mioze7Ae
to be continued...

reserved...

is there any good howto how to create boot.img?

fjfalcon said:
is there any good howto how to create boot.img?
Click to expand...
Click to collapse
check this
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
1. download kernel sources from motorola
2. check _READ.txt in downloaded sources
if you'll further have questions please ask

Mine first boot.img
Powersave governor
ext2
ext3
ext4
swap
This is my first attemp of 2.6.29.
So, Resar, where can i get fastboot for linux?
Already founded...
Like always make fastboot in copy of android git comes with answer =)
Damn =(
Don't booted.
So, i get zImage from /home/fjfalcon/mydroid/out/target/pr/generic/obj/PARTITIONS/kernel_intermediates/build/arch/arm/boot
and tryed to mkbootimg with ramdisk from Dexter 1.3(that pulled by cat /dev/mtd/mtd4 > mtd.img) and splited by perl splitter.
Damn =(

fjfalcon said:
Powersave governor
ext2
ext3
ext4
swap
This is my first attemp of 2.6.29.
So, Resar, where can i get fastboot for linux?
Already founded...
Like always make fastboot in copy of android git comes with answer =)
Damn =(
Don't booted.
So, i get zImage from /home/fjfalcon/mydroid/out/target/pr/generic/obj/PARTITIONS/kernel_intermediates/build/arch/arm/boot
and tryed to mkbootimg with ramdisk from Dexter 1.3(that pulled by cat /dev/mtd/mtd4 > mtd.img) and splited by perl splitter.
Damn =(
Click to expand...
Click to collapse
Congrats, Nice done Your kernel boots fine on motoroi 2.2.1 rom (it boots to android then after 1 minute reboots. It seems ramdisk problem). You should try to build from milestone xt720 sources, But as I remember there is something broken in that sources

Additionally you can overclock the cpu by changing values S600M, S550M, S500M, S250M, S125M in arch/arm/mach-omap2/omap3-opp.h

So, what can we do with ramdisk to make it work normaly?

The problem is the kernel not the ramdisk. You have made a boot.img from motoroi kernel zImage and the ramdisk of Dexter's rom which is based on Milestone xt720 rom. We can try to compile kernel from Milestone xt720 sources. If it won't boot then We'll have to make some changes in kernel sources. But right now I don't know what changes should be done.
Now I'm trying to patch kernel to 2.6.38 version.

Thanks, but how do i know it wrok?

just do
Code:
adb reboot bootloader
then wait till the phone reboots to bootloader
Code:
fastboot boot boot.img
now it will show the M logo for about 20 seconds after that animation starts.
Run SetCPU application, go to Info and under Kernel you'll find info about running kernel, and also I have made an overclocked version kernel and will update the first post as sooon as possible.
You must run motoroi 2.2 rom to boot my kernel, it doesn't work on Dexter's 2.2 rom.

Ok, now will try to compile kernel from 2.1 source.
Thank you, resar.

fjfalcon said:
Ok, now will try to compile kernel from 2.1 source.
Thank you, resar.
Click to expand...
Click to collapse
How is going your work. have you compiled ms xt720 kernel?

Yesterday stoped on kernel error.
Today when i will go to home... that about 5 or 6 gmt will try to fix it.

Just booted with my kernel!!!! =)
Omg, IT REALLY WORKS! =)
Enabled swap... enabled ext2, ext3, ext4...
Mine new Kernel on 2.6.29 from 2.1 source
Works with Dexter's 1.3!!!
Wow =)
Already works fine about 20 min's.
It's very good news! =)
Is there anyway to always boot fastboot with my kernel when phone loading?

fjfalcon said:
Just booted with my kernel!!!! =)
Omg, IT REALLY WORKS! =)
Enabled swap... enabled ext2, ext3, ext4...
Mine new Kernel on 2.6.29 from 2.1 source
Works with Dexter's 1.3!!!
Wow =)
Already works fine about 20 min's.
It's very good news! =)
Is there anyway to always boot fastboot with my kernel when phone loading?
Click to expand...
Click to collapse
thats great news, congrats next step is the patching of kernel to upper versions))

so why cant we flash these boot images if they boot?

easye420 said:
so why cant we flash these boot images if they boot?
Click to expand...
Click to collapse
The boot.img are not signed with Motorola's bootloader signing key. If you flash it, the bootloader signature validation will fail. Under a normal boot if the signature validation fails, the bootloader will refuse to load boot.img and will instead drop you into Motorola recovery. fastboot bypasses the Motorola signature check, but it requires loading boot.img from USB.

stupid motorola has to ruin everything.

fjfalcon said:
Is there anyway to always boot fastboot with my kernel when phone loading?
Click to expand...
Click to collapse
It seems that there is no way to do that. The only thing you can do is automatically boot to fastboot. But then you'll need a PC to boot boot.img from from fastboot.

[I9020T][REF] All OTA and Available Full ROM Packages

---------------------------------------------------------------------------
I HAVE CEASED UPDATING THIS THEAD.
The old information contained below will remain for posterity, but will no longer be updated. From this point forward, all updates to this information will be found at http://www.randomphantasmagoria.com/firmware/nexus-s
---------------------------------------------------------------------------
Below is a list of all available OTA and full ROM packages for the Nexus S, model I9020T.
THIS IS FOR I9020T ONLY. IF YOU HAVE ANOTHER VARIANT, PLEASE FIND THE THREAD FOR YOUR VARIANT.
Typical disclaimer where I tell you that all of this stuff is at your own risk and I'm not responsible if you mess up your phone, yadda yadda.
These updates are 100% stock and are NOT rooted.
HOW TO FLASH
I'm not giving instructions on how to flash ZIP files or fastboot images. If you don't know how to do that, you probably shouldn't be looking for stuff in this thread. There are plenty of threads on how to flash fastboot images or how to flash zips through recovery. Do a little reading before proceeding.
The recovery-flashable full ROM packages will only flash if your phone has no ROM, any custom ROM, or a stock ROM that's older than the version you're trying to flash. For instance, the 2.3.4 full ROM package will flash over the stock 2.3.1 ROM, but not over the stock 2.3.6 ROM.
With fastboot images, you can flash any version over any other version.
WHAT HAPPENS IF I GET AN ERROR WHILE FLASHING?
If you get an error flashing a recovery-flashable full ROM package, it means that you are running a stock ROM that's newer than the version you're trying to flash. If you're trying to downgrade, then you must install ClockworkMod recovery, then wipe system, boot, data, cache, and Dalvik cache. You will then be able to flash the older version. Optionally, you can also flash fastboot images of a version older than the version you're trying to flash.
If you get an error flashing an incremental update, it means one of four things. Either you don't have an I9020T, you aren't running a stock ROM, you have changed something with your stock ROM (this includes build.prop changes, radio or bootloader changes as well), or you're running Android 4.X and trying to update manually. These incremental updates only work if you are running a completely, perfectly stock ROM exactly the way Google provides it, with the right radio and the right bootloader. There are no exceptions to this rule. Furthermore, Android 4.X ROMs can no longer be updated manually in stock recovery. See below.
A NOTE ABOUT ANDROID 4.X OTAs
Beginning with Ice Cream Sandwich, Google has made a change to stock recovery that prevents you from flashing future OTA updates manually. Instead you are now required to wait for the OTA notification on your phone and then tap "Reboot and Install."
If this pisses you off, you have the option of unlocking your bootloader, installing either a stock Gingerbread recovery or ClockworkMod recovery, and then flashing the OTA updates manually.
LATEST VERSION
The latest Android version available for I9020T is Ice Cream Sandwich version 4.0.4, build IMM76D.
BUILD REFERENCE
GRH55 - Android 2.3
GRH78 - Android 2.3.1
GRH78C - Android 2.3.2
GRI40 - Android 2.3.3
GRI54 - Android 2.3.3 (shipped on some non-USA I9020T devices)
GRJ22 - Android 2.3.4
GRK39F - Android 2.3.6
IML74K - Android 4.0.3
IMM76D - Android 4.0.4
FULL ROMS
FASTBOOT IMAGES
If you're comfortable with fastboot, you can flash these images to return your phone back to raw stock. FLASHING FASTBOOT IMAGES WILL ERASE ALL OF YOUR PHONE'S DATA AND WILL RETURN YOU TO A FACTORY STOCK, UNROOTED STATE.
Android 2.3.1/GRH78/XXJK8 Radio/JK1 Bootloader
Official factory fastboot images, must be flashed using fastboot on an unlocked bootloader. Contains recovery, radio, and bootloader.
THESE IMAGES MUST BE FLASHED USING BOOTLOADER VERSIONS I9020XXJK1 OR I9020XXKA3
Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader
Official factory fastboot images, must be flashed using fastboot on an unlocked bootloader. Contains recovery, radio, and bootloader.
THESE IMAGES MUST BE FLASHED USING BOOTLOADER VERSIONS I9020XXJK1, I9020XXKA3, OR I9020XXKL1
Android 2.3.3/GRI54/XXKB3 Radio/KA3 Bootloader
Official factory fastboot images, must be flashed using fastboot on an unlocked bootloader. Contains recovery, radio, and bootloader.
THESE IMAGES MUST BE FLASHED USING BOOTLOADER VERSIONS I9020XXJK1, I9020XXKA3, OR I9020XXKL1
Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader
Official factory fastboot images, must be flashed using fastboot on an unlocked bootloader. Contains recovery, radio, and bootloader.
THESE IMAGES MUST BE FLASHED USING BOOTLOADER VERSIONS I9020XXJK1, I9020XXKA3, or I9020XXKL1
Android 4.0.4/IMM76D/XXKI1 Radio/KL1 Bootloader
Official factory fastboot images, must be flashed using fastboot on an unlocked bootloader. Contains recovery, radio, and bootloader.
THESE IMAGES MUST BE FLASHED USING BOOTLOADER VERSIONS I9020XXJK1, I9020XXKA3, OR I9020XXKL1
RECOVERY-FLASHABLE ROMS
Android 2.3/GRH55/XXJK8 Radio/JK1 Bootloader
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Android 2.3.1/GRH78/XXJK8 Radio/JK1 Bootloader
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Android 2.3.2/GRH78C/XXJK8 Radio/JK1 Bootloader
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 2.3.3/GRI54/XXKB3 Radio/KA3 Bootloader
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 4.0.3/IML74K/XXKI1 Radio/KL1 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 4.0.4/IMM76D/XXKI1 Radio/KL1 Bootloader
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Courtesy of XDA forum member kibmcz.
INCREMENTAL UPDATES
The links provided here are to Google's official update package for each version. Sometimes Google provides a small incremental update package for upgrading between versions, other times they just provide full ROM packages for bigger version upgrades. For instance, Google pushed a small incremental update to upgrade from 2.3.4 to 2.3.6. If your phone was running 2.3.1, there is no 2.3.1 to 2.3.6 incremental update, so Google would push the 2.3.6 full ROM package.
If you don't see an upgrade path from your version to your desired version, it means you need to use a full ROM package above instead.
Android 2.3 (Build GRH55/XXJK8 Radio/JK1 Bootloader)
2.3 -> 2.3.1
Android 2.3.1 (Build GRH78/XXJK8 Radio/JK1 Bootloader)
2.3.1 -> 2.3.2
2.3.1 -> 2.3.3 (GRI40)
2.3.1 -> 4.0.4
Android 2.3.2 (Build GRH78C/XXJK8 Radio/JK1 Bootloader)
2.3.2 -> 2.3.3 (GRI40)
2.3.2 -> 2.3.4
Android 2.3.3 (Build GRI40/XXKB1 Radio/KA3 Bootloader)
2.3.3 (GRI40) -> 2.3.4
Android 2.3.3 (Build GRI54/XXKB3 Radio/KA3 Bootloader)
Neither of these following OTA updates actually work. Both of them require an unknown radio, and will fail if you try to flash them on a phone running 2.3.3/GRI54 with the XXKB3 baseband. The 2.3.3->2.3.4 update has since been pulled by Google and the link is only provided here for posterity and reference. The only way to properly update 2.3.3/GRI54 is to flash a full ROM over it.
2.3.3 (GRI54) -> 2.3.4 (Update requires an unknown radio and will NOT update build GRI54 with XXKB3 radio.)
2.3.3 (GRI54) -> 4.0.4 (Update requires an unknown radio and will NOT update build GRI54 with XXKB3 radio.)
Android 2.3.4 (Build GRJ22/XXKD1 Radio/KA3 Bootloader)
2.3.4 -> 2.3.6
2.3.4 -> 4.0.4
Android 2.3.6 (Build GRK39F/XXKF1 Radio/KA3 Bootloader)
2.3.6 -> 4.0.3
2.3.6 -> 4.0.4
Android 4.0.3 (Build IML74K/XXKI1 Radio/KL1 Bootloader)
4.0.3 -> 4.0.4

Is There An Official Repository For These ROM Packages?
I am from the west coast of the US and received the OTA ICS update on my Nexus S. I have been waiting for this update just as many of us but I was concerned about the battery issues the update caused for other users... finally I applied the update.
My battery with moderate usage lasted about two days (applications installed: Orbot, Firefox, Skype) with Gingerbread latest version. I was very satisfied with the performance of the device. After the upgrade to ICS 4.0.3 my battery life went to 9 hours at most.
I have read many forums on the net but none give a definitive explanation on the issue. Finally I found one that explained some known CPU bug.
I decided to downgrade to Gingerbread but could not find the official stock ROM.
Thank you very much for posting them.
Is there an official repository for these versions?

The explanation of what each model variant is (eg. I9020T, AWS/2100, T-mobile, Windmobile, Mobilicity...) is missing from the main and sub thread.

Updated from 2.3.4 Gingerbread to ICS, everything is running smooth except the android market won't work over 3G. (works fine with a wifi connection) Any suggestions on what might be causing the problem?

Try clearing cache and dalvik.

Is anyone experiencing issues on the Build GRK39F/XXKF1 Radio for ICS? I'm especially interested in those who use WIND mobile.

I've been told that it's usually a good idea to run the right radio paired with the right ROM. Is there some reason why you want to run XXKF1 with IML74K?

oldblue910 said:
I've been told that it's usually a good idea to run the right radio paired with the right ROM. Is there some reason why you want to run XXKF1 with IML74K?
Click to expand...
Click to collapse
I'm not sure if your comment was directed towards me, but I thought by matching the Build Number, I could have a nice upgrade. I can't attach images, but my information are as follows:
Android Version: 2.3.6
Baseband Version: I9020XXKF1
Build Number: GRK39F
I'm also not rooted.

Also, check Market settings. There is an "Update over Wi-Fi only" checkbox. I don't remember if 2.3 had that or not.

sysadmn said:
Also, check Market settings. There is an "Update over Wi-Fi only" checkbox. I don't remember if 2.3 had that or not.
Click to expand...
Click to collapse
It comes with market 3.4.4
Sent from my ice cream powered Nexus S

@mrjimyjohn
To fix the 3G Market downloads problem on Mobilicity, go to Settings -> Wireless -> Mobile Networks -> Access Point Names.
Click on the MOWAP and MOMMS entries and delete anything that’s in the proxy field for each one.
You may need to reboot after doing this to see a change.

Hi,
ia hve cyanogen 7 ver. 2.3.7
and the baseband is I9020XXKD1.
can i flash stock 2.3.6 and then flash ics with the posted links?

eben0 said:
Hi,
ia hve cyanogen 7 ver. 2.3.7
and the baseband is I9020XXKD1.
can i flash stock 2.3.6 and then flash ics with the posted links?
Click to expand...
Click to collapse
Yes, or you could just flash full 4.0.3 rom if you wanted
Sent from my ice cream powered Nexus S

so.. can i flash the stock 4.0.3 via the recovery without going back to stock 2.3.6 ?

eben0 said:
so.. can i flash the stock 4.0.3 via the recovery without going back to stock 2.3.6 ?
Click to expand...
Click to collapse
Yes, but do a full wipe first
Sent from my ice cream powered Nexus S

thx a lot update went flawlessly, the interface looks awesome.

Hi I have a nexus s i9020. is it different from i9020T or i9020A? Which one should I use for my device?

jkyfrm said:
Hi I have a nexus s i9020. is it different from i9020T or i9020A? Which one should I use for my device?
Click to expand...
Click to collapse
If it doesn't have a A (check behind the battery), then it is a i9020T. They just use the T & A to distinguish in the US between the T-Mobile and AT&T versions since they support different bands but the T is implied unless it is the A version.

Could you give me a few pointers please....
I bought my google nexus s from carphone warehouse and its on the vodafone network in the UK.
The details from the phone are:
Android version 2.3.6
Baseband version I9020XXKF1
Kernel version 2.6.35.7-gf5f63ef [email protected] #1
Build number GRK39F
My phone has not been rooted, and is completely stock (apart for the apps ive installed). The only updates that have been applied are those that come OTA. Im doing this because Vodafone UK seem to have no interest in updating the nexus s with the latest ICS.
From looking at these threads, I think this thread has the correct software to download and install on the phone, so I downloaded the incremental update 2.3.6 > 4.0.3 - firstly could you confirm that this is the correct rom ?
So then I renamed the file to update.zip, and copied it onto the root of the sd card.
I then powered off the phone and turned it back on whilst holding the power button and volume up to get to the bootloader.
I selected recovery and then phone reboots and shows the google logo for a second or two, then a box being unpacked for a second, and then an exclamation mark with a droid underneath it.
Could someone please give me some pointers as to what Im doing wrong here ? If its a stock update, then I dont think I have to unlock the bootloader.
I can then pull the battery and it will reboot as normal.
Thanks in advance.

markkeny said:
I bought my google nexus s from carphone warehouse and its on the vodafone network in the UK.
The details from the phone are:
Android version 2.3.6
Baseband version I9020XXKF1
Kernel version 2.6.35.7-gf5f63ef [email protected] #1
Build number GRK39F
My phone has not been rooted, and is completely stock (apart for the apps ive installed). The only updates that have been applied are those that come OTA. Im doing this because Vodafone UK seem to have no interest in updating the nexus s with the latest ICS.
From looking at these threads, I think this thread has the correct software to download and install on the phone, so I downloaded the incremental update 2.3.6 > 4.0.3 - firstly could you confirm that this is the correct rom ?
So then I renamed the file to update.zip, and copied it onto the root of the sd card.
I then powered off the phone and turned it back on whilst holding the power button and volume up to get to the bootloader.
I selected recovery and then phone reboots and shows the google logo for a second or two, then a box being unpacked for a second, and then an exclamation mark with a droid underneath it.
Could someone please give me some pointers as to what Im doing wrong here ? If its a stock update, then I dont think I have to unlock the bootloader.
I can then pull the battery and it will reboot as normal.
Thanks in advance.
Click to expand...
Click to collapse
Once you choose recovery hold volume down and tap power once the Droid pops up, then it should enter, oh and fyi our updates come from Google directly, not carries
Sent from my ice cream powered Nexus S

Kernel Fix and Kernel Repo...

Fix to: Phone not booting... (after non-stock rom install / switching to stock based rom.)
Zip Method Currently Discontinued. Learn how to fast boot a kernel below. ​
Scenario: (ADB Sideload Install) If you install a kernel, lets say it was CyanogenMod 10's kernel, then you do not wipe the boot.img, but then you flash a "stock-rom" based rom, Your phone will not boot, this is because the kernel is not compatible. Your screen will turn gray and hold... To fix this download your roms kernel (I scripted and put in an individual, CLOCKWORKMOD-ONLY flashable zip.) Or you can put your device into AP Fastboot mode and type the command "Fastboot Flash Boot C:/Location-of-boot.img" Boot image can be found bellow as an alternative.​
Kernel Repository​Flash-able zip form...​- CyanogenMod 10.0 (Eprinter) - Corresponding Thread - status: (in repo)
- CyanogenMod 10.1 (Eprinter) - Corresponding Thread - status: (in repo)
- CyanogenMod 10.0 (Hashcode) - Corresponding Thread - status: (in repo)
- CyanogenMod 10.1 (Hashcode) - Corresponding Thread - status: (in repo)
- Stock 4.1.1/4.1.2 (Motorola) - Manufacture & Developer Website - status: (uploading)
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Credit...​
Kernel Credit: Hashcode; Eprinter; Motorola; Google; CyanogenMod Team.
Scripted Zip Credit: Me (Codex01).
META-INF Script: Me (Codex01).
Enjoy.

codex01 said:
fix to: Phone not booting... (after non-stock rom install / switching to stock based rom.)
diy: Download "blankboot.zip" (in attachments section) ; place your roms boot.img in the root of the zip.​
scenario: (adb sideload install) if you install a kernel, lets say it was cyanogenmod 10's kernel, then you do not wipe the boot.img, but then you flash a "stock-rom" based rom, your phone will not boot, this is because the kernel is not compatible. Your screen will turn gray and hold... To fix this download your roms kernel (i scripted and put in an individual, clockworkmod-only flashable zip.) or you can put your device into ap fastboot mode and type the command "fastboot flash boot c:/location-of-boot.img" boot image can be found bellow as an alternative.​
kernel repository​flash-able zip form...​- cyanogenmod 10.0 (eprinter) - corresponding thread - status: (uploading)
- cyanogenmod 10.1 (eprinter) - corresponding thread - status: (uploading)
- cyanogenmod 10.0 (hashcode) - corresponding thread - status: (uploading)
- cyanogenmod 10.1 (hashcode) - corresponding thread - status: (uploading)
- stock 4.1.1/4.1.2 (motorola) - manufacture & developer website - status: (uploading)
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
credit...​
kernel credit: Hashcode; eprinter; motorola; google; cyanogenmod team.
Scripted zip credit: Me (codex01).
Meta-inf script: Me (codex01).
Enjoy.
Click to expand...
Click to collapse
i looked at your updater script. Are you sure its correct? It has references to "omap" and this is quallcom chipset. Im just curious, not saying its wrong.

mikeyinid said:
i looked at your updater script. Are you sure its correct? It has references to "omap" and this is quallcom chipset. Im just curious, not saying its wrong.
Click to expand...
Click to collapse
I didn't get to test it, because this was the issue with my phone. I posted this at work and didn't bring my razr hd, I brought my iphone instead because this happened to me and just started it. I dev for many phones so I researched how to do it so I could get it done before I got home. (I tried to make it universal.). I guess I uploaded the wrong one. My bad. It will be fixed. I'm gonna test it out now.

codex01 said:
i didn't get to test it, because this was the issue with my phone. I posted this at work and didn't bring my razr hd, i brought my iphone instead because this happened to me and just started it. I dev for many phones so i researched how to do it so i could get it done before i got home. (i tried to make it universal.). I guess i uploaded the wrong one. My bad. It will be fixed. I'm gonna test it out now.
Click to expand...
Click to collapse
no worries. Im not really sure why i even looked.

I think your updater script should look like this, and you *might* not even have to mount system:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.100000, 0);
unmount("/system");

not work

I know... It says discontinued.The zip method doesn't work you have to put your phone in fast boot and write fastboot flash boot C:/direcory-to-boot.IMG as it is clearly stated, above. Read everything next time.
Sent from my MB886 using xda app-developers app

Codex01 said:
I know... It says discontinued.The zip method doesn't work you have to put your phone in fast boot and write fastboot flash boot C:/direcory-to-boot.IMG as it is clearly stated, above. Read everything next time.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Whoa. What's with the attitude? Are you talking to me? I was just trying to help. And what I posted will work.
Sent from my Galaxy Nexus using xda premium

Lol. No the other guy.
Sent from my MB886 using xda app-developers app

[Q] Upgrade Bootloader 3.01 to 1.8 with 1.7.3 Recov and JB ROM

Subject: How do I Upgrade Bootloader 3.01 to v8, with 1.7.3 recovery and a JB Rom installed ?
My A500 is currently configured as follows:
Bootloader Version 3.01
Recovery Version Thor 1.7.3
ROM Version JB-MR1(4.2) device building - v11
I would like to upgrade to the current Bootloader (from v3.01 to v8) so that I can get multi-boot working. I have followed the various posts to obtain the CPUID, but without success. As a result I am stuck at the first step without a valid SBK......
In the Recovery Screen, a CPU UUID starting with 0x037c...... with a length of 18 characters is shown. If I do a full backup from Recovery, and then have a look at the "uid.txt" file under the CWM Backup directory, it contains the same 18 character alpha numeric string.
When I tried the blackthund3r ATX flash tool's "A500Manager" it returned blank values for CPUID and Recovery Version. If I connect to the device using "adb devices" the serial number reported is an 11 digit number.
One of the guides from this forum (forgotten which guide now - I've looked at so many) suggested that maybe having a JB Rom on the old version of the bootloader was causing the problems and that a downgrade to a Honeycomb Rom was necessary. So after suitable backups, I installed the Lightspeed 2.1 Rooted Honeycomb ROM. It didn't change the way that the CPUIDs are being reported. I've since restored back to the JB-MR1(4.2) ROM.
Can someone please advise me:
1) What should the correct CPUID look like - i.e. how many characters, and alpha/numeric, or numeric only?
2) What process should I use in these circumstances to upgrade the Bootloader ?
Regards,
RoyG (Bocean)