Flashing Radio & Recovery - Nexus S General

I haven't touched my Nexus S in a while and wanted to flash some new ROMs. I'm sure my radio and recovery files are outdated.
What's the best way to flash the latest radio and recovery files now? I believe I used Android SDK back in the day, but I'm sure there's another way now. Any information would be appreciated!

Android SDK still works
stewroids said:
I haven't touched my Nexus S in a while and wanted to flash some new ROMs. I'm sure my radio and recovery files are outdated.
What's the best way to flash the latest radio and recovery files now? I believe I used Android SDK back in the day, but I'm sure there's another way now. Any information would be appreciated!
Click to expand...
Click to collapse
FWIW (maybe there is a better method)
I had to update my radio just the other day and found the old SDK method worked perfectly...
Steps
1. Came across this ADB statement to flash radio 'fastboot flash radio radio-crespo-i9020xxki1.img'
2. Found GT-I9020T radio-crespo.i9020xxki1.img file here: http://forum.xda-developers.com/show...php?p=24217600
3. ADB: adb reboot bootloader
4. ADB: fastboot devices
5. ADB: fastboot flash radio D:\XYZ\radio-crespo-i9020xxki1.img
If you're looking for a different approach then I have had excellent results with the NexusRoot Toolkit.

Use Odin to flash the latest factory image from here. It's the safest, most user-friendly method. Unless you're comfortable with terminal I wouldn't recommend using it for fastboot flashing.
just download the archived files from the google factory image page and extract the .img files from it to use with Odin.

Related

[Q]How to flash back to stock with no USB?

I have a problem with mounting my phone in Windows (see here; http://forum.xda-developers.com/showthread.php?t=841645) and I need to return it for testing.
How can I flash it back to stock without a USB connection?
E.E.
Assuming you're rooted and on a custom ROM
You will need unlimited data to try this.
Not sure if this will work, but please do try.
1. Make sure your phone is juiced up.
2. Download the Stock RUU you want from the internet - save to your sdcard
3. Download another sense based ROM that you has no issues with the USB cable - check the post and changelogs.
4. Perform rom backup with ROM manager (get from android market)
5. Wipe and flash new Sense based ROM on your phone.
6. Once your phone is booted, the USB SHOULD WORK.
7. Move RUU to your PC. Link to HTC sync - phone should be set to sync.
8. Install RUU.
And once it is one, you have unrooted and are back to stock ROM.
Should your USB fail at stage 6, you should try a different custom ROM.
If it's still not working, you might want to search how to USB unbrick (i think there's something like that on the forums).
Unfortunately its not a rom problem. The USB issue seems to be a hardware problem.
I have flashed multiple different backups from CM6 to myvery first backup I made of the newly rooted rom.
I just need to put a stock rom on it so that I can get warranteed service. Otherwise I'm pretty sure they'll just shoot it back to me, marked warranty void.
E.E.
Have you tried this?
It's to unbrick your usb
http://forum.xda-developers.com/showthread.php?p=7616115#post7616115
I had also problems with mounting USB, can't tell if they were the same as I don't use windows and can't tell how it behaves. My problem was solved after I flashed the rooted vodafone FroYo. Maybe this could help you, too.
I haven't tested it yet but it may be as simple as downloading the zip from shipped-roms.
(http://shipped-roms.com/download.ph...35.21_release_130330_signed.zip&send_file=yes)
Renaming it to update.zip and flashing it from Recovery.
Can anyone confirm?
E.E.
Actually the best solution I've found yet is this one here from the CM forums.
This using the .img files from the zip I downloaded from Shipped-Roms earlier
Instructions
---------------
1. Boot n1 to fastboot mode
2. Extract the FRG33 files to your tools directory in PC (you need system.img and boot.img)
3. In your tools directory, fastboot the following commands
fastboot flash system system.img
WAIT
fastboot flash boot boot.img
WAIT
Reboot
Alternative method
------------------------
Rename the stock file to passimg.zip
Now you need to use ADB to get it on the SD card, or just copy file to sd card root directory
Command: adb push passimg.zip /sdcard
Now get into the bootloader and it should detect the passimg.zip file and ask if you want to install it.
Click to expand...
Click to collapse
Since I have Fastboot available to me, this seems the most hopeful method.
Can anyone confirm is this not just hopeful thinking?
E.E.

4.4.2 (KOT49H) update fails on rooted device

Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
amplifier1980 said:
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Click to expand...
Click to collapse
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit? http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Lexus One said:
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit?
Click to expand...
Click to collapse
Hi. Meanwhile i found a thread in nexus5 Android development area which contains both deodexed and odexed stock rooted full rom . so i just flashed odexed Version over my 4.4... Now i am on 4.4.2 finally... And still rooted..
Thank u anyway..
Greetz, fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
Hi,
You can try performing a full unroot in the SuperSU app if it still doesn't work... I had to adb sideload mine to work, don't know how it works with toolkit, but you have to first set your tablet to receive it. As you are on TWRP you simply go to advanced and select adb sideload, then try using the tool, or following the instructions on it to do so .
You cannot install a OTA zip like a Custom ROM zip, they are a little bit different hehe.
Hope this helps,
~Lord
PS.: This will work for N5 too.
I somehow got the idea that rooted Nexus devices with a custom recovery could handle OTA's without trashing the recovery. I guess I expected that I would lose root. I think I'm just going to wait for someone to put together a "CleanROM" based on 4.4.2 or newer. I've been waiting for a rom like this since I bought my Nex10 anyway. I don't think I'll suffer too much running on 4.4 until then.
Thanks to those who contributed, I'll remember your suggestions. Especially if I end up waiting a long time for a 4.4.2 based Cleanrom.
Update: Thanks to Wug's toolkit. I'm now running 4.4.2..
I should ask for a sticky for this but these instruction will work EVERY TIME if you are running either custom recovery or Root.
You will need the latest adb/fastboot from google, you can either install the SDK or download any of the many smaller adb/fastboot and libs for your os
You will need STOCK 4.4/4.3/4.2 recovery depending on what version of android you are currently on. Download the factory image from here. Open the zip within the package and pull out recovery.img and rename it stockrecovery.img
Copy your custom recovery to the adb folder name it twrp.zip or short name for whatever you are using I am using twrp.
You will need the correct OTA you are seeking to apply - rename it to something short simple and obvious - for this example I will use otaupdate.zip
If you wish to root get the latest patch (I believe its up to 1.75 now) and copy it to the adb/fastboot folder.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If you are already Rooted:
If you are using SuperSU - go to the application options and completely unroot and reboot if needed
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If not rooted start here:
I am assuming most of you are Windows users. Open your file explorer and open the ADB folder.
On the left hand folder where ADB is located press shift and right click the ADB folder and select "Open command window from here". This will open a command prompt window for you to run all your adb/fastboot commands from. This is the same folder where you copied your recoveries and updates to.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
Copy your custom recovery and stock recovery to your adb folder
Copy and rename the OTA to the adb folder
Copy your root.zip patch to the /sdcard downloads folder (if you wish root)
>adb reboot bootloader
>fastboot flash recovery stockrecovery.img
>fastboot reboot-bootloader
Go into recovery and wait till dead droid appears
Press power and Volume Up at same time to go into the stock recovery menu
Using the volume buttons move and down the blue list of options and select: Apply update from ADB
You will now have orange text at the bottom of the screen - follow the instructions to side load by typing >adb sideload otaupdate.zip in your command prompt window
Wait and watch the progress, at this point you should see the ota processing steps of which there a few and will vary depending on the package. When its complete there will be a "install complete" or similar message
Reboot and let the update complete the system optimizations and go in validate your device is working and the version is what you wanted
>adb reboot bootloader
>fastboot flash twrp.zip
>fastboot reboot-recovery
Using your newly installed custom recovery you can now apply zips/root etc
Reboot as needed and update root if using older .zip to current binaries and enjoy your updated device.
And yes you only need to backup once prior to starting but many people skip that step -DON'T BE ONE OF THOSE PEOPLE.
Hopefully I've not missed a bit.
You can also use these same instructions if you're stuck in boot loop or applied a patch without first replacing stock or unrooting - just boot to bootloader using fastboot and replace recovery and apply the patches. This will usually work just fine and prevent much heart ache on your part.

poor signal reception

Hi, i'm receiving very poor signal reception on my phone and was wondering if there was a way to try and fix this? I'm currently on cm12 with hellscore. Thanks!
If you have been on custom ROM's for quite some time, it may be helpful to do a TWRP backup of your cm12 and
then Flash to Lollypop Stock 5.01 image.
Reason being, it will update your radio baseband to the latest version which may improve your signal reception.
After you flash stock 5.01 image, you can restore your TWRP backup to cm12 and reflash hellscore.
The baseband will be unaffected by the restoration of your cm12 backup and still be the latest one from Lollypop Stock 5.01.
Best of luck
thanks for the reply! i was wondering, could i just update the radio baseband?
nightryder1 said:
thanks for the reply! i was wondering, could i just update the radio baseband?
Click to expand...
Click to collapse
Yes you can. Connect your phone to the computer in fastboot mode. Download the latest radio.img. Use (fastboot flash radio radio.img). OR. If you have downloaded the latest radio in .zip format, just flash it in recovery mode.
Absolutely,
Download direct from Google 5.0.1 (LRX22C)factory image for your Nexus 4. The latest is "occam-lrx22c-factory-86c04af6.tgz"
HERE
On your PC, Extract the files from the factory image and put a copy of "radio-mako-m9615a-cefwmazm-2.0.1701.05.img" in the ADB Tools folder.
restart your phone into fastboot or you can use the following ADB command.
adb reboot fastboot
Once you phone is in fastboot mode, run the following command.
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.05.img
Hope it helps to improve your signal .
Best of luck

[ GUIDE ] [ Marshmallow Firmware Upgrade ROM install including ViperOneM9 4.x.x ]

Dummy friendly guide how to upgrade, flash and install the latest Marshmallow Firmware and the latest ROM’s such as the ViperOne ROM 4.x.x, this guide is intended for those who are already slightly familiar with the flashing process and have previously managed to flash a ROM on their HTC One M9 device…
CHECKLIST BEFORE STARTING:
1) Phone is S-OFF
2) Unlocked Bootloader
3) Rooted
4) Latest TWRP recovery
5) SUPER CID changed to 11111111
6) External SD Card
7) NANDROID Backup and any or every other form of backup
8) Device drivers, Android SDK Platform Tools including ADB & FASTBOOT.
9) USB Debugging enabled.
10) BACK UP OF ALL YOUR DATA !!!
Before we begin make sure you back up all your data on both the internal and external SD card.
For the purpose of this tutorial we will be installing the latest ViperOneM9 ROM…
a) Downloaded and place the latest ViperOne ROM - ViperOneM9_4.x.x.zip on your External SD card,
Main Thread by j to the 4n is found here:
http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773
Latest ViperOne ROM for download is here:
http://venomroms.com/htc-one-m9/
b) If you are currently on ViperOneM9 3.5.0 or older and wish to upgrade to the latest 4.x.x than the latest Marshmallow firmware is required (3.35.401.12 or 3.35.617.12 firmware)… This can be found here and within Sneakyghost original thread.
https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Now download the latest version of either:
NO WIPE ZIP
or
FULL STOCK WIPE ZIP
For this tutorial we will use the FULL STOCK WIPE ZIP (to archive a clean install – this will wipe everything on your phone excluding the External SD card)
c) Place the downloaded M9_3.35.401.12_FullStock_wipe.zip into your Android SDK Platform Tools Folder (for example C:\Android\ if this is where all your tools are found)
d) Download the latest version of TWRP recovery from
http://www.teamw.in/devices/htconem9.html
Place the downloaded twrp-2.8.7.0-hima.img in your Android SDK Platform Tools Folder
e) Once you are 101% ready to begin the process start by connecting your device and launching the command window (hold shift, right click in window with all the required ADB/FASTBOOT aps and select "open command window here) once the black terminal window appears start by typing in
adb devices
if your phone appears in the list we can continue by typing:
adb reboot download
wait a few seconds for the screen to appear and type:
fastboot oem rebootRUU
your phone should now be in the RUU mode with a silver HTC logo, now type
(if you renamed the original file type its current name, by default it is as follows)
fastboot flash zip M9_3.35.401.12_FullStock_wipe.zip
f) you will most likely receive something like this towards the end after running the above command...
FAIL90 hboot pre-update! please flush image again immediate
FAILED (remote: FAIL90 hboot pre-update! please flush image again immediate)
For "hboot-preupdate" response, restart the same procedure for device...
just type the above command again and phone will flash the update again and hopefully it will take at least a minute or more to complete, hopefully there will be no more errors, just in case repeat the above command... Just in case you do see errors try looking them on Sneakyghost's thread found here
g) Once this is done and everything passed than we have successfully upgraded our firmware to Marshmallow... Since we selected the FULL STOCK WIPE option we need to flash TWRP once again (as it was wiped) and don't bother resetting or hoping for the phone to boot normally as it won’t...
(if you renamed the original file type its current name, by default it is as follows)
Type:
fastboot flash recovery twrp-2.8.7.0-hima.img
and once it’s done
adb reboot-bootloader
*if for any reason you need to reset your phone and gain access to the bootloader menu, download mode, recovery etc. you can always do this manually by holding vol up, vol down and power buttons at the same time for a few seconds to reset the device, to get into the bootloader, recovery, download mode etc. After the phone resets continue holding the vol down and power button until you reach the bootloader menu.
*if you type adb devices and you see multiple devices or emulators that prevent the commands from working I suggest running the following:
adb kill-server
adb devices
Now only your connected device should appear…
h) It is now time to enter our recently flashed recovery to finally install our latest ROM.
Enter the recovery manually or by typing
adb reboot recovery
From there you may select the wipe option (swipe to factory Reset) and proceed to the Install section, browse for your ROM file and select it.
i) Within Aroma installer select all your preferred options and begin to install, once the flashing completes your device should reboot and now you keep your fingers crossed and wait (will take several minutes so just be patient…. And DONE!!! You now have the latest Marshmallow firmware and ViperOneM9 ROM installed.
#Please note that I’m no expert when it comes to these matters, this guide is here to help anyone who is unsure what to do, I tried to write it up the best way possible (sorry that there are no fancy pictures) if there any errors or issues with my methods please feel free to correct them but so far they worked for me and hopefully will also work for you. (This guide will also help you flash other ROM's) If you need more help please feel free to ask, there is always someone here on xda who knows the answers 
Excellent write up !!
Many thanks !!!....g
glad i could help
GODSPD said:
glad i could help
Click to expand...
Click to collapse
Very nice writeup. Just got an M9 for the wife. I've been around the block so I get everything, but I've been away from HTC since the One X...well, there's the N9 but it's a nexus. What are the RUU mode and Download mode. If I remember correctly there was only the bootloader to go to on the One X. If it's complicated is there somewhere I can read about the modes?
Can you write instructions for s-on and unlocked boatloader? Thanks.
Sent from my HTC One M9 using Tapatalk
Excellent write-up! For extra-completeness, could you please cover changing the mid in android-info and dealing with error 22 (stuff about headers). I'm still fighting that one...
Thanks for your time.
CrazyRom said:
Excellent write-up! For extra-completeness, could you please cover changing the mid in android-info and dealing with error 22 (stuff about headers). I'm still fighting that one...
Thanks for your time.
Click to expand...
Click to collapse
PM sent, hope it helps.
zrzhu said:
Can you write instructions for s-on and unlocked boatloader? Thanks.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Have you received the official Marshmallow OTA yet on your device? the S-OFF method is available for those who don't want to wait for official updates, I will gladly write up a S-ON method once more people receive the official update...
GODSPD said:
PM sent, hope it helps.
Click to expand...
Click to collapse
Also try the following as error 22 was not covered in the error handling section...
http://forum.xda-developers.com/showpost.php?p=59783531&postcount=3
Download 7zip, open the zip inside of the program, right click on the Android text file and open within. Change the mid to yours hit save. It will ask if you want to update the zip, hit yes. Then try and flash.
SneakyGhosts post explains this:
Error 22 is new to me too but the string is kind of self explanatory: every archive has a header where the archive-program finds info about what type of archive and what compression. If the error says anything about this header, the logical conclusion is either a corrupted, broken archive or an unsupported archive type.
I suspect the latter simply due to the fact that the zip was unpacked and repacked, which then easily creates an incompatible zip.
GODSPD said:
Have you received the official Marshmallow OTA yet on your device? the S-OFF method is available for those who don't want to wait for official updates, I will gladly write up a S-ON method once more people receive the official update...
Click to expand...
Click to collapse
No, I've att m9. I'm still I viperone 3.5. Why do we need to wait for the official update?
Sent from my HTC One M9 using Tapatalk
zrzhu said:
No, I've att m9. I'm still I viperone 3.5. Why do we need to wait for the official update?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
because you need the latest firmware in order to install 4.x.x and the only way to get the latest firmware is via the OTA or by flashing it with the s-off method.
GODSPD said:
because you need the latest firmware in order to install 4.x.x and the only way to get the latest firmware is via the OTA or by flashing it with the s-off method.
Click to expand...
Click to collapse
Thanks. Hopefully ATT will release Marshmallow soon then.
Hi guys i dont have anymore pc. Can i flash new firmware without pc? Plz help
Can you put here your all c:\android folder in .zip file? Of course you can't put here all venom rom zip, but only all your files in that folder
BLEK0TA said:
Can you put here your all c:\android folder in .zip file? Of course you can't put here all venom rom zip, but only all your files in that folder
Click to expand...
Click to collapse
which exact files are you after, the android sdk?
thanks bro!! nice collection!
zrzhu said:
Thanks. Hopefully ATT will release Marshmallow soon then.
Click to expand...
Click to collapse
I'm still kind of "fuzzy" on this whole firmware thing.... IF I don't want to wait (on ATT) and IF I go S-OFF, which firmware can I/should I use for Marshmallow?
Delete
HI, can you please tel me how long does the firmware flash take as mine has been at it for over 2 hours? Not sure if it is stuck?
I am on sprint. How do i get the new firmware? It isnt on the list. Thank you

Anyone have the stock recovery image for Asus Zenfone 3 Zoom (ZE553KL)?

I newbed up my phone (soft bricked) and am trying to flash back to stock, but didn't think to save the stock recovery image before I flashed TWRP. Does anyone happen to have it for the ZE553KL? Or perhaps the stock firmware can be flashed through TWRP? I tried to flash via adb sideload, and it appeared to work, but that could be the totally wrong way.
Thanks!
Check the ROM somewhere here "convert CN to WW". There's a stock image in there with instructions how to sideload through ADB.
Thanks @magicmanfk!
The recovery.img is indeed in the ROM file attached to that thread. I extracted it and ran
Code:
fastboot flash recovery recovery.img
and it brought back the stock recovery. Then I was able to flash one of the older firmware files via
Code:
adb sideload UL-Z01H-WW-11.41.87.2-user-1.zip
and I'm back to stock. Now going to try to upgrade to N.
lirpa said:
Thanks @magicmanfk!
The recovery.img is indeed in the ROM file attached to that thread. I extracted it and ran
Code:
fastboot flash recovery recovery.img
and it brought back the stock recovery. Then I was able to flash one of the older firmware files via
Code:
adb sideload UL-Z01H-WW-11.41.87.2-user-1.zip
and I'm back to stock. Now going to try to upgrade to N.
Click to expand...
Click to collapse
Did you use that image for a US phone or other?
The image you used looks like the firmware on the Asus site dated 6/6/2017 so I guess the firmware there are full images and not patches like someone suggested???
I'm asking because I feel like I may want to go back to US version stock at some point and don't have a backup so if the above is the case then I probably don't need to ask someone for a backup...
Did you have any luck upgrading to N? When I try using the phone's normal procedure I get an error saying I can't upgrade to N from a firmware less current than 11.41.87.2 even though that's the one I'm running. After flaking back to stock recovery I was able to update to that one normally... I wonder if there was something subtle that went wrong.

Categories

Resources