[Q] NS4G d720 issues after flashing imm26 - Nexus S Q&A, Help & Troubleshooting

hello,
i am a first time poster on here. i have been very thankful for all help i have read about thus far. i have a NS4G and i just couldnt wait for ICS 4.0.4 and was looking around and foud the IMM26 build and instructions how to install it with Odin. followed all the directions to a T, but then all my friends were getting the OTA and it is IMM76d. i habe tried installing the IMM76d with odin 1.85 and it fails, now i know its been said that one may have to use an HTC usb cord and i do. i also have tride to do the recovery mode and apply the downloaded imm76d update renamed it update.zip ans that aborts showing a status 7 error.. i am lost. i dont want to be rooted or have an unlocked bootloader. i would just like to know how to return my phone to 2.3.7 and all factory settings so i can receive the OTA from sprint. i would greatly appreciate any help or direction to solve my issue
thanks in advance

This'll put you back on 2.3.7. (Well, 2.3.4, but then you'll get all of the OTAs until 2.3.7 and then possibly 4.0.4 if it's actually rolling out in your area)
http://forum.xda-developers.com/showthread.php?t=1167819

u could root and unlock the boot loader flash to 2.3.7 then unroot and relock boot loader and wait for ur ICS update
Sent from my Nexus S 4G using XDA Premium App

neo_x22000 said:
u could root and unlock the boot loader flash to 2.3.7 then unroot and relock boot loader and wait for ur ICS update
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
i am guessing there is a how to do this exactly somewhere here.

Related

Problems updating OTA 2.3.4

I want to update my nexus s to 2.3.4
I'm currently on stock 2.3.3, build number GRI40, baseband I9020XXB1. Rooted and unlocked bootloader.
My phone keeps trying to update ota - 12mb file but the update fails and gets stuck on a triangle with exclamation mark in it. I've tried booting into clockworkmod recovery and apply update from SD card but still it fails.
Could somebody tell me what I'm doing wrong. Thanks
Sent from my Nexus S using XDA App
JTopaz said:
I want to update my nexus s to 2.3.4
I'm currently on stock 2.3.3, build number GRI40, baseband I9020XXB1. Rooted and unlocked bootloader.
My phone keeps trying to update ota - 12mb file but the update fails and gets stuck on a triangle with exclamation mark in it. I've tried booting into clockworkmod recovery and apply update from SD card but still it fails.
Could somebody tell me what I'm doing wrong. Thanks
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
if you want to update to 2.3.4 via OTA,you have to run stock rom,otherwise update will be fail
There is a sticky in the general forum: 2.3.4 OTA guide. the first post has a link to a full rom that should do the trick
Sent from my Nexus S

[Q] OTA 2.3.4 update

Hi All
Let me start by saying what a wicked forum, I love it!!
Hopefully I wont get shot for this.
I have tried the search function and read a number of posts, but it has just confused me.
I have an unbranded HTC Sensation 2.3.3 s-off and rooted.
I want to update it to 2.3.4, I have had the OTA notification and the install failed.
My question is, do I have to install a custom ROM, or is there away to install the OTA update. I know I will probably lose root.
Thank you
Kam
You must be on stock ROM and stock recovery. Not sure if root matters
Sent from my HTC Sensation using Tapatalk
I've got CWM how do I get back to stock recovery? I've got stock rom.
KamSandhu44 said:
I've got CWM how do I get back to stock recovery? I've got stock rom.
Click to expand...
Click to collapse
You can always get the Ruu.exe and extract the recovery image and make a flashable zip. There are numerous threads about it.
Sent from my HTC Sensation 4G using Tapatalk

[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

Bootloader brick possible?

Hi, sorry if there is some answer to my question but i couldn't find it. Is there any chance of bricking device or screw something up when unlocking a bootloader? Tnx.
Sent from my GT-I5800
Not by unlocking it via fastboot OEM unlock. You could brick phone by flashing an incorrect bootloader..
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
Not by unlocking it via fastboot OEM unlock. You could brick phone by flashing an incorrect bootloader..
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
How to know which bootloader to use..?
Sent from my GT-I5800
Don't touch the bootloader, they generally come with the ROM. As for a recovery partition, most people use ClockWorkMod Recovery. Latest version is 5.0.2.0 and recommended.
Harbb said:
Don't touch the bootloader, they generally come with the ROM. As for a recovery partition, most people use ClockWorkMod Recovery. Latest version is 5.0.2.0 and recommended.
Click to expand...
Click to collapse
The only thing i want to do, is instal official OTA gb 2.3.6 from recovery on my nexus s, than try system upgrade from phone settings, to upgrade on ICS. Or if that is not working, to flash 2.3.6, than official OTA ICS from recovery.
My question is, do i really must unlock bootloader to flash any official or custom rom from stock recovery? As you can see i'm new to this, i have galaxy 3, there is all simple, just flash flash flash. Here i read you must unlock bootloader, than root, than install recovery..
Sent from my GT-I5800
Only need to unlock for unofficial ROMs. If you're using an official .zip (upgrade or full), you do not need an unlocked bootloader, a custom recovery or root. Just open the stock recovery and flash away.
I recently accidentally (noob) flashed a nexus s jelly bean bootloader update on my nexus s 4g and it screwed up my network, unable to be flashed for service. My USB doesn't get recognized by my computer regardless of cord or computer. Phone wi-fi works but no network, is there any way to solve this problem.
Just do a re flash using cwm, and throw it on a sd card and do it from your phone. Something similar happened to me.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Bad bootloader
Nexus85 said:
I recently accidentally (noob) flashed a nexus s jelly bean bootloader update on my nexus s 4g and it screwed up my network, unable to be flashed for service. My USB doesn't get recognized by my computer regardless of cord or computer. Phone wi-fi works but no network, is there any way to solve this problem.
Click to expand...
Click to collapse
Friend a have de same problem, my system works perfectly but doesn't have network. I put a korean version bootloader and I'm not root and don't have CWM recovery. I'm wait for jelly bean update because it has a new bootloader.img. I was reading this thread http://forum.xda-developers.com/showthread.php?t=1566475 but the nexus s 4G has all electronic things in different side.
I'm ask for help in this link http://forum.xda-developers.com/showthread.php?t=1839449.

New guy

Hello guys I just got may galaxy S3 from a friend. I think the bootloader is still unlocked after I received an OTA today. I don't have root or recovery. I just want to be sure I use the correct root and recovery method. Could someone point me to the one they used on this build with success? I would be greatly appreciated. I did look but none are specific enough for me to be sure I'm using the correct one.
Is my bootloader still unlocked if it says (custom)?
Again I appreciate any help
Sent from my SCH-I535 using xda premium
mike216 said:
Hello guys I just got may galaxy S3 from a friend. I think the bootloader is still unlocked after I received an OTA today. I don't have root or recovery. I just want to be sure I use the correct root and recovery method. Could someone point me to the one they used on this build with success? I would be greatly appreciated. I did look but none are specific enough for me to be sure I'm using the correct one.
Is my bootloader still unlocked if it says (custom)?
Again I appreciate any help
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Welcome! In order to unlock your BL in the first place you must have had root. This is a good thread on rooting, unlocking, and flashing recovery/ROMs/kernels:
http://forum.xda-developers.com/showthread.php?t=1762709
nghtrain88 said:
Welcome! In order to unlock your BL in the first place you must have had root. This is a good thread on rooting, unlocking, and flashing recovery/ROMs/kernels:
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
Thanks so much bud! Will I be all good on the updated build I received today?
My bootloader is unlocked if it says custom on boot?
Again I really appreciate it!
Sent from my SCH-I535 using xda premium
mike216 said:
Thanks so much bud! Will I be all good on the updated build I received today?
My bootloader is unlocked if it says custom on boot?
Again I really appreciate it!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
As long as you have one of the stock builds listed in section 2 of that thread you should be good. The EZ-unlock app should be able to tell you if you're BL is unlocked.. also if you reboot the phone, if the samsung splash flashes for a split second (the one before you see Samsung Galaxy SIII), then you're prob unlocked.. if you see it for a few seconds then you're prob locked
Man I rooted flashed recovery in rom manager. (recovery wouldn't stick) so I flashed it again after making a nandroid and ended up having to recover a soft brick at 4am. Thank God for puremotive's guide on how to recover from it I was able to be back up. I don't know what went wrong. Because I didn't have busy box. Maybe I shouldn't have used the latest recovery rom manager flashes? I'm on stock with root and afraid to move anywhere! Anyone know how to make recovery stick on stock rom? I've never had this happen. Usually I would be OK and on to try AOSP on other devices uve had. Right now I'm rooted on stock rom with bootloader unlocked and have OTA root keeper in case I get another OTA. Any help would be greatly appreciated! Take care
Sent from my SCH-I535 using xda premium
How did you unlock your bootloader?
annoyingduck said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
With the app
Sent from my SCH-I535 using xda premium
Ok, issue is probably that you used the current version 1.4 I think. In the app description in the playstore is a link to older versions, you want 1.2. The new ones are unlocking, but it's not sticking. There is also a link in the current root guide somewhere, but direct from the play store is fine.
annoyingduck said:
Ok, issue is probably that you used the current version 1.4 I think. In the app description in the playstore is a link to older versions, you want 1.2. The new ones are unlocking, but it's not sticking. There is also a link in the current root guide somewhere, but direct from the play store is fine.
Click to expand...
Click to collapse
link for ez-unlock 1.2
annoyingduck said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
Let me be more specific because I may have had a locked bootloader.
I received the phone yesterday from my friend. He did unlock the bootloader with the app. I installed the official OTA from Verizon as soon as I got it. I rooted it. I didn't bother trying to unlock the bootloader because after the OTA when it booted it said custom with a lock symbol on boot up. I rooted and flashed the latest recovery from rom manager. I'm sure I picked the right phone. I made a nandroid but my recovery wouldn't stick. I remember it saying something about Co firming something about a recovery and I could have chosen yes. It sounded like CWM wouldn't stick if I choose yes?
I don't know if the OTA locked my bootloader back up?
I would like to try again. Any of you guys no how to make recovery stick on stock rom? I would like to try paranoid android. What recovery should I be on to flash this jelly bean based rom? I would really appreciate anyone who knows how I screwed up or has went straight to JB from a specific CWM recovery. I'm also not sure if I should said yes or know when in CWM when asking me that recovery question. I wish I remember what the question was
Sent from my SCH-I535 using xda premium
nghtrain88 said:
As long as you have one of the stock builds listed in section 2 of that thread you should be good. The EZ-unlock app should be able to tell you if you're BL is unlocked.. also if you reboot the phone, if the samsung splash flashes for a split second (the one before you see Samsung Galaxy SIII), then you're prob unlocked.. if you see it for a few seconds then you're prob locked
Click to expand...
Click to collapse
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
mike216 said:
Man I rooted flashed recovery in rom manager. (recovery wouldn't stick) so I flashed it again after making a nandroid and ended up having to recover a soft brick at 4am. Thank God for puremotive's guide on how to recover from it I was able to be back up. I don't know what went wrong. Because I didn't have busy box. Maybe I shouldn't have used the latest recovery rom manager flashes? I'm on stock with root and afraid to move anywhere! Anyone know how to make recovery stick on stock rom? I've never had this happen. Usually I would be OK and on to try AOSP on other devices uve had. Right now I'm rooted on stock rom with bootloader unlocked and have OTA root keeper in case I get another OTA. Any help would be greatly appreciated! Take care
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
mike216 said:
Let me be more specific because I may have had a locked bootloader.
I received the phone yesterday from my friend. He did unlock the bootloader with the app. I installed the official OTA from Verizon as soon as I got it. I rooted it. I didn't bother trying to unlock the bootloader because after the OTA when it booted it said custom with a lock symbol on boot up. I rooted and flashed the latest recovery from rom manager. I'm sure I picked the right phone. I made a nandroid but my recovery wouldn't stick. I remember it saying something about Co firming something about a recovery and I could have chosen yes. It sounded like CWM wouldn't stick if I choose yes?
I don't know if the OTA locked my bootloader back up?
I would like to try again. Any of you guys no how to make recovery stick on stock rom? I would like to try paranoid android. What recovery should I be on to flash this jelly bean based rom? I would really appreciate anyone who knows how I screwed up or has went straight to JB from a specific CWM recovery. I'm also not sure if I should said yes or know when in CWM when asking me that recovery question. I wish I remember what the question was
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Brian Gove said:
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Click to expand...
Click to collapse
Thanks for everything Boss! That probably was the reason my recovery wouldn't stick. I used the link to grab easy unlock 1.2. I'm now unlocked, rooted. I want to flash an AOSP based rom (paranoid android) what recovery should I flash? The newest in rom manager or the slightly older one EZ-Recovery has to offer?
Thanks once again!
Sent from my SCH-I535 using xda premium
Cwm 6.0.1.2 for aosp jb, do not use the old 5 . something touch in ez recovery
mike216 said:
Thanks for everything Boss! That probably was the reason my recovery wouldn't stick. I used the link to grab easy unlock 1.2. I'm now unlocked, rooted. I want to flash an AOSP based rom (paranoid android) what recovery should I flash? The newest in rom manager or the slightly older one EZ-Recovery has to offer?
Thanks once again!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Which is the recovery that you want to use? I have the latest CWM touch on my Dropbox if that's the one you want. The regular CWM in the app is fine to use and twrp recovery has a thread in the development forum.
Brian Gove said:
Which is the recovery that you want to use? I have the latest CWM touch on my Dropbox if that's the one you want. The regular CWM in the app is fine to use and twrp recovery has a thread in the development forum.
Click to expand...
Click to collapse
I'm on stock ICS in want to go to paranoid android. Sorry guys but after last night I'm paranoid myself!
Sent from my SCH-I535 using xda premium
Brian Gove said:
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Click to expand...
Click to collapse
Thanks once again! I'm now on PA after a pack of smokes! Appreciate all your help. You were absolutely right ! Recovery stuck and it flashed with no problem. I used the current recovery straight from ROM manager
Sent from my SCH-I535 using xda premium
Good, glad to hear you got it rolling.

Categories

Resources