Related
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
I'm having the exact same problem with a GT-i9020 so would be interested in any help on this!
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Highl1 said:
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Click to expand...
Click to collapse
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
I'll wait for your link and instructions, it's obvious that I am doing something wrong
Thanks mate!
RANDYRKELLY said:
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
But I have stock recovery and can't copy anything to internal memory, since my phone doesn't boot
Highl1 said:
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
Click to expand...
Click to collapse
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
surdu_petru said:
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
Click to expand...
Click to collapse
Same thing mate, I ran it, click two times in console, can't unlock the bootloader, I always get stuck on it
Trying to update the drivers for Nexus S : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
and after that try to run.bat...Good luck!
I'll try today, but my problem is that adb cannot find the device, fastboot can
I would try downloading the full OTA from this thread, rename it to update.zip (for easy typing), place it in a directory where you can run fastboot, then use the command:
Code:
fastboot update update.zip
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Is the problem solved?
szk5230 said:
Is the problem solved?
Click to expand...
Click to collapse
Not so far, I'm still having trouble with the phone, and no solution so far helped
Highl1 said:
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Click to expand...
Click to collapse
Sorry my bad, haven't tried that before either...
If it bugs you the bootloader isn't unlcoked before flashing can't you just use
fastboot oem unlock
then commence with flashing your stock image?
Edit - Nevermind...I see you tried that.
any other suggestion? I'm out of ideas
I had this problem in December. I tried everything you tried without any luck so eventually took it back for warranty repair. Unfortunately I had some water damage from 9 months before so they wouldn't touch it. Luckily I got it replaced on my phone insurance but they said it couldn't repaired.
As far as I know it's a hardware fault. With CWM it looked like I could transfer files into the sd but they would disappear! I was able to use Fastboot and Odin but no joy. I had the same errors when trying to apply update using fastboot and never found answers about the "missing" files.
Sorry to come with bad news and good luck! I'm worried it'll happen to my replacement handset so keen to know if you resolve it.
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
http://www.filefactory.com/file/c0f....00_11.16.3504.20_2_release_227956_signed.zip
Click to expand...
Click to collapse
Download the CWM recovery image:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.7-doubleshot.img
Click to expand...
Click to collapse
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Here's a pointer to restoring your phone to stock, courtesy of blue:
http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
So if we've gotten this far, is S-OFF going to gain us anything more? Are we still locked out of certain areas? The tool worked for me, but I'm using the rest of your guide to flash CWM. Thanks for writing it!
xzuhto said:
So if we've gotten this far, is S-OFF going to gain us anything more? Are we still locked out of certain areas? The tool worked for me, but I'm using the rest of your guide to flash CWM. Thanks for writing it!
Click to expand...
Click to collapse
In my opinion, S-Off won't really gain you much more. You'll have to flash kernels separately when flashing ROMs, but that doesn't seem to be a big deal (IMO).
You could probably flash back to the original release software if you wanted, and gain S-OFF with revolutionary, but I haven't tried that and have no idea if it will work.
The only thing you can't do with Unlocked/S-ON is flash radios.
Well in that case this phone is right where I want it. I've never messed with kernels on any phone I've had previously nor have I messed with flashing radios. I just got done completing the steps and I'm now root along with CWM. Great work throwing this up for everyone.
jonnycat26 said:
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
Download the CWM recovery image:
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Click to expand...
Click to collapse
the doubleshot img downloads painfully slow, do you have another link?
edit: also i think you missed somthing here"
[*]Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
"
ac3theone said:
the doubleshot img downloads painfully slow, do you have another link?
...
Click to expand...
Click to collapse
Well, where football is hosting the new PG59IMG.zip file is the only place we have it - i just found it yesterday and we haven't had time to up it anywhere else yet.
We are working on making mirrors for it now - give us some time to get set up with our new data.
---------- Post added at 01:38 AM ---------- Previous post was at 01:33 AM ----------
jonnycat26 said:
In my opinion, S-Off won't really gain you much more. You'll have to flash kernels separately when flashing ROMs, but that doesn't seem to be a big deal (IMO).
You could probably flash back to the original release software if you wanted, and gain S-OFF with revolutionary, but I haven't tried that and have no idea if it will work.
The only thing you can't do with Unlocked/S-ON is flash radios.
Click to expand...
Click to collapse
No, you can't go back to retail factory if you are S-ON. This new PG59IMG.zip I found is the furthest back you can go completely.
With S-ON you cannot replace hboot, or radio - those two are a big deal - i'm still working on an S-OFF solution for S-ON people with hboot 1.45.0013.
With S-OFF I can swap out hboots on a whim, and thrice43 even flashed a Sensation hboot to his doubleshot and it worked out for him - but with S-ON you cannot do this. (and if you could, you would brick)
S-OFF is very much preferable to S-ON UNLOCKED.
I've also had problems flashing OTA updates through stock recovery manually when S-ON where I had no trouble doing so while S-OFF.
There are still a lot of things you can't do with your device while S-ON.
EDIT:
also, all the PG59IMG.zip files I made for people to flash recoveries, hboots, and so on in the dev reference sticky cannot be used by anyone S-ON because they fail the signature checks. My custom PG59IMG.zip files don't have an HTC signature which you must have for an S-ON device to load the PG59IMG.zip file.
...so there are a number of reasons why S-OFF is something to get.
xzuhto said:
Well in that case this phone is right where I want it. I've never messed with kernels on any phone I've had previously nor have I messed with flashing radios. I just got done completing the steps and I'm now root along with CWM. Great work throwing this up for everyone.
Click to expand...
Click to collapse
You must flash a kernel if you want to flash an ICS ROM or any GB ROM with a modified kernel.
Also:
Here's a faster mirror, hopefully: http://www.4shared.com/zip/vVHQuid0/PG59IMG_Doubleshot_TMOUS_15553.html
I see the downsides to s-on but I'm happy to have root and cwm. I will however be excited to get this thing fully unlocked. I won't be messing with custom roms till then. lol
Sent from my myTouch_4G_Slide using Tapatalk
I managed to host it on my Dropbox
Edit:
Oh sorry Lime, I didn't see that you were already hosting it...
this might deserve a sticky?
If anyone is going to mirror it please keep the original filename - we have more then one PG59IMG.zip file with an HTC signature (retail launch and this one).
If they are not named including the software version and radio then people may be confused on what they are getting - thanks guys!
it worked, now to get su. thanks for the guide
delete post
jonnycat26 said:
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
Download the CWM recovery image:
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Click to expand...
Click to collapse
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
fastboot flash recovery recovery.img
Cant do this last few steps.Don't understand what to do as yet
Scondrel said:
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
fastboot flash recovery recovery.img
Cant do this last few steps.Don't understand what to do as yet
Click to expand...
Click to collapse
You need to transfer the recovery image to the directory with your fastboot.exe file.
You would then need to rename it to recovery.img
Then you boot your phone into fastboot mode, and plug it into the computer.
Open a command prompt, and navigate to the directory with fastboot.exe and run the command:
fastboot flash recovery recovery.img
Thanks got it now.Appreciate the help
---------- Post added at 01:23 AM ---------- Previous post was at 12:53 AM ----------
Scondrel said:
Thanks got it now.Appreciate the help
Click to expand...
Click to collapse
Didn't work for me,I all the way to final step, but once i enter recovery for CWM,and try to flash the superuser file or anything else, it just shows the icon and nothing else happens.Once i click the power button it goes back to the CWM Home screen.Any advice on this guys ?
Scondrel said:
Thanks got it now.Appreciate the help
---------- Post added at 01:23 AM ---------- Previous post was at 12:53 AM ----------
Didn't work for me,I all the way to final step, but once i enter recovery for CWM,and try to flash the superuser file or anything else, it just shows the icon and nothing else happens.Once i click the power button it goes back to the CWM Home screen.Any advice on this guys ?
Click to expand...
Click to collapse
You are using the trackpad to "select" within CWM, not the power button, right?
jonnycat26 said:
You are using the trackpad to "select" within CWM, not the power button, right?
Click to expand...
Click to collapse
Thanks it was 'nt that. There wasn't enough space on the memory card and I didn't have USB debugging on.Got it solved now .Thanks for the speedy responses.Truly appreciated .Feels so good to be a part of this community.
jonnycat26 said:
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
Download the CWM recovery image:
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Click to expand...
Click to collapse
These instructions worked perfectly! Can not believe it worked. This should be stickied! Thank you.
tbalden said:
this might deserve a sticky?
Click to expand...
Click to collapse
revo420 said:
This should be stickied!
Click to expand...
Click to collapse
Eh, why not. Done .
Hi all. Ive finally managed to get a grasp of the principles of adb, shell, fastboot, etc.
Anyways - I have a Desire S which I unlocked via htcdev, and installer the lastest clockworkmod recovery. ive been trying to get S-off and nothing has worked for me. Ive spent the last 2 days downloading so much stuff my desktop if full of it - and im nowhere.
I had ICS for htc running before without any mods and wanted to try the root / mod thing.
My phone hangs at the htc boot screen. I have tried installing 3 different cw10.1 zip files all from xda to no avail, they always give me an error. Ive tried running the RUU exe and it ends in an error. I then fund the rom.zip file in the directory and renamed it to PB99IMG.zip, dropped it in root of sdcard and nothing.. it just skips past the lines and goes to fastboot. Should it not be named PB88IMG.zip? I recall seeing those numbers flit past.
Is it possible to force the bastard phone to take cwm this way by renaming the zip? (Ive read no - its only for official RUU's).
anyway - the oneclick didnt work, nor did ver1, ive tried various shell methods (which i cant even recall). Im currentlyunlocked, S-ON, firmware 20.2.2000 or something (the one that revolutionary WONT work on).
Ive been chasing my tail and just gave up.
please give me some info as to what i could have dobe wrong. I installed clockwork via lpay store. I factory reset, cleared caches and batt logs and was able to go into the OS a few times - but obviously one of the methods i tried did something.
thanks again great forum, but honestly, what a complete mess!! there are so many approaches with so many pitfalls its crazy.. esp for a noob when the noob apps dont work either!
HTC Desire S GSM
unclocked via htcdev
S-ON
hboot: 2.02.0002
Radio: 3831.19.00.110
Latest CMWR
Gets stuck @ white screen
Tried:
factory reset / wipe / dalvik / batt stats
reboot to recovery: install SU, gapps, cwm rom 10.1 (also tried 7.1). reboot / then fastboot boot boot.img (from the CWM zip). nothing.
Ive tried re installing the EU RUU - also nothing. Renaming the rom.zip to PG**IMG.zip, it reading the file then stops 2 fastboot screen. nothing. nada.zip.
fstarockr said:
Hi all. Ive finally managed to get a grasp of the principles of adb, shell, fastboot, etc.
Anyways - I have a Desire S which I unlocked via htcdev, and installer the lastest clockworkmod recovery. ive been trying to get S-off and nothing has worked for me. Ive spent the last 2 days downloading so much stuff my desktop if full of it - and im nowhere.
I had ICS for htc running before without any mods and wanted to try the root / mod thing.
My phone hangs at the htc boot screen. I have tried installing 3 different cw10.1 zip files all from xda to no avail, they always give me an error. Ive tried running the RUU exe and it ends in an error. I then fund the rom.zip file in the directory and renamed it to PB99IMG.zip, dropped it in root of sdcard and nothing.. it just skips past the lines and goes to fastboot. Should it not be named PB88IMG.zip? I recall seeing those numbers flit past.
Is it possible to force the bastard phone to take cwm this way by renaming the zip? (Ive read no - its only for official RUU's).
anyway - the oneclick didnt work, nor did ver1, ive tried various shell methods (which i cant even recall). Im currentlyunlocked, S-ON, firmware 20.2.2000 or something (the one that revolutionary WONT work on).
Ive been chasing my tail and just gave up.
please give me some info as to what i could have dobe wrong. I installed clockwork via lpay store. I factory reset, cleared caches and batt logs and was able to go into the OS a few times - but obviously one of the methods i tried did something.
thanks again great forum, but honestly, what a complete mess!! there are so many approaches with so many pitfalls its crazy.. esp for a noob when the noob apps dont work either!
Click to expand...
Click to collapse
There are so many people, blindly walking in to troubles just because they do not read,
and you seem to be one of them....
When you unlock your device via htc dev, your device stays s- on,
it means- whatever you flash, you have to flash boot.img from that thing ( meaning rom naturaly )
via fastboot
through command:
fastboot flash boot boot .img
Without it your phone will never boot...
Recovery you flash via fastboot as well via command:
fastboot flash recovery recovery.img
Then , when you have it, reboot your device to recovery
and flash superuser and its binaries
And that woud be all you have to do in order to have rooted and booting device...
Edit: Now i've seen your other post- it is a 100% the one im reading now,
You should know it is enough to post your question once,
people'll find it...
Because of impatience you're in trouble already with your phone
tx -
tx for that info - ill give it a go.
I reposted because some1 there said i was in the wrong section and supplied a link for the correct section (here) - so yes, i reposted to get the correct replies.
not to digress:
but as for not reading - i can assure u ive read alot. Been a freelance developer for 15 years. That doesnt mean that rooting often requires a handful of little hacks when things dont go smooth. Just like alot of programming tuts, the rooting ones have a similar "assumption" that u know whats half potting, and what will cause what and what wont. All the articles i read i made sure were either 2012 or 2013 - there is ALOT of old non applicable info around, I stick to xda of course as i really trust this place. as usual, not all is 1-2-3. thats all.
asgardr said:
There are so many people, blindly walking in to troubles just because they do not read,
and you seem to be one of them....
When you unlock your device via htc dev, your device stays s- on,
it means- whatever you flash, you have to flash boot.img from that thing ( meaning rom naturaly )
via fastboot
through command:
fastboot flash boot boot .img
Without it your phone will never boot...
Recovery you flash via fastboot as well via command:
fastboot flash recovery recovery.img
Then , when you have it, reboot your device to recovery
and flash superuser and its binaries
And that woud be all you have to do in order to have rooted and booting device...
Edit: Now i've seen your other post- it is a 100% the one im reading now,
You should know it is enough to post your question once,
people'll find it...
Because of impatience you're in trouble already with your phone
Click to expand...
Click to collapse
Well thats true, obvious things for me do not have to be obvious for
somebody else- one sometimes forgets that- begging your pardon
If not for XDA, i'd've known not much at all...
I've given the shortest and simpliest way that never failed me before
so, i truly hope, for you it'll turn out to be usefull as well- with no further accidents...
As for comming back to stock: you must relock device's bootloader before flashing,
otherwise procedure will always be throwing an error....
Success
details details
As for coming back to stock: you must relock device's bootloader before flashing,
otherwise procedure will always be throwing an error....
Im trying to get a picture of the inter relations ~ pls bear with me:i dont want to be trying to sys c: when i dont have a partition kind of scenario - absolute clarity is needed - my apologies as i try wrap this up..
#bootloader:
do the same rules apply for ALL installations? Does bootloader have to be locked FOR anything to boot or just the stock OS's? does it have to be in a sequence - ie do i have to do this each time i try install an OS or can i leave it? Will this break the booting if its wrong? Can i use a bootloader from company X and a rom from company Y? What files do i use/extract/where do i get them, and are they device specific - what r the base requirements?
#S-on/Off
I have been unable to get mine to off -
#unlocked bootloader
its been indicated that this will throw off a stock OS installer, will cyanogenmod work with this off?
#RUU / Mods
I assume these are the OS's - do i have to do this last/middle? and steps after? to duplicate: are they linked to the bootloader?
#recovery
this is just an upgrade to the stock junk and has no effect on booting, etc. can be left in place if working. can install via play or fastboot via zip. (and other methods im sure).
Im trying to figure out what i can do once, and what i have to keep fiddling with, so i can hone in and get up and running.
If my questions appear ignorant - then ignore me. Im trying to paint a very clear picture of the tech relations between the various aspects and how they relate / interact - which is crucial to moving on from noobness - so pls bear with me and drop the remarks / attitude. Ive read my a$$ off and am still unclear for what many assume is basic understanding.
Im sure there are ALOT of sane unlazy logic ppl out there stuck in the same boat - and sometimes ppl who are VERY knowledgeable get a bit semi-aggressive putting ppl off from asking questions.
So do i relock the bootloader before i install any mod - or is this for stock only? And do install stock first, or can i relock and follow the steps above to root / get cwm 10.7 or 7.1 running?
lastly - where do i get the boot.img from? is that device specific or can i extract it / dl it? reason im asking is because it appears this file is device specific - and needs to be backed up from stock device before rooting/unlocking etc?
Success[/QUOTE]
fstarockr said:
Hi all. Ive finally managed to get a grasp of the principles of adb, shell, fastboot, etc.
Anyways - I have a Desire S which I unlocked via htcdev, and installer the lastest clockworkmod recovery. ive been trying to get S-off and nothing has worked for me. Ive spent the last 2 days downloading so much stuff my desktop if full of it - and im nowhere.
I had ICS for htc running before without any mods and wanted to try the root / mod thing.
My phone hangs at the htc boot screen. I have tried installing 3 different cw10.1 zip files all from xda to no avail, they always give me an error. Ive tried running the RUU exe and it ends in an error. I then fund the rom.zip file in the directory and renamed it to PB99IMG.zip, dropped it in root of sdcard and nothing.. it just skips past the lines and goes to fastboot. Should it not be named PB88IMG.zip? I recall seeing those numbers flit past.
Is it possible to force the bastard phone to take cwm this way by renaming the zip? (Ive read no - its only for official RUU's).
anyway - the oneclick didnt work, nor did ver1, ive tried various shell methods (which i cant even recall). Im currentlyunlocked, S-ON, firmware 20.2.2000 or something (the one that revolutionary WONT work on).
Ive been chasing my tail and just gave up.
please give me some info as to what i could have dobe wrong. I installed clockwork via lpay store. I factory reset, cleared caches and batt logs and was able to go into the OS a few times - but obviously one of the methods i tried did something.
thanks again great forum, but honestly, what a complete mess!! there are so many approaches with so many pitfalls its crazy.. esp for a noob when the noob apps dont work either!
HTC Desire S GSM
unclocked via htcdev
S-ON
hboot: 2.02.0002
Radio: 3831.19.00.110
Latest CMWR
Gets stuck @ white screen
Tried:
factory reset / wipe / dalvik / batt stats
reboot to recovery: install SU, gapps, cwm rom 10.1 (also tried 7.1). reboot / then fastboot boot boot.img (from the CWM zip). nothing.
Ive tried re installing the EU RUU - also nothing. Renaming the rom.zip to PG**IMG.zip, it reading the file then stops 2 fastboot screen. nothing. nada.zip.
Click to expand...
Click to collapse
i think u have MDDI pannel (not the one compatible with cianogen) try to flash a sense rom
have a look of THIS
Hi
#bootloader:
do the same rules apply for ALL installations? Does bootloader have to be locked FOR anything to boot or just the stock OS's? does it have to be in a sequence - ie do i have to do this each time i try install an OS or can i leave it? Will this break the booting if its wrong? Can i use a bootloader from company X and a rom from company Y? What files do i use/extract/where do i get them, and are they device specific - what r the base requirements?
Click to expand...
Click to collapse
On HTC devices, the bootloader is called HBOOT. This is a 100% device-specific program whose sole purpose is to initialize the hardware so that an operating system (such as Android, i.e. Linux) can load. If your bootloader is damaged, your device is 100% bricked.
To prevent tampering with the system, HTC have locked ("S-ON") their bootloaders so that they won't accept unsigned ROM images. So, on your HTC phone, you cannot install any operating system other than what's provided by HTC. You can partially lift these restrictions by unlocking via htcdev, as you have, or you can fully lift all restrictions on your device by going S-OFF. S-OFF-ing the Desire S is done by exploiting a bug in HBOOT version 0.98 and overwriting the bootloader with a patched version ("Revolutionary") that has all write protection disabled.
In order to flash official HTC upgrade packages ("RUU"s), you can be either S-ON or S-OFF, but if you're S-ON you MUST lock the bootloader. Anything that's not a RUU can (only) be flashed without re-locking the bootloader.
Having an unlocked bootloader is only relevant when flashing new ROMs or recoveries. Having an unlocked or locked bootloader per se will not affect booting at all, with one well-known exception: if you're S-ON and htcdev unlocked, the write protection installed by the bootloader is still on for the bootloader, radio, and kernel partitions. This means that you can't flash kernels from a running OS -- only from the bootloader. This means that when you flash a custom ROM, it will not be able to flash the kernel automatically, you have to do that manually via fastboot. Failing to do that will result in your phone freezing on the white HTC screen when it tries to boot.
#S-on/Off
I have been unable to get mine to off -
Click to expand...
Click to collapse
That's expected, because you're most likely not running a ROM that has a HBOOT version that is vulnerable to the exploit used by Revolutionary.
edit: nope, your HBOOT is newer than 0.98 and is therefore not exploitable.
#unlocked bootloader
its been indicated that this will throw off a stock OS installer, will cyanogenmod work with this off?
Click to expand...
Click to collapse
Only official HTC RUUs require that the bootloader be locked.
Cyanogenmod can only be installed with the bootloader unlocked, but you may always re-lock after installing it. Remember to manually flash the boot.img (that's the kernel) via fastboot directly after flashing CM through your custom recovery.
#RUU / Mods
I assume these are the OS's - do i have to do this last/middle? and steps after? to duplicate: are they linked to the bootloader?
Click to expand...
Click to collapse
A RUU is a *complete* software package for your device made by HTC. It contains everything from bootloader to operating system. I don't really know what else you're trying to ask, so please elaborate.
#recovery
this is just an upgrade to the stock junk and has no effect on booting, etc. can be left in place if working. can install via play or fastboot via zip. (and other methods im sure).
Click to expand...
Click to collapse
The recovery is a specialized mini-Android OS that allows you to flash new software (such as unofficial ROMs such as CM) to your device. What recovery you have installed has no bearing on your main OS. If you're htcdev unlocked, the only way you can install a custom (i.e. non-stock and non-crippled) recovery is via fastboot; if you're S-OFF you can use the 4EXT updater app from Google Play.
So do i relock the bootloader before i install any mod - or is this for stock only? And do install stock first, or can i relock and follow the steps above to root / get cwm 10.7 or 7.1 running?
Click to expand...
Click to collapse
Why do you want to install stock?
lastly - where do i get the boot.img from? is that device specific or can i extract it / dl it? reason im asking is because it appears this file is device specific - and needs to be backed up from stock device before rooting/unlocking etc?
Click to expand...
Click to collapse
boot.img is inside the zip of the ROM you're going to flash.
I hope I've been able to answer most of your questions. If you require more help, please search first, and if you can't find what you're looking for, please do ask.
fstarockr said:
Im trying to get a picture of the inter relations ~ pls bear with me:i dont want to be trying to sys c: when i dont have a partition kind of scenario - absolute clarity is needed - my apologies as i try wrap this up..
#bootloader:
do the same rules apply for ALL installations? Does bootloader have to be locked FOR anything to boot or just the stock OS's? does it have to be in a sequence - ie do i have to do this each time i try install an OS or can i leave it? Will this break the booting if its wrong? Can i use a bootloader from company X and a rom from company Y? What files do i use/extract/where do i get them, and are they device specific - what r the base requirements?
#S-on/Off
I have been unable to get mine to off -
#unlocked bootloader
its been indicated that this will throw off a stock OS installer, will cyanogenmod work with this off?
#RUU / Mods
I assume these are the OS's - do i have to do this last/middle? and steps after? to duplicate: are they linked to the bootloader?
#recovery
this is just an upgrade to the stock junk and has no effect on booting, etc. can be left in place if working. can install via play or fastboot via zip. (and other methods im sure).
Im trying to figure out what i can do once, and what i have to keep fiddling with, so i can hone in and get up and running.
If my questions appear ignorant - then ignore me. Im trying to paint a very clear picture of the tech relations between the various aspects and how they relate / interact - which is crucial to moving on from noobness - so pls bear with me and drop the remarks / attitude. Ive read my a$$ off and am still unclear for what many assume is basic understanding.
Im sure there are ALOT of sane unlazy logic ppl out there stuck in the same boat - and sometimes ppl who are VERY knowledgeable get a bit semi-aggressive putting ppl off from asking questions.
So do i relock the bootloader before i install any mod - or is this for stock only? And do install stock first, or can i relock and follow the steps above to root / get cwm 10.7 or 7.1 running?
lastly - where do i get the boot.img from? is that device specific or can i extract it / dl it? reason im asking is because it appears this file is device specific - and needs to be backed up from stock device before rooting/unlocking etc?
Click to expand...
Click to collapse
# bootloader
The bootloader must be locked to install an RUU (stock rom), it must be unlocked to install a custom rom.
# s-on / s-off
If you unlock your bootloader through htcdev.com, the phone stays s-on. This means you can't install a different radio or hboot (mostly not necessary anyway), or write to the /boot partition or recovery apart from in fastboot.
That means, after every rom installation, you have to reboot to bootloader (fastboot), and flash the boot.img (extracted from the rom you installed)
# recovery
A custom recovery is a must for flashing custom roms (it's where you flash the zips) , I recommend 4ext, other known recoveries are Cwm and twrp. Be aware that you can only flash recoveries in fastboot (not through an app) , if your device is s-on
1.s-off means you can flash anything you want to all partitions on the phone..
S- on (htc dev unlocked) bootloader is unlocked so you gain acces to system partition,
but neither to radio partition nor bootloader itself, so you cannot freely change them at will.
While flashing rom via recovery, ( when s-on) each time you'll have to flash boot.img of that rom -via fastboot as well, because kernel partition is not reachable from recovery ,
Boot img is to bo found in the rom zip ( namely boot.img).
and is absolutely necessary to flash that particular one
or, if existing- other that is compatible with rom of you choice and phone model..
Assuming- to flash any custom:
-bootloader has to be unlocked
-you need custom recovery ( 4ext or clockworkmod)
-rom is packed in zip format ( flashing via recovery)
-each time you change roms, you have to flash boot img of that particular rom,
( to be found inside that rom.zip)
from recovery must reboot to bootloader (adb reboot bootloader)
then flash boot.img...
If it says ok you may now begin booting in to system
Recovery:
To flash anything like roms or mods etc.
custom recovery is required,
stock htc recovery is been there for slightly different purpose,
and is, well.. rather useless for any device customizing...
1.when s-on: is necessary to flash recovery via fastboot-as an < .img > file
so, when it is zipped- extract the file: xxxyy_recovery .img,
change its name just to recovery.img, and flash it...
2.when s-off : is possible to update it via market app (but only when s-off)
RUU: is a stock phone image, and ussualy contains radio and bootloader itself,
flashing it, may upgrade your device's components that normally -while s-on-
you'd not be able to touch, but there is a price:
1.you must relock bootloader: fastboot oem lock
otherwise you'll always be getting an error
(but if you still keep unlock_token from htc dev-can unlock it again)
2.you must establish
A) your device's CID - Customer IDentification number (whether is generic or carrier branded)
B) your phone's software version region ( wwe or asia or..etc)
C) software version ( froyo, gb, ics )
because, normally bootloader will not let you flash lower RUU version
than itself,
( every RUU contains bootloader, so the one working on the device
will never let downgrade itself- well not without a little trick of course-this is XDA)
Bootloader:
It is advised to use only bootloaders for your device- if you try to flash something slse,
you'll end up with a dead phone ( no fastboot no nothing- paperweight)
While s-on you cannot upgrade bootloader in any other way but by flashing official RUU...
While s-off it is possible to write to bootloader partition ( but always a bit risky)
There are:
- stock bootloaders
- patched ( revolutionary )
- eng bootloaders ( modified - possible to overwrite it by different one in case it is necessary)...
...well... now, there is much more to it if one wants to know everything
if there is something you'd like to know in particular- write back...
fantastic answers and explanations last 3 chaps!!!!
Guys - excellent answers thank you SO much! i have a MUCH better idea now thanks to your no attitude clear answers! I think this should be a sticky as it clears SOOO much confusion for a multitude of users - and fills the forums with the same problems over and over - simply because ppl lack this base understanding b4 opening the darn prompt lol (like me!!)
So to recap"
While flashing rom via recovery, ( when s-on) each time you'll have to flash boot.img of that rom -via fastboot as well, because kernel partition is not reachable from recovery ,
Click to expand...
Click to collapse
so by following these directions:
Assuming- to flash any custom:
-bootloader has to be unlocked
-you need custom recovery ( 4ext or clockworkmod)
-rom is packed in zip format ( flashing via recovery)
-each time you change roms, you have to flash boot img of that particular rom,
( to be found inside that rom.zip)
from recovery must reboot to bootloader (adb reboot bootloader)
then flash boot.img...
If it says ok you may now begin booting in to system
Click to expand...
Click to collapse
im basically working around the S-On / kernel & partition issue i take it?
Im gonna try all this now - reason i wanted to flash stock
Why do you want to install stock?
Click to expand...
Click to collapse
is so that i can apply the earlier exploits to gain S-Off - but ill try the steps above and see.
fwiw - at this point im only downloading roms specifically for my phone - its my 1st so im going with stable ones, cyanogen for now. Once I have a better grip ill explore after that
btw:
A RUU is a *complete* software package for your device made by HTC. It contains everything from bootloader to operating system. I don't really know what else you're trying to ask, so please elaborate.
Click to expand...
Click to collapse
I was trying to figure out if the OS / roms / RUU had to be tied to boot images - as it appears they do, and whether there was a specific sequence to installing them). Since u clarified the RUU's are all-in-ones i guess the installer takes care of that, where as the others have pointed out - flashing custom roms require the boot.img to be flashed AFTER installing the rom - not the best question i admit!!
If your bootloader is damaged, your device is 100% bricked.
Click to expand...
Click to collapse
So if i can access fastboot etc then i can assume mine is fine right?
Thanks again guys - if there was a ribbon bar instead of just thanks id hit all of u a few times - im SURE many noobs will find all this info really really helpful. Its hard to tie the parts together and get an idea of how they all fit - its really puzzling.. and I know u gotta break something before u really understand it - but its nice to avoid this if possible!
Ill keep u posted on progress/results
no luck .... yet
got it working guys - had to flash boot img BEFORE rom, not after.
cyanogen mod 10.1 running on Desire s.
2 days of pain over
fstarockr said:
so by following these directions:
im basically working around the S-On / kernel & partition issue i take it?
Click to expand...
Click to collapse
Exactly.
Im gonna try all this now - reason i wanted to flash stock
is so that i can apply the earlier exploits to gain S-Off - but ill try the steps above and see.
Click to expand...
Click to collapse
That's a valid reason, but in that case you don't need to flash a custom rom first. You just need to use misc_version to lower your mainversion (a fastboot variable) and then you must flash an old (exploitable) RUU. There are numerous guides on how to do this.
I was trying to figure out if the OS / roms / RUU had to be tied to boot images - as it appears they do, and whether there was a specific sequence to installing them). Since u clarified the RUU's are all-in-ones i guess the installer takes care of that, where as the others have pointed out - flashing custom roms require the boot.img to be flashed AFTER installing the rom
Click to expand...
Click to collapse
Correct, but only if you're S-ON and htcdev unlocked. If you're S-OFF the recovery has no problem writing the boot image by itself.
So if i can access fastboot etc then i can assume mine is fine right?
Click to expand...
Click to collapse
Hell, the mere fact that you can turn on your device means your bootloader is fine
got it working guys - had to flash boot img BEFORE rom, not after.
Click to expand...
Click to collapse
No you don't? The order doesn't matter, as long as you've flashed both.
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.
I have a Rooted and s off HTC one Sv from Boost mobile. I can download the OTA for Sense 5 and 4.2.2 but when I try to install it it cancels and says something like cant get ro.products.build = k2cl.. and something else ...
Im new to all of this, but Im really good with following a step by step guide if there is something I can read to fix this issue.
Im just trying to get the latest software available for this phone. And also if there is a way to edit the build.prop on this phone to make it run faster and increase the network speed too. that would be amazing. I have yet to find anything for this phon
Well, for boost mobile you can use a Ruu which they released for the latest available Software.
http://dl3.htc.com/application/RUU_...V_NV_Boost_2.20_150_release_389346_signed.exe
This will delete all of your data and your bootloader must be locked, if you are S-on (only as an info, in case you have unlocked at htcdev.com to gain root access).
Hi. Thanks.
So I need to turn the bootloader off and switch S off back to S on?
I dont remember what software I used to root it, it was on my other computer that got stolen.
How would I go about locking the bootloader? And turning the S back on? And once successful in getting the update will I be able to root it again?
Is there any other better roms I can flash on it now that is better? I would love to have KitKat on here if possible.. But as of now I know that cyanogen mod isnt supporting this device and all I know to do is update it to 4.2.2 with sense 5, if I could just figure out how.
Sorry for all the questions.
Last question is... I seen build.prop editing possiblities to be able to speed up 4g, 3g, and 2g networks speeds and even to bypass network caps, but no guides for htc one sv for boost. Are there any that I can be directed to to edit the build.prop to achieve this?
Don't know about boost specific tweaks.
Also there are no custom roms available for boost.
You are S-off, you didn't mention. But thats good! Don't go S-on, and no need to relock bootloader in this case, as far as i remember.
Backup everything you need, connect your device to your pc and run the Ruu. It will bring you to the latest software for your phone.
Ive been trying over and over to get the Ruu to work and I followed the instructions properly. And even deleted it and downloaded it again.
It keeps saying : Error 170 USB Connection Error. And wants me to check the USB sync cable or my connection to the PC.
But Both my cables work fine and my computer is new and nothing wrong with it. I am able to use my USB to Tether app just fine and im able to copy and paste to and from my phone and able to use HTC Sync manager too. SO Idk what the deal is.
Maybe some specifics about my setup may help.
My computer is an HP Envy Sleekbook with 8g of ram and i5 processor running windows 8.1 64bit.
My phone is the Boost mobiles version HTC One SV C525c with these details:
Android Version: 4.1.2
Sense: 4
Software number: 2.06.653.6 710RD
HTC SDK API: 4.65
HTC Extension Version: HTC Extension_Sense45_12
Kernel Version: [email protected] #1 SMP PREEMPT
Build Number: 2.06.653.6 CL209682 release-keys
I dont know if that helps with my situation but just in case I added it.
Thank you and I appreciate the help
Do a research on google with "htc ruu error 170".
You will get many results, like this:
http://forum.xda-developers.com/showthread.php?t=2553296
No matter what I do nothing seems to be helping
I have been googling for days. And been at it for hours today trying to figure this out.
I really just need a step by step guide. I dont understand this stuff.
So far, I downloaded and unistalled and reinstalled drivers for windows 8.1. I downloaded adb drivers and fastboot.
I tried to use RUU by going into Fastboot usb. I even tried to download the OTA update and then manipulate the update-script by deleting all the assert checks to stop getting the getprop errors. But still didnt work.
IDK what to do all I want to do is have my phone back to normal again and to be able to update it to the newest software version. Its annoying to see the update available notification in my tray and I cant do anything about it.
The closest I got so far was switching to the windows 7 computer and turning off the developer options menu. But then RUU starts to work but then stops at HTC fastboot.exe has stopped working. Im stuck.
Some more information about my phone just in case its helpful. :
Moonshine S-OFF
K2_CL PVT SHIP S-OFF RL
CID-SPCS_003
HBOOT-2.00.4444
RADIO-1.12.50.0516
OpenDSP-v9.2.0268.1214
eMMC-boot
I also got rid of CWM and put TWRP v2.8.4.0
I just went to the bootloader screen and tried to install the OTA file from there and also the OTA file that I deleted the assert build prop stuff from and I get the same error E: Error executing updater binary in zip
SO idk what to do but im determined to fix this.
Thank you much for helping me
Now my phone wont work at all.
Its stuck on the HTC screen and I cant figure out how to get it back. I know there is a way. This really sucks.
guitarjae said:
Now my phone wont work at all.
Its stuck on the HTC screen and I cant figure out how to get it back. I know there is a way. This really sucks.
Click to expand...
Click to collapse
Theres is not much what i can do, because i don't know much about boost, and i don't have any files for it.
Maybe @Modding.MyMind can help you here, he has much more knowledge in this kind of stuff, than me.
Ok. I managed to get my phone unbricked by using windows 7 and using fastboot to flash the same operating system I was already using. Now I don't have twrp or cwm. Its just a red triangle now if I try to log into recovery.
It is also switched from moonshine s off to locked.
So I'm assuming I'm S on now and bootloader locked.
I went back to the RUU program you told me to install and it started to work but then stop and gave an error 158 image error. I googled it but I don't understand how to fix it.
Is there any way I can just get sense 5 and 4.2.2. I'm starting to think its not possible. But would be nice if I could.
I don't know, whats wrong here. What have you flashed on your phone to get it running?
A RUU? This would explain, that you loose twrp, because it flashes everything to stock. But it don't set S-off to S-on! That step has to be done manually by yourself.
---------- Post added at 09:57 ---------- Previous post was at 09:13 ----------
Please check this website for more information and download of the RUU you need:
www.htc.com/us/support/htc-one-sv-boost/news/
guitarjae said:
Ok. I managed to get my phone unbricked by using windows 7 and using fastboot to flash the same operating system I was already using. Now I don't have twrp or cwm. Its just a red triangle now if I try to log into recovery.
It is also switched from moonshine s off to locked.
So I'm assuming I'm S on now and bootloader locked.
I went back to the RUU program you told me to install and it started to work but then stop and gave an error 158 image error. I googled it but I don't understand how to fix it.
Is there any way I can just get sense 5 and 4.2.2. I'm starting to think its not possible. But would be nice if I could.
Click to expand...
Click to collapse
https://www.dropbox.com/s/tacg3jdz84c6wlh/Pure_Jelly_Bean_4.1.2_TWRP_Backup.zip?dl=0
Download this pure 4.1.2 JellyBean backup made specifically for TWRP and extract the zip on to your desktop. Flash the TWRP recovery to your recovery partition using fastboot.
Code:
fastboot flash recovery twrprecovery.img
Reboot in to TWRP, make sure your device is plugged in to your computer.
Now before we move on further I need you to make a quick TWRP backup. You do not need to make a full backup. Just one will do since I am merely aiming to have the required TWRP backup directory be created on your device.
Did you make a quick backup? Good. Lets move forward.
Select the option to mount your usb (You should still be in TWRP). A window will pop up on your computer showing either your internal or external storage. Find the TWRP folder and look through it until you find the backup folder. Go inside the backup folder and you will see the files created to make your backup. Delete them all.
Copy my backup that you downloaded earlier over to that same directory. When done, unmount device from computer, then unmount device from phone. Select to restore your device using that TWRP backup. After completition, reboot your device, let the phone start up. Welcome back to 4.1.2.
Go to settings to manualkly update your device to 4.2.2 but before you accept the update you must make sure you flash back your stock recovery using the same instructions given at the beginning. DO not attempt to accept the OTA with TWRP installed, it will fail.
Hey thanks
Im on 4.1.2 now
Last night I went to this forum http://androidforums.com/threads/htc-one-sv-boost-stuck-on-splash-screen.826881. When I was there I followed the instructions that the guy gave the other guy for his problem, since I was bricked and stuck on the splash screen. I downloaded this https://www.dropbox.com/s/wqq04edwc844ufw/decrypted_k2_cl_2.06.653.6_rom.zip. And that got me back to 4.1.2 with sense 4.
Now since I did that it deleted the twrp I had on it and where it used to say moonshine S Off it now says LOCKED? So, I dont know what that means if Im s off or not anymore.
I went to download the update to 4.2.2 and it started to install but then just rebooted and it still asks me to update and im still on 4.1.2. I also tried the RUU again in fastboot mode and it will start to install and stops at error 158 image error. ? ... I also took the OTA update file that downloaded from the downloads folder and put it on my computer and tried to flash it with fastboot and it still stops after some kind of check. I even edited the update-script to delete the assert at the top and it started and stopped at a different error. So idk..
Right now my phone is back on and I can use it. I just want to get the update somehow. So maybe if you still think I should try again and do what you just mentioned, Ill do it tonight once i get to my desktop with win 7 since win 8.1 is stupid with this.
guitarjae said:
Hey thanks
Im on 4.1.2 now
Last night I went to this forum http://androidforums.com/threads/htc-one-sv-boost-stuck-on-splash-screen.826881. When I was there I followed the instructions that the guy gave the other guy for his problem, since I was bricked and stuck on the splash screen. I downloaded this https://www.dropbox.com/s/wqq04edwc844ufw/decrypted_k2_cl_2.06.653.6_rom.zip. And that got me back to 4.1.2 with sense 4.
Now since I did that it deleted the twrp I had on it and where it used to say moonshine S Off it now says LOCKED? So, I dont know what that means if Im s off or not anymore.
I went to download the update to 4.2.2 and it started to install but then just rebooted and it still asks me to update and im still on 4.1.2. I also tried the RUU again in fastboot mode and it will start to install and stops at error 158 image error. ? ... I also took the OTA update file that downloaded from the downloads folder and put it on my computer and tried to flash it with fastboot and it still stops after some kind of check. I even edited the update-script to delete the assert at the top and it started and stopped at a different error. So idk..
Right now my phone is back on and I can use it. I just want to get the update somehow. So maybe if you still think I should try again and do what you just mentioned, Ill do it tonight once i get to my desktop with win 7 since win 8.1 is stupid with this.
Click to expand...
Click to collapse
You should still be S-Off. If you boot up to your bootloader it will either say S-On or S-Off. You used a decrypted RUU so it is a good chance your bootloader is in fact locked. You lost TWRP because the "RUU" restored your device back with the original images as if your device came right out of the box. Which is the whole purpose of an RUU. As for the issue you are having with the OTA update, that seems a bit off, so just follow my instructions and you should be fine. Check to see if you are S-On or S-Off. Also insure that your bootloader is unlocked. If you are S-On then take the boot.emmc.win file from my backup and rename it to boot.img. Use fastboot to flash the boot.img to the boot partition.
Code:
fastboot flash boot boot.img
recovery.emmc.win is the stock recovery. Again, if you are S-On, then rename it to recovery.img and flash it using fastboot.
Code:
fastboot flash recovery recovery.img
This is required because being S-On will prevent you from writing to those partitions using DD. Requires you to be S-Off otherwise. If you are S-On, then that is fine. First focus on getting yourself up to 4.2.2. Once that has been accomplished then use rumrunner universal for HTC to gain S-Off again.
Modding.MyMind said:
You should still be S-Off. If you boot up to your bootloader it will either say S-On or S-Off. You used a decrypted RUU so it is a good chance your bootloader is in fact locked. You lost TWRP because the "RUU" restored your device back with the original images as if your device came right out of the box. Which is the whole purpose of an RUU. As for the issue you are having with the OTA update, that seems a bit off, so just follow my instructions and you should be fine. Check to see if you are S-On or S-Off. Also insure that your bootloader is unlocked. If you are S-On then take the boot.emmc.win file from my backup and rename it to boot.img. Use fastboot to flash the boot.img to the boot partition.
Code:
fastboot flash boot boot.img
recovery.emmc.win is the stock recovery. Again, if you are S-On, then rename it to recovery.img and flash it using fastboot.
Code:
fastboot flash recovery recovery.img
This is required because being S-On will prevent you from writing to those partitions using DD. Requires you to be S-Off otherwise. If you are S-On, then that is fine. First focus on getting yourself up to 4.2.2. Once that has been accomplished then use rumrunner universal for HTC to gain S-Off again.
Click to expand...
Click to collapse
Hello
Sorry I havent been online lately to give an update.
Thank you for your help. I am successfully now on 4.2.2 with sense 5 by following your instructions.
So now all I have to do is Root again. Can you tell me an quick and easy way to Root again?? I did it last over a year ago on this phone and I think the way it was rooted was the reason I was having such issues. But idk.... Im open for better options on rooting the phone. Towelroot doesnt work for this phone, not that I every used towelroot, i just seen that lots of others are saying it worked and it was fast and easy.
After I root it, I want to be able to increase my phone storage too and be able to move apps to sd card instead of it using all my phone storage. It is already saying cant download bc of insufficient storage.
And other than that, do you know of a good build.prop script for this phone that can increase network speed and maybe bypass the data cap?
Also, I still dont know how I can tell if Im S off or S on? When I hold the vol down and power button, it pops up like it used too but instead of saying its S off it just says LOCKED?