What's My Course of Action Here? - Nexus S Q&A, Help & Troubleshooting

Yikes, am I in a predicament.
So, here I am, with my Nexus S I9020A on Koodo in Canada, rooted with TWRP v2.2.0 recovery and stock 4.0.4; well, with all the JellyBean buzz going about I figured, hey, why not, and I made a nandroid backup using TWRP, and copied said backup onto my PC for an extra copy.
Well, after playing around with an AOSP rom of 4.1.1 I want the stock OTA, but restoring the backup I made yields no results, touting "no recovery or img" as an error. So now I have no idea how to get to either stock JellyBean (which is where I want to be) or at least stock 4.0.4 for the I9020A so I can get the OTA.
What do I do?!

Try flashing twrp again. I had this problem on my ns4g awhile ago while running one of the older twrp recoveries. If memory serves, I was able to reflash twrp, reboot recovery, then restore a twrp backup. If it still won't restore, try wiping & flashing a ROM of your choice. You may have to adb fastboot flash...
Sent from my Nexus S 4G using xda premium

p1gp3n said:
Try flashing twrp again. I had this problem on my ns4g awhile ago while running one of the older twrp recoveries. If memory serves, I was able to reflash twrp, reboot recovery, then restore a twrp backup. If it still won't restore, try wiping & flashing a ROM of your choice. You may have to adb fastboot flash...
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I'm trying to reflash TWRP and restore again - fingers crossed.
What happened to that list of all official OTA variants for the Nexus S?
I'm referring to that list that had for instance :
Nexus S - I9020A:
2.3.4 - Download link
2.3.6 - Download link
etc, etc.
I just want to get back to stock 4.0.4 so I can get the 4.1.1 OTA :S
Or have any way to get to STOCK 4.1.1 for the I9020A Nexus :S

Found this link posted by user oldblue910, it should have what you need if you're still stuck... http://www.randomphantasmagoria.com/firmware/nexus-s/
Sent from my Nexus S 4G using xda premium

p1gp3n said:
Found this link posted by user oldblue910, it should have what you need if you're still stuck... http://www.randomphantasmagoria.com/firmware/nexus-s/
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
That's exactly what I was looking for, thanks, ended up just taking the long road there and back from Gingerbread to JellyBean, so far so good!
Thanks for everyone's help!

Related

cant load recovery

Hey guys..
I just today rooted my lovely Nexus S, 9023 or what its called (non branded or nothing)
But i cant load recovery.. went fine when i rooted it, but now that i want to load an custom rom it fails.. i followed this guide to root: http://forum.xda-developers.com/showthread.php?t=883032
Anyone have some ideas??
I just get a android logo and triangle + ! in it.. as error.. (
Best regrads
n0ta
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
n0ta said:
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
Click to expand...
Click to collapse
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
I have had this happen on my NS4G. I know they are a little different, but it seems like you are having the same thing happen that I did and to solve it, I open Windows command prompt(or terminal depending on you OS) and fastboot flash recovery (insert recovery.img name here) and reflashed the recovery partition with clockwork. Very easy fix. Just make sure you boot straight into recovery after flashing and flash the Rom you want to flash before booting back into stock(also make a nandroid before that). After that you shouldn't have any more problems unless you unroot. There must be a small glitch somewhere when flashing the clockwork doesn't fully erase stock recovery partition.
krohnjw said:
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Works now thanks all to both of you.
n0ta said:
Works now thanks all to both of you.
Click to expand...
Click to collapse
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
bender_123 said:
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
Click to expand...
Click to collapse
The Nexus one did the same thing. Most OTAs verify / replace this file. It's easy enough to deal with if you're unlocked and rooted.
Sent from my Nexus S 4G using XDA Premium App
This is about the third or fourth time this question has come up over the past week...
bender_123 said:
This is about the third or fourth time this question has come up over the past week...
Click to expand...
Click to collapse
I assure you it won't be the last.
Sent from my Nexus S 4G using XDA Premium App

[Q] i9020A updating to 2.3.6

I really hate to do this, but i've searched for a while now and can't seem to find anything that matches my situation.
i'm on stock 2.3.4, but rooted with a different kernel, boot image, and a different radio flashed. I realize that i'm not going to be able to install the update directly from my phone, but I can't seem to install the signed update file through cwm or the stock recovery I just flashed. cwm fails with a status 7 error, and stock recovery won't even let me bring up the menu to manually install the update.
i'm just wondering if I should flash a stock rom with recovery and then try to flash the update that way, or is there some other way that I could do it? I don't want to lose any data from my phone, and I would flash the full 2.3.6 rom instead, but I can't connect to the download link in this thread http://forum.xda-developers.com/showthread.php?t=1063664.
once again, I really hate to do this, but I am pretty much stuck right now.
thanks
hoponpop said:
I really hate to do this, but i've searched for a while now and can't seem to find anything that matches my situation.
i'm on stock 2.3.4, but rooted with a different kernel, boot image, and a different radio flashed. I realize that i'm not going to be able to install the update directly from my phone, but I can't seem to install the signed update file through cwm or the stock recovery I just flashed. cwm fails with a status 7 error, and stock recovery won't even let me bring up the menu to manually install the update.
i'm just wondering if I should flash a stock rom with recovery and then try to flash the update that way, or is there some other way that I could do it? I don't want to lose any data from my phone, and I would flash the full 2.3.6 rom instead, but I can't connect to the download link in this thread http://forum.xda-developers.com/showthread.php?t=1063664.
once again, I really hate to do this, but I am pretty much stuck right now.
thanks
Click to expand...
Click to collapse
Sent from my Google Nexus S using XDA Premium App
The 2.3.6 update for the i9020a was pulled by Google. There will be a new update released soon. I would wait.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
The 2.3.6 update for the i9020a was pulled by Google. There will be a new update released soon. I would wait.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
i'm pretty sure it just got re-released. i'm guessing it isn't causing issues anymore either

Will Nexus S Unlocked bootloader and custom kernel update OTA to ICS when it's out?

My gf got a Nexus S last month and loves it! She just needs BLN to work... so we unlocked the bootloader and installed a custom Kernel (Matr1x I believe). Will the OTA come through? If so, will it wipe out anything like CWR or the unlocked bootloader? I saw Matr1x already released a ver for ICS so it would be an easy install...
Sent from my XT860 using xda premium
danifunker said:
My gf got a Nexus S last month and loves it! She just needs BLN to work... so we unlocked the bootloader and installed a custom Kernel (Matr1x I believe). Will the OTA come through? If so, will it wipe out anything like CWR or the unlocked bootloader? I saw Matr1x already released a ver for ICS so it would be an easy install...
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
No it wont update.
Sent from my Nexus S using xda premium
thegtfusion said:
No it wont update.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
How would I go about updating the device? She's pretty excited for ICS.
It will fail the verifying stage of the update. All the original files of the previous version of the update your flashing needs to be there.
snandlal said:
It will fail the verifying stage of the update. All the original files of the previous version of the update your flashing needs to be there.
Click to expand...
Click to collapse
So if I restore the Kernel (I'm not sure how I would go about doing that though, can someone provide instructions? ) would it apply the update at that point? Or do I need to re-lock the bootloader? Relocking would be a pain........
danifunker said:
So if I restore the Kernel (I'm not sure how I would go about doing that though, can someone provide instructions? ) would it apply the update at that point? Or do I need to re-lock the bootloader? Relocking would be a pain........
Click to expand...
Click to collapse
If you have a nand backup of stock restore it, Otherwise download one of the stock roms from here and flash it in recovery.
http://forum.xda-developers.com/showthread.php?t=1063664
snandlal said:
It will fail the verifying stage of the update. All the original files of the previous version of the update your flashing needs to be there.
Click to expand...
Click to collapse
That depends on what kind of update it will be ... The update from 2.3.3 to 2.3.4 on my i9023 nexus was a full rom and could be flashed without a problem.
Verstuurd van mijn Nexus S met Tapatalk
Go back to latest available stock version. (Rooted with Superuser.apk in /system/app is OK) & Keep your Custom Recovery or reflash it.
Put a Superuser flashable zip on your sdcard.
When you have the OTA update.zip somewhere on your sdcard ( Copied from /cache) boot into custom recovery
Flash update.zip manually and directly after it flashes, flash the Superuser.zip right on top of update.
Wipe /cache
Reboot
Download Joeykrim's flash_image gui from the market.
Place custom-recovery.img on root of sdcard. (Rename it to recovery.img)
Flash custom recovery in flash_image gui
Change permissions of /system/etc/install-recovery.sh & /system/recovery-from-boot.p to "000"
I would just wait till ics is out and then youll find a flashable .zip here on xda and you can just flash that like you did with the matr1x kernel... not shure if full wipe would be nescesary but if yes then you can backup your apps through titanium or sth similar!
Sent from my Nexus S using XDA App
Edit: what i actually wanted to say that theres no need to go back to stock now because you can get the update over xda and just flash that!
while we're on the topic....would editing the build.prop keep an OTA from installing? For example, LCD density??
Why not just wait like one day for someone to post a rooted stock ICS rom? I am sure one of our wonderful devs here will be all over it. It will probably show up in one of those REF threads pretty quickly. Then you don't have to mess around with setting root up again. That's what I always did with my EVO Shift so I'll probably do it with this phone as well.
If you hadn't modified your build.prop or removed system apps, you'll just need to flash the stock kernel. Theres no need to flash the whole stock Rom.
What if your bootloader is unlocked and nothing else. Will it get the OTA?
Question since we on the subject when will ics be released for our phones or is it still unknown as to when is gonna be released?
Sent from my Nexus S 4G using Tapatalk
cpaixao said:
If you hadn't modified your build.prop or removed system apps, you'll just need to flash the stock kernel. Theres no need to flash the whole stock Rom.
Click to expand...
Click to collapse
That's exactly what I was looking for... but where would I find the stock Kernel and can I overwrite it while the system is in use? I downloaded the entire stock ROM for her phone so I should have the file somewhere in one of the IMG files (yes, I have mounted them before in Windows)
Sent from my XT860 using xda premium
danifunker said:
That's exactly what I was looking for... but where would I find the stock Kernel and can I overwrite it while the system is in use? I downloaded the entire stock ROM for her phone so I should have the file somewhere in one of the IMG files (yes, I have mounted them before in Windows)
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
boot.img is the kernel.
How do I apply just boot.img?
Sent from my XT860 using xda premium
Fastboot flash boot boot.img
Sent by breaking the sound barrier

Moving from ICS Alpha11 to Official?

Hi,
I'm currently using Koush's ICS Alpha 11, I've downloaded the official 4.0.3 version and tried to rename it "update.zip" and flash but it fails.
I'd really appreciate any help.
Thanks!
Did you go back to stock 2.3.6 and flash in stock recovery
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Oh, so I should download this:
Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
... rename it to update.zip and then back into CWR and then ICS?
Download stock 2.3.6 and flash it you will loose clockwork mod.you have to do this to apply the official
Rename it to update.zip
In fastboot mode go to recovery and select it with your power button
When you see the android question mark hold up and power again
Choose apply update.zip and bam your done
I forgot get voodoo ota root keeper from the market and run it before flashing the stock rom
Good luck and keep ne posted
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Can't seem to find FULL stock 2.3.6 for nexus S, some links floating around the web are just the update packs (around 12mb), not full.
ibr4him said:
Can't seem to find FULL stock 2.3.6 for nexus S, some links floating around the web are just the update packs (around 12mb), not full.
Click to expand...
Click to collapse
There's a stickied post right here on the forums (this forum, in fact). It has every OTA released.
- chris
You do not need to go back to stock recovery. Do it all from cwm recovery.
Full wipe and flash the 2.3.6 from
Flash the ota file.
Reboot. The reboot into the os will flash the stock recovery
Sent from my Nexus S using XDA App
Hey guys, I'm in a similar situation too, I'm on Carbon ROM and I was waiting for a Stock update. So is there any way that I can update and keep the root? Because I think when I'll flash the stock 2.3.6, I'll lose root.
ok so I went back to 2.3.6 stock, and susprisingly I didn't lose my root/cwr or anything, then I went into recovery again and tried installing update.zip (which is ICS official stock) but the same error:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
When you go back to stock you need to do a wipe.
Sent from my Nexus S using XDA App
I did wipe partition as well as cache. let me try again though.
Format everything but sdcard. Flash the official 2.3.6 T-Mobile rom. Flash the official ota update for said rom and your good. You would have to have a the 9020t model of course
Sent from my Nexus S using XDA App
albundy2010 said:
Format everything but sdcard. Flash the official 2.3.6 T-Mobile rom. Flash the official ota update for said rom and your good. You would have to have a the 9020t model of course
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
How do I format? from PC? delete everything from the mounted usb volume?
From cwm recovery. Mounts and storage. Just DONT format your sdcard. Your backups are there.
Sent from my Nexus S using XDA App
I don't have clockwork anymore. I see limited options now, and the title on top is "Android System Recovery <3e>", but I do see an unlock icon when the phone boots.
You need to reflash clockwork from fastboot. When you load a stock os it overwrites the recovery
Sent from my Nexus S using XDA App
I have no clue how I did it couple months back, can you please point me to a guide that shows how to flash cwr on 2.3.6? many thanks
What rom that is on the phone does not matter . You just need to get your phone recognized on a computer with fastboot. Then flash the recovery from there. Or just boot the recovery directly from fastboot.
Sent from my Nexus S using XDA App
hmmmmmmmmmmmmmmmmmmmmmmm
are you going to go around and say stupid crap in every thread now?
Sent from my Nexus S using XDA App

[Q] CM Stuck on logo animation while booting

Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
- Rooted it using the following guide (it now has ICS)
- SIM Unlocked it using the following guide (now it works on other networks)
- Updated to CWM 6.0.3.8, since JB roms needs it
- Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
TINGEA said:
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
-Rooted it using the following guide (it now has ICS)
-SIM Unlocked it using the following guide (now it works on other networks)
-Updated to CWM 6.0.3.8, since JB roms needs it
-Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
Click to expand...
Click to collapse
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
TINGEA said:
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
Click to expand...
Click to collapse
No boot loaders man. This is before Samsung's complications.
Recovery is here.
http://d-h.st/AFu
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Somcom3X said:
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
BTW - when I was flashing via Odin my upload phone screen was showing that I have a custom rom and the counter was 1.... do I need to fix that?
TINGEA said:
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
Click to expand...
Click to collapse
SOLUTION:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Good Luck and Happy Tweaking.
Click to expand...
Click to collapse
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but I'm not sure this is needed for my case. I read the original blog post and my recovery does not get overwritten. I actually rebooted multiple times into CWM recovery and each time it is the same 6.0.4.4.
I also went into the /system/etc folder and there is no install_recovery.sh file.
to clarify, here is where I'm stuck now:
- when I use CWM 6.0.3.8 CM install completes successfully, but then CM will not boot, and will keep on cycling on the boot logo screen.
- when I use CWM 6.0.4.4 I can't start to install CM as it complained that my phone is not t769.
in all cases I'm using CM 10.2 nightly for T769.
Thanks for the help.
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but this is more trouble than what I wanted to put in - I'll stick with the rooted stock ROM I have. I was hoping the process was a little more straight forward, similar to my SGS3.
thanks for all your help thus far!
Somcom3X said:
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
TINGEA said:
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
Click to expand...
Click to collapse
Hmm. Go back to stock ics, flash a 10.2 recovery, then flash whatever you desire.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It would be cwm 6.0.2.7
You can flash the img through a zip or by terminal on the phone.
Odin needs a tar'd recovery img
Sorry been very busy.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2577265
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
TINGEA said:
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
Click to expand...
Click to collapse
I'm very sorry for the delay. Been very very busy.
https://www.dropbox.com/s/awp1zy4u3x34a2v/CWM-cm-10.2-Recovery-t769.zip
That is my personal 10.2 recovery. Works fine for me.
The author is me, but I was too lazy to change the lines.
Sent from my SAMSUNG-SGH-T769 using Tapatalk

Categories

Resources