Related
Just to confirm one thing before i go smoke my NS's warranty away. If i nand backup the current stock rom and then flash the custom roms...i can always easily flash back to stock rom no?
Yes it is pretty easy to restore to your current build from a backup
Also, there are threads with stock images for the different models of the Nexus S here on XDA detailing how to go back to stock if that's something you choose to do so later
jackslim said:
Yes it is pretty easy to restore to your current build from a backup
Also, there are threads with stock images for the different models of the Nexus S here on XDA detailing how to go back to stock if that's something you choose to do so later
Click to expand...
Click to collapse
but wouldn't just recovering to backup takes to stock rom? and i believe the root can be deleted right? so that if i plan to send back the phone, i can do that...i'm only flashing roms over the weekend so that i can see if the wifi problem is fixed with different kernels...
I can't get my router to be shown in the network list and other networks have poor wifi signals :/ i'm really worried...
Yes recovering from your backup will return you to a rooted stock, and you can remove root by deleting su from /system/xbin/
can you direct me to clockworkmod apk? since i don't want to flash the .img
The recovery image isn't an .apk file, you are going to have to flash the .img from fastboot to get clockwork recovery installed.
jackslim said:
The recovery image isn't an .apk file, you are going to have to flash the .img from fastboot to get clockwork recovery installed.
Click to expand...
Click to collapse
yes i know it's not an apk but i believe, clockwork can be installed as apk and then rebooted into the clockwork recovery through the application as my motorola defy...
i don't want to flash the .img file or i won't be able to remove it if i had to...
You can flash a recovery image from ROM Manger which will install a custom reocovery
**However**
ROM Manager needs root access to install a recovery image, so therefor you need to install root permission, which in turn requires a custom recovery to flash the zip file to install the necessary file.
So... flashing the recovery image from fastboot is a necessary step in rooting on this phone
so apps like z4root and universal root don't work for nexus s?
I'm honestly not sure what exploits work with the Nexus S personally, feel free to browse through the guides that are stickied
In my opinion if you already had the intention of unlocking the bootloader, then you'll already have fastboot setup and you will already be in the bootloader so it's just one additional command to type to get your recovery image installed, pretty easy
Since the Nexus S comes with a bootloader that can be unlocked I don't think anyone would look for an expoit that works specifically for this phone because, but exploits that were built for other phones may work on this one, again you would have to browse around to see, I'm not sure about this
my main purpose is to have an option to revert back the phone to its orignal state...unlocking bootloader would be permanent no? also if i flash clockwork, that would be permanent or is there an easy way (excluding ADB) to delete clockwork ?
shad0wboss said:
so apps like z4root and universal root don't work for nexus s?
Click to expand...
Click to collapse
This phone has an unlockable bootloader. You don't need exploits like that. Just follow the directions on this forum for your specific model and you will be fine. Everything you will do can be reversed. So don't worry.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
This phone has an unlockable bootloader. You don't need exploits like that. Just follow the directions on this forum for your specific model and you will be fine. Everything you will do can be reversed. So don't worry.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
read my previous post...unlocking bootloader will be permanent thus messing up with my warranty.
You can lock the bootloader on this phone, just use the following command in fastboot
fastboot oem lock
You would have to flash over the original recovery image from fastboot before relocking the bootloader
This phone can be returned to complete stock fairly easily, if you were to find all stock images for your particular model of the Nexus S you could completely return it to stock from fastboot with a few easy commands
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Just look through root/unroot guides and find the images for your model, you will need to do this to at least get the recovery image for when you decide to return to stock
jackslim said:
You can lock the bootloader on this phone, just use the following command in fastboot
fastboot oem lock
You would have to flash over the original recovery image from fastboot before relocking the bootloader
This phone can be returned to complete stock fairly easily, if you were to find all stock images for your particular model of the Nexus S you could completely return it to stock from fastboot with a few easy commands
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Just look through root/unroot guides and find the images for your model, you will need to do this to at least get the recovery image for when you decide to return to stock
Click to expand...
Click to collapse
sorry i'm not with you here...so you're suggesting me to unlock my bootloader, flash rom? so for these purposes i won't have to install root? so how can i backup my current rom?
haha also i can't install ADB drivers :/ although i can access the phone memory lol
Yes, if you want to install custom ROM's then you should unlock your bootloader and install a custom recovery, these are both reversible.
To help getting adb/fastboot drivers you can get PDAnet from:
http://junefabrics.com/android/index.php
Setting up PDAnet usually fixes the driver problem, you can uninstall it once it's done
I think you should read through an root/unroot guide pertaining to your model, sounds like that would answer a lot of concerns and doubts
But mainly since you are concerned about your warranty, unlocking the bootloader and rooting your phone is completely reversible.
shad0wboss said:
read my previous post...unlocking bootloader will be permanent thus messing up with my warranty.
Click to expand...
Click to collapse
I don't think you get it. Nexus S is a development phone and comes with a factory built-in unlocker. This means you do NOT void your warranty when unlocking or rooting.
It is however recommended that you return to stock and lock the bootloader before returning the phone for any warranty needs because most idiots at sprint stores or service centers don't know any better even though the rules clearly tell them they must service the Nexus S even if rooted.
Now, to answer your question, when you restore back to stock and close bootloader the phone is indistinguishable from factory settings and data. So no, the bootloader unlocking is NOT permanent.
On a side note, you will have to use the Samsung exe to restore your phone to factory settings along with locking the bootloader if you want the original recovery. But I think there is an img of the original available somewhere.
Also, to replace the recovery you MUST use adb. There is a one click to do that but all it does is do all the steps you would do manually and still needs all drivers installed.
Sent from my Nexus S 4G
obsanity said:
I don't think you get it. Nexus S is a development phone and comes with a factory built-in unlocker. This means you do NOT void your warranty when unlocking or rooting.
Click to expand...
Click to collapse
It clearly states while unlocking your bootloader that by doing so your warranty is voided.
While Sprint's policy is to in fact service unlocked/rooted phones this is not the case for all carrier's.
Returning or attempting to return a phone that is unlocked can very well have you turned away since your warranty is voided in many cases, especially depending on the carrier of the phone.
jackslim said:
It clearly states while unlocking your bootloader that by doing so your warranty is voided.
While Sprint's policy is to in fact service unlocked/rooted phones this is not the case for all carrier's.
Returning or attempting to return a phone that is unlocked can very well have you turned away since your warranty is voided in many cases, especially depending on the carrier of the phone.
Click to expand...
Click to collapse
When I unlocked my phone the first time I had NO such disclaimer. This was something added later with an update. Therefore I did not void my warranty and anyone else can argue the same.
Sent from my Nexus S 4G
obsanity said:
When I unlocked my phone the first time I had NO such disclaimer. This was something added later with an update. Therefore I did not void my warranty and anyone else can argue the same.
Click to expand...
Click to collapse
I'm pretty sure that the screen has always had the warranty information on it after you type "fastboot oem unlock" in fastboot and then you have to acknowledge the unlock on the phone. It was part of the original Nexus One unlock screen and I'm sure part of the unlock on Nexus S. Especially if you're on the NS4G which came out months after the original NS. I know I had to acknowledge it when I unlocked mine. It only makes sense that if you willingly unlock your device and flash something you shouldn't in example a radio for a different model and brick your device the manufacturer isn't responsible for your mistake.
So I have a ns4g that I attempted to root but got hung up and am now stuck with a unlocked bootloader but no super user. So as I see it I have 3 options (if you see others PLEASE TELL ME)
1. somehow get my bootloader locked again and go back to stock (unroot)
2. keep unlocked bootloader and eventually accept ics ota (will this be ok or will having an unlocked bootloader much things up with the ota?)
3. figure out a way to finish the root process I'm sort of in the middle of (aka get super user)
If it matters I am running 2.3.7 and using a macbook running 10.7.2
What would you guys suggest?
jmelick07 said:
So I have a ns4g that I attempted to root but got hung up and am now stuck with a unlocked bootloader but no super user. So as I see it I have 3 options (if you see others PLEASE TELL ME)
1. somehow get my bootloader locked again and go back to stock (unroot)
2. keep unlocked bootloader and eventually accept ics ota (will this be ok or will having an unlocked bootloader much things up with the ota?)
3. figure out a way to finish the root process I'm sort of in the middle of (aka get super user)
If it matters I am running 2.3.7 and using a macbook running 10.7.2
What would you guys suggest?
Click to expand...
Click to collapse
flash a custom recovery(cwm or twrp) via fastboot, then flash a custom rom(and gapps). thats all you need. all the custom roms out there have root. you dont have to flash superuser.
How do I flash cwm? I think when I did this before I had the wrong version as it didn't allow for me to mount after I unlocked the bootloader
Use http://forum.xda-developers.com/showthread.php?t=1250583 to root! It will recognize that your bootloader is already unlocked and skips to flashing CMW and giving you root! There's a youtube video showing it in action if you get stuck by qbking!
Will this work with osx?
jmelick07 said:
How do I flash cwm? I think when I did this before I had the wrong version as it didn't allow for me to mount after I unlocked the bootloader
Click to expand...
Click to collapse
heres the latest version of cwm recovery for the nexus s(not ns4G) http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-crespo.img
heres where all the cwm recoveries can be found, including the ns4g http://clockworkmod.com/rommanager
Ok, now how do I get that img on my phone?
The cwm for ns4g that I just downloaded that is
I'm fairly content just waiting for the google ics ota... when that comes will it mess my phone up because of my unlocked bootloader?
or even better can someone write me instructions to lock my bootloader?
I found this forum http://forum.xda-developers.com/showthread.php?t=875630
But obviously there are steps before this to have the terminal put these commands towards the phone.
jmelick07 said:
Ok, now how do I get that img on my phone?
The cwm for ns4g that I just downloaded that is
Click to expand...
Click to collapse
look at part 3 http://forum.xda-developers.com/showthread.php?t=1007782
only you dont need superuser, any custom rom has root.
Ok, I think I just want to relock my phone and wait for the ota...
I've tried just going into terminal and typing "fastboot oem lock" and it says that the command is not found... what did I do wrong?
You don't need to lock bootoader to get ota.
I've read before that accepting an ota with an unlocked bootloader will brick your phone... Can anyone else confirm that it's ok to accept the eventual ota with an unlocked bootloader?
I unlocked my MT4GS's bootloader a few months ago using HTC's tool, but I now find myself in a place where I need to reflash a stock ROM due to miscellaneous malfunctions. It's not for warranty/damage, I tried to restore my ROM to factory settings and couldn't due to removing the Sense UI for ADWLauncher. I tried to reflash my ClockWorkMod stock ROM backup, but it had a MD5 mismatch (and, sadly, was deleted accidently last night in organizing my SD card).
I am on an unlocked bootloader with S-ON RL showing on the boot screen. I have tried downloading one of the SG59IMG.zip files (both the latest 1.63 release, and the 1.55 release), but those do not work. I place them on my SD Card's root and allow HBOOT to find them, but it reports "Wrong ZIP!". I've read that re-locking my bootloader will fix this; any confirmation?
At this point, what I really want to do is get my phone back on a stock ROM, with or without ClockWorkMod, and start over again with the rooting process. As I said, this isn't for warranty service; I want to make sure I have a good stock recovery image available and that I have a solidly working phone while I wait for an ICS ROM that's stable for everyday use to come around.
Thanks in advance for any help.
WinterHalliwell said:
I unlocked my MT4GS's bootloader a few months ago using HTC's tool, but I now find myself in a place where I need to reflash a stock ROM due to miscellaneous malfunctions. It's not for warranty/damage, I tried to restore my ROM to factory settings and couldn't due to removing the Sense UI for ADWLauncher. I tried to reflash my ClockWorkMod stock ROM backup, but it had a MD5 mismatch (and, sadly, was deleted accidently last night in organizing my SD card).
I am on an unlocked bootloader with S-ON RL showing on the boot screen. I have tried downloading one of the SG59IMG.zip files (both the latest 1.63 release, and the 1.55 release), but those do not work. I place them on my SD Card's root and allow HBOOT to find them, but it reports "Wrong ZIP!". I've read that re-locking my bootloader will fix this; any confirmation?
At this point, what I really want to do is get my phone back on a stock ROM, with or without ClockWorkMod, and start over again with the rooting process. As I said, this isn't for warranty service; I want to make sure I have a good stock recovery image available and that I have a solidly working phone while I wait for an ICS ROM that's stable for everyday use to come around.
Thanks in advance for any help.
Click to expand...
Click to collapse
Get the stock recovery from the devs section, Change " SG59IMG.zip" to " PG59IMG.zip", relock the bootloader so that hboot will see the zip. I think the lock command is "fastboot oem lock". To unlock it again you would have to flash the unlock token again
Sent from my DoubleShot Lite using Tapatalk
ac3theone said:
Get the stock recovery from the devs section, Change " SG59IMG.zip" to " PG59IMG.zip", relock the bootloader so that hboot will see the zip. I think the lock command is "fastboot oem lock". To unlock it again you would have to flash the unlock token again
Sent from my DoubleShot Lite using Tapatalk
Click to expand...
Click to collapse
Whoops, it is PG59IMG already, just at work and wasn't in front of my phone at the time to confirm the file name. Is there a way to relock my bootloader without using the fastboot program from my computer? I've already uninstalled all of the HTC/ADB stuff to save processing power on my netbook and I'd like to avoid reinstalling it all if at all possible.
WinterHalliwell said:
Whoops, it is PG59IMG already, just at work and wasn't in front of my phone at the time to confirm the file name. Is there a way to relock my bootloader without using the fastboot program from my computer? I've already uninstalled all of the HTC/ADB stuff to save processing power on my netbook and I'd like to avoid reinstalling it all if at all possible.
Click to expand...
Click to collapse
Theres no other way that i know of sry
Sent from my DoubleShot Lite using Tapatalk
http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
That covers everything.
WinterHalliwell said:
... Is there a way to relock my bootloader without using the fastboot program from my computer? I've already uninstalled all of the HTC/ADB stuff to save processing power on my netbook and I'd like to avoid reinstalling it all if at all possible.
Click to expand...
Click to collapse
Ask and ye shall receive - I put together a package with the bare minimum you need to use ADB or fastboot. At about 736kb I think it's exactly what you were looking for.
(windows machine)
You don't need to install the entire SDK just to get the ADB or fastboot tools - all you need is what's here.
doubleshot_adb-fastboot.zip
Download Link
MD5: 47e72c0a2e2c1caaabd95b5df83e8913
Size: 736.03 KB
I also included a command prompt .bat file (Command.bat) so that when you unzip the archive to a folder, open that folder and double-click the Command.bat file and it will open you up to a command prompt already in the folder with the tools, wherever it is.
No more typing in some annoying CD command to get to the directory with the tools - simply open the folder (wherever it is at the time) and run Command.bat.
You will be ready to just dive right into ADB or fastboot commands (which is all you want, anyway, right?)
You will need the fastboot drivers for the doubleshot installed if they are not - get them here:
HTCDriver.exe
Download Link
MD5: 7fe1a01a816722718c6d369a3dc49166
Size: 13.08 MB
...and these are the same drivers that originally came on the SDcard of the doubleshot when you first got it. If you lost them, you can grab them again.
Enjoy!
Hi everyone, i'm new here as you can see... I had installed Android 4.2.1 CM10.1 Nightly ROM in the last 2-3 days but now I am to stock firmware, I've unrooted my device successfully after reading all the threads in this forum, BUT it seems that I can't find any method to download my original recovery kernel image because I can't install any new updates, it says: "Entering recovery kernel image" a loading bar appear under the android logo and after that an android logo with the red exclamation mark. I couldn't find any helpful information on how to bypass this error here in this forum so PLEASE HELP ME, I don't know what to do...I've spend almost 2 days trying to figure it out and nothing. THANK YOU IN ADVANCE and sorry for "my english".
When i put the device into fastboot mode and run the command "fastboot oem lock" i've got this message on the screen: "The system.img is not a official image"
I am assuming that no one knows... now i screwed up things and i deleted my recovery img, tablet doesn't enter recovery mode anymore. Please guys i'm begging you, i'm desperate...what should I do???
You cannot "re-lock" your bootloader once you have unlocked it. Although, a few users have has success re-locking it after installing certain ICS stock roms. You may have to try several ICS stock roms and get lucky.
You can get a stock recovery image for the 700/701 here in the dev forum. Just make sure you select the one for your OS. (ICS-JB). Don't mix them.
Typically, once you do OEM unlock, you will not be able to get OTA updates. 50-50
MD
Moscow Desire said:
You cannot "re-lock" your bootloader once you have unlocked it. Although, a few users have has success re-locking it after installing certain ICS stock roms. You may have to try several ICS stock roms and get lucky.
You can get a stock recovery image for the 700/701 here in the dev forum. Just make sure you select the one for your OS. (ICS-JB). Don't mix them.
Typically, once you do OEM unlock, you will not be able to get OTA updates. 50-50
MD
Click to expand...
Click to collapse
Thank you, i've made it reinstalling recovery image, everything working fine. From what I understand my warranty is gone, even if I install ICS they will know.
I can install updates but only manually...renaming file in update.zip but before modifying in "META-INF"...google...com the updater script the line with "assert prop".
Moscow Desire said:
You cannot "re-lock" your bootloader once you have unlocked it. Although, a few users have has success re-locking it after installing certain ICS stock roms. You may have to try several ICS stock roms and get lucky.
You can get a stock recovery image for the 700/701 here in the dev forum. Just make sure you select the one for your OS. (ICS-JB). Don't mix them.
Typically, once you do OEM unlock, you will not be able to get OTA updates. 50-50
MD
Click to expand...
Click to collapse
On the end of the update (flashing update.zip trough cwm) proces i got the question if i want to keep cwm recovery, when not stock was installed. (or am i confused?)
Hi All,
Of course the first thing I did after getting my new HTC One SV is root it and install LBE privacy protection to stop data leakage. However recently ive been getting a notification of an update to jelly bean through my phone provider (Vodafone Australia). However this will not install due to custom recovery image so the pre-install check fails. I cannot find stock recovery images anywhere and even if I did, due to presence of clockwork mod cant push images via Android SDK (skips straight past hboot to clockworkmod so isn't detected as an available device).
Can anyone help me get my phone back in a state where I can install the new update and the re-root?
Am not 100% noob, am familiar with custom roms and basics required to root and use SDK, this is my 3rd android device ive played with so hopefully this question is not tooooo SIGH.
Seems like HTC one SV is too new to have its on page in XDA support?
Try find here something or sombody who can help. http://forum.xda-developers.com/showthread.php?t=2292432
Wysłane z mojego HTC One SV
Not helpful
marceli-szpak said:
Try find here something or sombody who can help. http://forum.xda-developers.com/showthread.php?t=2292432
Wysłane z mojego HTC One SV
Click to expand...
Click to collapse
Hi there,
Unfortunately I don't have permission to post messages in that thread, nor does it seem the appropriate place to ask my question as it is an area for resources not help.
You must have 10 posts to write in some threads. Try ask in thread root for One sv. Have you bootloader unlocked ? What is your hboot number? For now when you update to JB via OTA you can't make s-off and next you can't back to previous hboot version.
Wysłane z mojego HTC One SV
RE HTC One SV Revert to Stock Help (for update)
marceli-szpak said:
You must have 10 posts to write in some threads. Try ask in thread root for One sv. Have you bootloader unlocked ? What is your hboot number? For now when you update to JB via OTA you can't make s-off and next you can't back to previous hboot version.
Wysłane z mojego HTC One SV
Click to expand...
Click to collapse
Yes bootloader is unlocked, I have clockworkmod working, in fact I think that is the problem. If I could get back to original recovery image I think the OTA would work
HBOOT number is 1.01.000
snorglamp said:
Yes bootloader is unlocked, I have clockworkmod working, in fact I think that is the problem. If I could get back to original recovery image I think the OTA would work
HBOOT number is 1.01.000
Click to expand...
Click to collapse
What you have to do is, download the OTA Update (will be located to sdcard/download/), copy to pc and unzip it. You will find another firmware.zip, there is the jelly bean recovery inside. Flash this JB recovery over fastboot.
Boot.img/Kernel also have to be stock and maybe bootloader also locked (for this i'm not sure), then you should be able to install JB.
But think about, if you need S-Off, cause you only get this on ICS.
old.splatterhand said:
What you have to do is, download the OTA Update (will be located to sdcard/download/), copy to pc and unzip it. You will find another firmware.zip, there is the jelly bean recovery inside. Flash this JB recovery over fastboot.
Boot.img/Kernel also have to be stock and maybe bootloader also locked (for this i'm not sure), then you should be able to install JB.
But think about, if you need S-Off, cause you only get this on ICS.
Click to expand...
Click to collapse
Thanks this sounds like the best advice I have had yet. MANY THANKS SIR!
However at the moment I have problems getting ADB/fastboot to recognise the phone is connected (using command line). Just says waiting for device and nothing happens. Is this because I have clockworkmod installed? I just got a new PC and installed latest ADB/SDK and latest HTC sync software so everything should be latest. I cant do much if I cant give commands unfortunately. If I solve this I will post an update.
snorglamp said:
Thanks this sounds like the best advice I have had yet. MANY THANKS SIR!
However at the moment I have problems getting ADB/fastboot to recognise the phone is connected (using command line). Just says waiting for device and nothing happens. Is this because I have clockworkmod installed? I just got a new PC and installed latest ADB/SDK and latest HTC sync software so everything should be latest. I cant do much if I cant give commands unfortunately. If I solve this I will post an update.
Click to expand...
Click to collapse
Can be related to cwm! Look into my index thread, there is a link to cwm with working adb or use TWRP2.5.
Good luck.
?????????????*
ismailnayir said:
?????????????*
Click to expand...
Click to collapse
If's there anything you don't understand, ASK!
So nobody knows, what you want, sorry.
old.splatterhand said:
Can be related to cwm! Look into my index thread, there is a link to cwm with working adb or use TWRP2.5.
Good luck.
Click to expand...
Click to collapse
Yes I thought that might be the case but was not having any luck with search results to find out what to do. Thank the internet gods for you! Going to your thread now XD!
I had similar issue with an update, the reason is that the stock recovery has some commands that neither cwm nor twrp have.
Here's what I did to fix it and update succesfully:
- extracted recovery.img from the update itself
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
- after that I was able to update without problems
note that you need to flash back twrp or cwm if you want root.
Of course you need unlocked bootloader, android-sdk's platform tools and adb drivers to do this, but you should already have them if you flashed cwm
good luck!
madpausa said:
I had similar issue with an update, the reason is that the stock recovery has some commands that neither cwm nor twrp have.
Here's what I did to fix it and update succesfully:
- extracted recovery.img from the update itself
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
- after that I was able to update without problems
note that you need to flash back twrp or cwm if you want root.
Of course you need unlocked bootloader, android-sdk's platform tools and adb drivers to do this, but you should already have them if you flashed cwm
good luck!
Click to expand...
Click to collapse
DUDE! THATS TOTALLY WHAT I WANNA HEAR, however, ive been having enormous trouble getting fastbood/ADB to recognise the phone is attached, I have tried the universal clockwork mod ADB driver which didnt work, and I havent had any luck folloing the instructions on Splatterhand's other threads in getting it recognised. The command fastboot devices just leaves a flashing cursor FOREVER! Other commands leave the message "waiting for device". According to splatterhand ADB/Fastboot wont recognise the phone as attached because of clockworkmod and therefore I cant push any commands or files...how did you solve this?
OMG
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhand for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!
snorglamp said:
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhead for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!
Click to expand...
Click to collapse
Just a thought, if you're upgrading from ics to jb, I think you should use ics recovery (I guess you can grab it from another ruu)... anyway, glad to be of any help
madpausa said:
Just a thought, if you're upgrading from ics to jb, I think you should use ics recovery (I guess you can grab it from another ruu)... anyway, glad to be of any help
Click to expand...
Click to collapse
So I took your advice and pulled a recovery image from the ICS Cricket (using the link in splatterhand's thread to stock resources) image. Downloaded the OTA and went to apply it, got past boot/recovery screen checks and all was looking good until i got to a screen with what looked to be an SD card icon and a loading bar under a larger phone icon with a green recycle type circle over it. That loading bar stopped about half way with a red triangle and exclamation mark (i.e. during the update process). Fortunately not bricked. It may be that I need the original Vodafone AU recovery image, or that there was something about the ICS OTA image that I used that made it fail. Not sure. Will try to find another stock recovery image.
Applied recovery from EU RUU stock and while that went fine and can boot into htboot no problem, when applying the OTA update it skips the fastboot and gets stuck on HTC One screen like normal loading except stuck.
I think I will try old.splatterhand's recommendation now that I am able to push things to the phone through adb/fastboot, so thanks for your commandline tip but now I must try flashing the JB recovery etc as outlined in his post.
The problem may be that the OTA is expecting a vodafone australia stock recovery as i seem to be getting different outcomes depending on which stock recovery image I apply...
I have sent Old.Splatterhand the Vodafone Australia JB OTA file for the main thread collection in case anyone wants it or the images therein, but at the moment it is of little use to me hehe.
SUCCESS! How to update to Jelly Bean from modded/rooted HTC One SV ICS
Ok so I should probably post this somewhere else so old.splatterhand can just post the summary. But here is what happened and a combination of your advice helped me so super thanks to both of you (madpausa and old.splatterhand)!
So I was in a situation where having rooted my stock HTC One SV and flashed clockworkmod I couldnt apply the Jellybean update that was constantly in my notifications bar (referred to as OTA update). When I tried to reboot into recovery clockworkmod would take over instantly and I was unable to run commands from fastboot command lines.
I was however able to download the update which could be found in (internal memory) "Downloads" folder "OTA_K2_UL_JB...zip".
In order to apply the advice of madpausa I had to first revert to stock recovery image before applying the recovery image from the OTA. So I got a stock recovery image from the cricket version (see old.splatterhand's thread) and flashed that first.
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc (select HTC Sync) and fire up the CMD interface for command line time (cd Android)
- command 'adb reboot bootloader' which actually did boot the phone into Hboot and not clockworkmod, so that solved the ADB/fastboot issue for me
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Once I had reverted to stock recovery I was then able to apply the rest of madpausa and old.splatterhand's advice
What finally worked for me was copying that OTA JB update zip to pc my and unzipping it. Inside there was firmware.zip, which also needed to be unzipped and inside is the jelly bean version recovery.img.
- put it in the same directory as fastboot program (and remove the other recovery.img or overwrite)
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Then when I booted up my phone again it asked me if wanted to download and install the update, which I did. The phone rebooted, update applied, all good!
Hboot did not have to be re-locked, so dont go as far as locking your phone again.
Thanks to everyone's help for this one, I am now a happy use of Jellybean on my previously modded HTC One SV...now to get superuser back and stock that data leakage with LBE again!!!
Good to see you got your problem sorted out!:highfive:
And the download of OTA was succesful, thanks!:good:
snorglamp said:
Ok so I should probably post this somewhere else so old.splatterhand can just post the summary. But here is what happened and a combination of your advice helped me so super thanks to both of you (madpausa and old.splatterhand)!
So I was in a situation where having rooted my stock HTC One SV and flashed clockworkmod I couldnt apply the Jellybean update that was constantly in my notifications bar (referred to as OTA update). When I tried to reboot into recovery clockworkmod would take over instantly and I was unable to run commands from fastboot command lines.
I was however able to download the update which could be found in (internal memory) "Downloads" folder "OTA_K2_UL_JB...zip".
In order to apply the advice of madpausa I had to first revert to stock recovery image before applying the recovery image from the OTA. So I got a stock recovery image from the cricket version (see old.splatterhand's thread) and flashed that first.
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc (select HTC Sync) and fire up the CMD interface for command line time (cd Android)
- command 'adb reboot bootloader' which actually did boot the phone into Hboot and not clockworkmod, so that solved the ADB/fastboot issue for me
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Once I had reverted to stock recovery I was then able to apply the rest of madpausa and old.splatterhand's advice
What finally worked for me was copying that OTA JB update zip to pc my and unzipping it. Inside there was firmware.zip, which also needed to be unzipped and inside is the jelly bean version recovery.img.
- put it in the same directory as fastboot program (and remove the other recovery.img or overwrite)
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Then when I booted up my phone again it asked me if wanted to download and install the update, which I did. The phone rebooted, update applied, all good!
Hboot did not have to be re-locked, so dont go as far as locking your phone again.
Thanks to everyone's help for this one, I am now a happy use of Jellybean on my previously modded HTC One SV...now to get superuser back and stock that data leakage with LBE again!!!
Click to expand...
Click to collapse
This is the exact problem I had. I started trying to root my HTC One SV (Boost Mobile) a couple of months ago. I got past the HTC unlock bootloader, but I got confused by the rest of the rooting guide, so eventually I gave up on finishing the rooting process. Ever since then, it has said ***TAMPERED*** in hboot when I go in there. Well, just like you, I started getting the JB update notification in the OTA. I tried to install it like 15 times, but it always just rebooted into the existing image I had, which was the stock image.
So today I decided to try and finish the root and then find a JB ROM to install. old.splatterhand helped me out with getting it rooted, and it was a success. But when I asked him about JB ROMs, he said I had to have S-off. When we spoke a little more about it, he pointed me here, telling me that he helped you get the root back after you got through the OTA update.
So now, I guess I need to try and follow your instructions on getting the OTA update, and then go back to the thread where he helped you get the root back.
I'm a complete n00b to rooting android devices, but I'm pretty confident that I can do this with the proper guidance. I have rooted 2 Samsung SCH-i500s and today I finally got this HTC One SV rooted. I'm starting to see how it all works.
If you don't mind, let me know of any details of issues you faced that may not be in the guides you followed. That would be a great help.
Congrats on getting yours all done.
Thanks.
---------- Post added at 07:32 PM ---------- Previous post was at 07:15 PM ----------
snorglamp said:
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhand for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!
Click to expand...
Click to collapse
Do you type "adb reboot bootloader" in the command line? I wanna be clear on this before I make any moves.