Related
Hy guys! This is my first post because I've always found a solution in this great fourm for my previous issues
Now, after searching the whole fourm without finding a solution, I've to open a new thread, hoping you could help me
I've upgraded my Dream from JF ADP1.1 to JF RC33 following this [1]. These are the steps I've followed:
-placed the RC33 image [2] in the sd root, after renaming it to update.zip
-boot up the ADP1.1 into recovery mode
-perform a wipe and reboot into recovery mode again
-perform the update and reboot
-activate the phone with my google account via EDGE
-placed the radio update [3] in the sd root, after removing the old update.zip and renaming it to update.zip
-reboot into recovery mode and perform the update.
Everything seems to went fine. Into recovery mode the phone verifies and extracts the image and then asks to press HOME+BACK to reboot. After pressing HOME+BACK the system flashes the radio image and then reboots showing the image with the arrow and the chip. After this image the phone boots again into recovery mode. At this point I've pressed home+back to reboot again and now the dream boots in standard mode, loading the OS.
Everything works (EDGE, SMS, CALLS, WIFI etc.) but, when checking the settings, the build number is ok (*RC33*) but the baseband has not been updated. In fact the version is still the old one *22_12.29
Same thing if I check the baseband version via the SPL (HardSPL)
Any help much appreciated!
Thank you!
Simone "simoneinweb" Mainardi
[1] http://forum.xda-developers.com/showthread.php?t=475381
[2]http://jf.odiness.com/v1.41/JFv1.41_RC33.zip
[3]http://jf.odiness.com/RC33/RC33radio_update_testkeys.zip
I've also tried to reflash the ADP1.1 and then apply the update.zip containing the radio update but baseband version is still the old.
Please help...
Hi!
I did the same thing with my ADP, but I had previously flashed it with JF RC30 1.41. I updated to RC33 with no problem, and then I applied the radio patch. My phone got stuck in the boot logo and I had to do a wipe and reflash with RC33 to get it working. I applied the radio patch and everything was OK, but the baseband is still in the same old version.
Maybe an specfic ADP issue?
I updated from ADP 1.1 to RC33 and flashed radio, and the baseband confirms the update was successful.
How do you flash the radio? I applied JF RC33 update and he mentioned we have to flash the new basebad separately, I've never done that before
Are you using an actual ADP1 or just a G1 flashed with the ADP firmware. I haven't tried it on my ADP1 as I have no real need for RC33 but I believe if you are on a real ADP1 it won't actually flash the radio with the update from a normal G1 because of the unlocked radio in the ADP1. Just my $.02.
Simone: Can you verify the MD5 of the radio update after you have copied it to your microsd? Should be cf8714d273fb0274574d9e3831e11fdd.
Ok this is my problem after I installed jf rc33 and the radio. Yes I did a wipe from my jf adp1.1 installed jf rc33 then did the radio update but now I get no internet on my g1. I went into. Settings > about and it says that the connection is EDGE with no data connection. The g1 its self almost closes the edge as soon as I receive a mms as there is no E in my status bar. Also I live in a market that doesn't have 3g yet so I have tried the settings use 2g only and without. Any ideas what the problem could be? I assume it is the radio but can I reflash an old radio without doing a wipe? Or if I need to wipe and go back to jf rc30 or adp1m1 do I need to flash back to rc29?
You can flash an old radio without a wipe. Replace the radio.img inside the radio updater with the one from signed-kila-ota-116143-prereq.TC4-RC19+RC28+RC29.zip and resign the entire zip file with SignApk.
ok before i do this what else could the problem be if any? causing no internet?
I was with rc30 JF , and then i moved to rc33 , then flashed the radio. What is the number supposed to be after the update or before? Mine right now is
_1.22.14.11
Is this right after i flashed the radio? or this is the old one? no idea..never paid attention to the baseband version.
jojo_angelov said:
I was with rc30 JF , and then i moved to rc33 , then flashed the radio. What is the number supposed to be after the update or before? Mine right now is
_1.22.14.11
Is this right after i flashed the radio? or this is the old one? no idea..never paid attention to the baseband version.
Click to expand...
Click to collapse
i have the same radio baseband version after i did my update... but when mine went into a loop i hit alt x and typed reboot and my g1 booted normally.
another note does anybody have a signed update of the old radio they could post. i have not gotten into signing apks yet and when i did a search for sign.apk i got stercsons thread but i didnt setup the sdk yet my desktop is very limited on space.
Here's the radio from RC30 signed with test keys. (ver 1.22.12.28)
http://drop.io/rc30radio
9817b38ff5797370e3270e40cca36e15 *rc30_radio_testkey_assert-dream.zip
thanks jashsu . Since the version is different than rc30 you just gave, i suppose the radio update was a success. What does that update do? boost 3g or?
How do you flash the radio? I applied JF RC33 update and he mentioned we have to flash the new basebad separately, I've never done that before
Click to expand...
Click to collapse
I've flashed the radio separately, as described in http://forum.xda-developers.com/showthread.php?t=475381
Are you using an actual ADP1 or just a G1 flashed with the ADP firmware.
Click to expand...
Click to collapse
I'm using a G1 flashed with the ADP image. But I've also tried to flash it back (successfully) to jf RC30 and then perform the radio update but without success.
Can you verify the MD5 of the radio update after you have copied it to your microsd?
Click to expand...
Click to collapse
I always verify the checksum before flashing everything in the ROM. I trust in the reliable data transfer service offered by TCP but in this cases an md5sum is a gooood thing!
Hello,
I have updated to JF 1.5 and its working great. But when I boot up to make a nandroid backup, it says "Android system recovery utility Build: JFv1.41"
When I press Alt+B to backup I get an error saying:
Error running nandroid backup. Backup not performed.
Any ideas?
I guess you didn't bother to read JF's notes about not having a modified recovery based on 1.5 yet. Anyway, recovery is versioned independently of the main system software, like the radio.
jashsu said:
I guess you didn't bother to read JF's notes about not having a modified recovery based on 1.5 yet. Anyway, recovery is versioned independently of the main system software, like the radio.
Click to expand...
Click to collapse
I did read it, I am totally fried :/
It took me 4 hours to recover my phone earlier and now studying for my 5 final exams this week, so I totally forgot about his post regarding the recovery image
Thanks for the reminder
You should update your recovery though. The latest JF recovery is v1.42. The link in JF's ADP1.5 post links to a v1.43 recovery-only updater, but it is v1.42 (confusingly named 1.43 because it was bundled with the JF1.43 system software updates). It fixes a recovery 1.41 bug where adb didnt run with escalated privileges.
I'm creating this thread in hopes no one who owns a MyTouch, in America, on T-Mobile with a perfected SPL doesn't have to go through the brain numbing process I've just adventured through over the past week.
Special thanks to Amon_RA and Radix999 who have compiled an impressive set of information on this topic. I would have been totally lost without their contributions to this forum.
Setup:
You'll need a brand-spanking-new MyTouch 3G, 1.6 updated, un-modded, perfected SPL [Mine was: HBOOT-1.33.0006 (SAPP30000)]. To find out if your SPL is perfected power your phone off: press the vol button down > hit the power button > compare the info listed in fastboot (white screen with three skateboarding Androids) to Amon_RA's list of SPL's. If you have done anything to your phone before attempting this process go consult someone who knows wtf they are doing. I don't, but I rather tell people how this went down for me.
How I Rooted my MT3G:
1. Get your phone back to 1.5 cupcake by whatever means necessary. I used these directions: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
2. Follow these steps to root your device: http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/. When you are done with this process you should have Amon_RA's recovery and boot loader all setup. This will allow you to format your SD card to whatever file system you want, flash roms, do nandroid backups, the works.
3. Go to Amon_RA's thread about SPL's: http://forum.xda-developers.com/showthread.php?t=529019
and download a Engineering SPL for your phone. (Engineering SPL 1.33.2004 by Crios worked for me)
4. Edit the SPL file name to "update.zip"
5. Load the SPL to the root of your SD card.
6. Load up RA's boot loader. (Power + Home)
7. Wipe / Clear from the boot loader menu.
8. Apply update.zip from the boot loader menu.
9. Wait for the phone to reboot, all kinds of whacky **** will happen, don't mess with the device, etc. Eventually you should reboot into recovery mode. Whatever you do - figure out how to get to recovery mode.
10. Wipe / Clear from the boot loader menu.
11. Format the SD VIA boot loader.
12. Load a new / favorite ROM onto the SD. (I use Blueberry Hero)
13. Install the Rom VIA boot loader.
14. Crack open a beer.
No gold card, fastbook, no crazy 40 step process. There may be some security issues or something involved with this process. Whatever the case, whatever the politics are between XDA/unlockr - this WORKED for me from a STOCK 1.6 device.
With a little bit of reading you should either have turned your phone into a 400$ brick or a happy little Hero pumping Android phone.
Cheers.
donut
if you have donut 1.6, the one click root doesnt work. You may have had the .006 SPL but in Android 1.6 the exploit that one click used is corrected.
byt3b0mb said:
if you have donut 1.6, the one click root doesnt work. You may have had the .006 SPL but in Android 1.6 the exploit that one click used is corrected.
Click to expand...
Click to collapse
From 1.6 - unlockr explains in detail how to get back to 1.5 in the link listed above.
Check http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/ for details.
Does this allow you to flash hero roms? I have bypassed perfect spl and cant flash hero roms (boot image error)
bonesy said:
Does this allow you to flash hero roms? I have bypassed perfect spl and cant flash hero roms (boot image error)
Click to expand...
Click to collapse
Whats the size of the hero boot.img?
bonesy said:
Does this allow you to flash hero roms? I have bypassed perfect spl and cant flash hero roms (boot image error)
Click to expand...
Click to collapse
I'm able to load and run blueberry_full_V05 (http://forum.xda-developers.com/showthread.php?t=562071) with no issues.
Interface is a little wonky with his custom buttons... but it's faster than Max's Hero rom for me.
The key for me is no following anyones directions. I just load the ROM onto my properly formatted SD (done via boot loader) > Install the .zip file via boot loader. Done.
Note: Just remember to download the right version of the rom. (A or B)
what do you mean by "Wipe / Clear from the boot loader menu"?
is it select the "wipe data/factory reset? or "wipe sd:..."?
ashyou said:
what do you mean by "Wipe / Clear from the boot loader menu"?
is it select the "wipe data/factory reset? or "wipe sd:..."?
Click to expand...
Click to collapse
What he means is data wipe from the options in the boot loader before you update in that section.
I used these procedures and I am now running Hero Rom. thanks man.
so what's the point of doing this? My HBOOT is 1.33.0006 same as lowrez but i've been able to run roms with no problem. sorry for the noob ques.
Confirmed the update.zip method.
This worked on my Mytouch which was previously rooted but running a perfected spl not allowing fastboot operations. SPL was changed to 004 and Dwang's ROM is working fine with Amon_Ra's 1.2.3 recovery.
Good work dude.
lowrez01 said:
I'm creating this thread in hopes no one who owns a MyTouch, in America, on T-Mobile with a perfected SPL doesn't have to go through the brain numbing process I've just adventured through over the past week.
Special thanks to Amon_RA and Radix999 who have compiled an impressive set of information on this topic. I would have been totally lost without their contributions to this forum.
Setup:
You'll need a brand-spanking-new MyTouch 3G, 1.6 updated, un-modded, perfected SPL [Mine was: HBOOT-1.33.0006 (SAPP30000)]. To find out if your SPL is perfected power your phone off: press the vol button down > hit the power button > compare the info listed in fastboot (white screen with three skateboarding Androids) to Amon_RA's list of SPL's. If you have done anything to your phone before attempting this process go consult someone who knows wtf they are doing. I don't, but I rather tell people how this went down for me.
How I Rooted my MT3G:
1. Get your phone back to 1.5 cupcake by whatever means necessary. I used these directions: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
2. Follow these steps to root your device: http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/. When you are done with this process you should have Amon_RA's recovery and boot loader all setup. This will allow you to format your SD card to whatever file system you want, flash roms, do nandroid backups, the works.
3. Go to Amon_RA's thread about SPL's: http://forum.xda-developers.com/showthread.php?t=529019
and download a Engineering SPL for your phone. (Engineering SPL 1.33.2004 by Crios worked for me)
4. Edit the SPL file name to "update.zip"
5. Load the SPL to the root of your SD card.
6. Load up RA's boot loader. (Power + Home)
7. Wipe / Clear from the boot loader menu.
8. Apply update.zip from the boot loader menu.
9. Wait for the phone to reboot, all kinds of whacky **** will happen, don't mess with the device, etc. Eventually you should reboot into recovery mode. Whatever you do - figure out how to get to recovery mode.
10. Wipe / Clear from the boot loader menu.
11. Format the SD VIA boot loader.
12. Load a new / favorite ROM onto the SD. (I use Blueberry Hero)
13. Install the Rom VIA boot loader.
14. Crack open a beer.
No gold card, fastbook, no crazy 40 step process. There may be some security issues or something involved with this process. Whatever the case, whatever the politics are between XDA/unlockr - this WORKED for me from a STOCK 1.6 device.
With a little bit of reading you should either have turned your phone into a 400$ brick or a happy little Hero pumping Android phone.
Cheers.
Click to expand...
Click to collapse
thanks for the how too... worked great for me... running Engineering SPL 1.33.2009... thanks again!
I've run Eugene373's 2.0, MLIGN's 3.1.1, and am now running OTPA 3.0, and I have yet to tinker with the SPL. Only problems I've had is with MLIGN's Hero, the screen would get all blurry, which is why I switched to OTPA.
What I'd like to know, is in your opinion, what are the advantages of switching SPL's? Is it just to enable fastboot? After each instillation, the least internal mem. i was left with was 288mb so it's not a space issue, like the G1, correct?
A life saver...
Thanks for the write up. I couldn't find any coherent answer on the issue of the perfect 0006 SPL and yours was the only thread that was specific to my needs (T-Mobile MT3G 32B).
There's no way this work on MT3G 32a?
thanks, has anyone tried or can confirm this works on mytouch 1.2?
Is there any method that will work on mytouch 1.2 without having to do all that goldcard stuff, like is there a 1 click rooting for mytouch 1.2?
thanks
lowrez01 said:
13. Install the Rom VIA boot loader.
Click to expand...
Click to collapse
can you please explain more about installing the rom via boot loader? which option to use and what should the file name be?
dude if your device is rooted, you can flash any ROM with .0006. There is no need to do this. The 1-Click root worked fine way way back when I did. There hasnt been a ROM that I haven't been able to flash.
I guess this can be useful for people who are still buying the old myTouch 3G (which is dumb, with all the new devices out there now)
I bought my mytouch used from ebay and it is 1.33.0007 and i couldnt get pass the first step. i got through the update, but it said it failed to update.
Hi guys,
I'd like to downgrade from Android 3.2 (build HTJ85B) to Android 3.0.1 (build HWI69), since this was the last version that allowed me to flash a new kernel without getting stuck at the Motorola logo. The Xoom is rooted, using the rootboot.img floating around here. Is it just a matter of flashing the stock boot, system, recovery, and userdata images back onto the Xoom? Or is there more to it than that? This will effectively unroot the phone too, correct, since it will be wiped clean? Thanks in advance for any help!
mattberman said:
Hi guys,
I'd like to downgrade from Android 3.2 (build HTJ85B) to Android 3.0.1 (build HWI69), since this was the last version that allowed me to flash a new kernel without getting stuck at the Motorola logo. The Xoom is rooted, using the rootboot.img floating around here. Is it just a matter of flashing the stock boot, system, recovery, and userdata images back onto the Xoom? Or is there more to it than that? This will effectively unroot the phone too, correct, since it will be wiped clean? Thanks in advance for any help!
Click to expand...
Click to collapse
Look, there's obviously something else going on with your Xoom that is not related to the Honeycomb version you have updated to. My suggestion is to very logically figure out what may have happened to get you stuck so we can get you unstuck.
Of course, if you go to the Moto Dev site you can download the stock images for your Xoom model (be careful to choose the correct model) and flash them through fastboot.
Don't relock.
You can reroot at HC3.01 or you can OTA update to 3.1/3.2 as desired and then root.
It's all up to you.
I know there's something else wrong, but for the life of me I cannot figure out what it is. I've tried different kernels (stock, Tiamat, different branches of each), but whenever I try to build and flash a new kernel, I get stuck at the Motorola logo, and have to reboot and reflash the older rootboot.img from these forums. I tried different mkbootimg offsets (it should be 0xe19f8000 for the Xoom I believe, correct?) and different ramdisks, but still the same problem. Unless there is some other special step I missed for building Xoom kernels, I'm out of ideas, and I know I had better luck building and flashing kernels on Android 3.0.1, so this is sort of my final fallback method.
These are the steps I took to get where I am:
1. Upgrade Android 3.2 OTA (build HTJ85B) for US WiFi Xoom (which is my model)
2. Unlock Xoom via fastboot
3. Copy su files over for root access
4. Build 2.6.36.3 kernel from source tree (many different branches, etc like mentioned above)
5. Extract ramdisk and combine with zImage kernel output using mkbootimg (tried both no offset and offset=0xe19f8000, which I found after digging around on the Xoom)
6. Flash new boot image via fastboot and reboot. This is when I get stuck a Motorola logo..
Any advice?
mattberman said:
I know there's something else wrong, but for the life of me I cannot figure out what it is. I've tried different kernels (stock, Tiamat, different branches of each), but whenever I try to build and flash a new kernel, I get stuck at the Motorola logo, and have to reboot and reflash the older rootboot.img from these forums. I tried different mkbootimg offsets (it should be 0xe19f8000 for the Xoom I believe, correct?) and different ramdisks, but still the same problem. Unless there is some other special step I missed for building Xoom kernels, I'm out of ideas, and I know I had better luck building and flashing kernels on Android 3.0.1, so this is sort of my final fallback method.
These are the steps I took to get where I am:
1. Upgrade Android 3.2 OTA (build HTJ85B) for US WiFi Xoom (which is my model)
2. Unlock Xoom via fastboot
3. Copy su files over for root access
4. Build 2.6.36.3 kernel from source tree (many different branches, etc like mentioned above)
5. Extract ramdisk and combine with zImage kernel output using mkbootimg (tried both no offset and offset=0xe19f8000, which I found after digging around on the Xoom)
6. Flash new boot image via fastboot and reboot. This is when I get stuck a Motorola logo..
Any advice?
Click to expand...
Click to collapse
Quick question: are you using CWM Recovery to flash the zip files, and if so what version of recovery do you have installed?
The version which works best for the Xoom is v3.2.0.0 R4c. However if you "updated" through Rom Manager to v4.0.0.X, that version is incompatible with the external sdcard and if you are trying to flash from your internal sdcard, it will seem like it's working but will not work, will just hang or revert to previous state. So maybe I'm really off base...you seem to know a lot...but I've seen similar problems caused by that bad recovery version.
I'm not using CWM at all, since I still don't have an SD card to use (I'm waiting on an order from a few weeks back). So that is probably not the issue. I hope to test using CWM after my card arrives, maybe that will fix the issue, but I doubt it.
Edit: Also, just to clarify, I'm not flashing any zip files, just the boot image .img files.
mattberman said:
I'm not using CWM at all, since I still don't have an SD card to use (I'm waiting on an order from a few weeks back). So that is probably not the issue. I hope to test using CWM after my card arrives, maybe that will fix the issue, but I doubt it.
Edit: Also, just to clarify, I'm not flashing any zip files, just the boot image .img files.
Click to expand...
Click to collapse
So you are decomposing the zip files and flashing image files through fastboot? Because you know you can't flash zip files through fastboot.
mattberman said:
Hi guys,
I'd like to downgrade from Android 3.2 (build HTJ85B) to Android 3.0.1 (build HWI69), since this was the last version that allowed me to flash a new kernel without getting stuck at the Motorola logo. The Xoom is rooted, using the rootboot.img floating around here. Is it just a matter of flashing the stock boot, system, recovery, and userdata images back onto the Xoom? Or is there more to it than that? This will effectively unroot the phone too, correct, since it will be wiped clean? Thanks in advance for any help!
Click to expand...
Click to collapse
Worst logic EVAR
mattberman said:
I'm not using CWM at all, since I still don't have an SD card to use (I'm waiting on an order from a few weeks back). So that is probably not the issue. I hope to test using CWM after my card arrives, maybe that will fix the issue, but I doubt it.
Edit: Also, just to clarify, I'm not flashing any zip files, just the boot image .img files.
Click to expand...
Click to collapse
Annnnd here is the problem....flash in a custom image would be a good start to fixing ur trouble. Search solarnz custom clockwork recovery image and flash through fastboot
rockhumper said:
Annnnd here is the problem....flash in a custom image would be a good start to fixing ur trouble. Search solarnz custom clockwork recovery image and flash through fastboot
Click to expand...
Click to collapse
He doesn't have his microsd card yet. But might as well get ready.
okantomi said:
So you are decomposing the zip files and flashing image files through fastboot? Because you know you can't flash zip files through fastboot.
Click to expand...
Click to collapse
Sorry if I was unclear, I am not using any zip files anywhere in the flashing process, except when dealing with the ramdisk. I've done this many times before with other devices, I'm not completely new to the process.
rockhumper said:
Worst logic EVAR
Click to expand...
Click to collapse
How is that bad logic? If something isn't working as it should, go back to the last stable point when it did.
rockhumper said:
Annnnd here is the problem....flash in a custom image would be a good start to fixing ur trouble. Search solarnz custom clockwork recovery image and flash through fastboot
Click to expand...
Click to collapse
I could try this but how would that help? Do I need a custom recovery image to flash a new kernel? It won't work with stock? I'll give it a shot, thanks for the input. Okantomi, he's talking about the recovery .img file (flashed via fastboot), and not the .zip via CWM (I think).
Just get a 2gb or 4gb sd card, or borrow one from a phone, it's pretty simple...
To go back just grab the stock images from my sticky. Fastboot flash them, wipe cache and start over.
Sent from my PG86100 using Tapatalk
Hi everyone... I've tried searching and seen references to this kind of thing, but no download links or guides...
So I've got my Nexus S (bootloader unlocked, rooted, stock 2.3.4 until attempting the following, I have no Sim card in this phone), and I tried to flash 2.3.6, and while the update appeared to run just fine, the wifi won't turn on, just gives "error". So I attempted several things, reflashing the update, flashing the 4.04 update (which was the original point), etc, but they all give the following; installation aborted, assert failed, error in xxx.zip, "status 7".
Anyways... I'm a bit at a loss, I've never had this problem, or any problems flashing ROMs on other phones or updates. It seems no update.zip, or any .zip, will install. Back in my captivate days, there was a very handy program called Odin, and it had a master clear functionality that brought you back to the stockest of stock. Ideally... is there a tool like this for the Nexus S? I don't care about whether or not it re-locks the bootloader, I can unlock it again in just a couple minutes... but I need help.
I've read guides about "return to stock" but they all involve flashing a .zip. I need a way to push past that, and get back to 2.3.4, or alternatively, a way to completely reinstall 2.3.6.
I know an Odin exists for the Nexus S, but is there a way to use that to reset to stock?
Thank you so much anyone who can help...
Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
And as always, make sure you backup properly before flashing -anything-.
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.
Harbb said:
Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
Click to expand...
Click to collapse
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Harbb said:
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.
Click to expand...
Click to collapse
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?
Dareoth said:
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
Click to expand...
Click to collapse
Some people supposedly had troubles with the ICS update and keeping all data as-is, though i've not experienced it myself, but it is definitely possible and with such a big update, if it's in your power to start fresh it is always the best option. It was more of a general statement, not directed at your situation - something to keep in mind
Dareoth said:
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Click to expand...
Click to collapse
You can flash the latest CWM through fastboot from your PC or Mac, you can grab the latest file from here. Name it whatever you like and put it in a known folder (preferrably current folder) and : fastboot flash recovery recovery.img
Dareoth said:
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?
Click to expand...
Click to collapse
Of course i do
Great, I'm all set now. Thanks so much.
(Also for linking to that ref guide again, I had read it three times, but I didn't get how to use it until I went in going, I just need the fastboot commands, which is all that guide gives.)
Your welcome mate. All you need for that is setting up the android SDK or essentially downloading platform-tools seperately. There are guides all over the place describing how to do this for Windows, Mac and Linux as it is no different from getting oem unlock to work, they're just mostly disguised as rooting guides.
Once you do it the first time it's quite simple, but it can definitely be confusing before that