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.
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.
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!
OK so I've been researching for days how to unlock boot loader, root and s-off my HTC one mini. I bought the phone in november so im assuming that i updated to 4.3 or it was already installed (relevant later). I htcdev unlocked my boot loader, installed twrp and made a backup, installed superuser and rooted my phone. Then I installed titanium backup pro, made a backup and uninstalled all the system apps/bloatware I didn't need. All was peachy but the apps kept reappearing which I found was down to s-on (despite what I read about htcdev unlock boot loader method making my phone s-off) . So I tried the revone method and got error 1 which apparently is down to having android 4.3 so I looked for an earlier ROM and flashed Magio r1 which worked fine but couldn't find the data/local/temp folder to install revone into. Probably could of put it somewhere else but I wasn't that confident with the s-off process. So I finally found Jmz m4 stock ROM so there was light at end of tunnel. So I read up on twrp factory reset/format data functions and saw people were using both methods. I went with the full format and factory reset afterwards. Looking back now that was pretty stupid as I have no ROM and no backups to restore to. I did manage to chmod 777 the permissions on my twrp backups and copy the to dropbox (after endless scouring of forums). I also know how to flash boot images and use the adb side load functions. So that's my story.
Problem is I can't adb push the file as it returns with error closed, I've tried the following commands:
adb device - my device is attached and side loading.
adb usb - returns error closed
adb kill-server
adb start server - server starts successfully then returns error closed.
adp push rom.zip /data/media/0 - returns error closed
And just to be sure I tried with /data/media/, same error
I've fastboot flashed the jmzM4 ROM image and kernel but no joy as I'm guessing the boot image isn't enough and you need the zip.
If anyone can help out that would be greatly appreciated.
Currently I can load into boot loader and recovery no problem, just freezes on HTC load screen in normal boot up.
STEAKTASTIC said:
OK so I've been researching for days how to unlock boot loader, root and s-off my HTC one mini. I bought the phone in november so im assuming that i updated to 4.3 or it was already installed (relevant later). I htcdev unlocked my boot loader, installed twrp and made a backup, installed superuser and rooted my phone. Then I installed titanium backup pro, made a backup and uninstalled all the system apps/bloatware I didn't need. All was peachy but the apps kept reappearing which I found was down to s-on (despite what I read about htcdev unlock boot loader method making my phone s-off) . So I tried the revone method and got error 1 which apparently is down to having android 4.3 so I looked for an earlier ROM and flashed Magio r1 which worked fine but couldn't find the data/local/temp folder to install revone into. Probably could of put it somewhere else but I wasn't that confident with the s-off process. So I finally found Jmz m4 stock ROM so there was light at end of tunnel. So I read up on twrp factory reset/format data functions and saw people were using both methods. I went with the full format and factory reset afterwards. Looking back now that was pretty stupid as I have no ROM and no backups to restore to. I did manage to chmod 777 the permissions on my twrp backups and copy the to dropbox (after endless scouring of forums). I also know how to flash boot images and use the adb side load functions. So that's my story.
Problem is I can't adb push the file as it returns with error closed, I've tried the following commands:
adb device - my device is attached and side loading.
adb usb - returns error closed
adb kill-server
adb start server - server starts successfully then returns error closed.
adp push rom.zip /data/media/0 - returns error closed
And just to be sure I tried with /data/media/, same error
I've fastboot flashed the jmzM4 ROM image and kernel but no joy as I'm guessing the boot image isn't enough and you need the zip.
If anyone can help out that would be greatly appreciated.
Currently I can load into boot loader and recovery no problem, just freezes on HTC load screen in normal boot up.
Click to expand...
Click to collapse
PM me with your gmail and we can chat on Hangouts to get you sorted - will be easier chatting real-time than posting loads of instructions etc....
If u can flash the att ruu then the problem is fixed. Just flash it throught fasbttboot.
Well hat off to nelvinchi sorted the problem out and she's working like a bewt again what a genuine legend!
*removes tongue from ar-se*
STEAKTASTIC said:
Well hat off to nelvinchi sorted the problem out and she's working like a bewt again what a genuine legend!
*removes tongue from ar-se*
Click to expand...
Click to collapse
Ive kinda had the same issue after using superwipe before insalling a new rom...now my problem is that i cant ADB PUSH (error: closed)
Can i ask how you managed to sort this? I have international version, unlocked bootloader and s-off.
Thanks
Braddison said:
Ive kinda had the same issue after using superwipe before insalling a new rom...now my problem is that i cant ADB PUSH (error: closed)
Can i ask how you managed to sort this? I have international version, unlocked bootloader and s-off.
Thanks
Click to expand...
Click to collapse
I could probably lead you through the same process but I'd advise asking nelvinchi for help as he will get it sorted promptly and correctly. If not pm me
STEAKTASTIC said:
I could probably lead you through the same process but I'd advise asking nelvinchi for help as he will get it sorted promptly and correctly. If not pm me
Click to expand...
Click to collapse
thanks for your prompt reply. yeah i will prob PM him but im going to try a few things first.cheers
Braddison said:
thanks for your prompt reply. yeah i will prob PM him but im going to try a few things first.cheers
Click to expand...
Click to collapse
Hi!
A couple of things to help you get this sorted:
You can't ADB from HBOOT/Bootloader, if you have TWRP boot to recovery then you can adb push - I'd recommend this over trying to sideload (sideload instantly flashes the zip)
You won't be able to boot if you are UNLOCKED and have S-OFF - You can either use the terminal emulator in recovery or adb shell to use revone.
adb push your rom zip and UPDATE-SuperSU-v1.86 zip to /sdcard/ if this returns an error, push to /data/local/ (you can install zip from here in recovery)
Once done, install the rom, install supersu.
Most likely revone will be missing, so do this:
adb push revone /data/local/
adb shell
cd /data/local/
chmod 755 revone
./revone -l
Reboot to recovery and wipe cache and dalvik
Reboot
REBOOT TO BOOTLOADER
Choose FASTBOOT
fastboot flash boot boot.img (boot.img extracted from the rom zip)
Reboot to recovery
Reboot system
* revone download:
download revone from http://revolutionary.io/revone
remove .bin extention
****** REMEMBER to
Thanks, i will try the instructions you've posted. i am unlocked and s-off.
Adb push worked, however Install of rom failed...as you said i will prob have to download revone and take it from there .
Braddison said:
Thanks, i will try the instructions you've posted. i am unlocked and s-off.
Adb push worked, however Install of rom failed...as you said i will prob have to download revone and take it from there .
Click to expand...
Click to collapse
What error did you get when it failed? Which rom are you flashing?
nelvinchi said:
What error did you get when it failed? Which rom are you flashing?
Click to expand...
Click to collapse
Coming from MagioR5 to his Stock sense 4.3(deox) and used SUPERWIPE hoping for a clean install.
so pushing rom via Adb worked but failed to install the rom, said it was unable to open zip file..
I then full wiped and tried pushing the rom (and supersu update zip) via ADB to /LOCAL/DATA/.....this worked and said zip flash was successful however, couldn't find the MD5...??? (weird)
The phone has now rebooted with sense 5.5 android 4.3 and all seems ok...so far!!!
rebooted to bootloader and phone still s-off and rooted...All seems fine and in working order.
slightly concerned about the md5 as i thought this should have some implications
but so far so good.
thanks to nelvinchi for his support and magio for his custom roms....cheers guys
Braddison said:
Coming from MagioR5 to his Stock sense 4.3(deox) and used SUPERWIPE hoping for a clean install.
so pushing rom via Adb worked but failed to install the rom, said it was unable to open zip file..
I then full wiped and tried pushing the rom (and supersu update zip) via ADB to /LOCAL/DATA/.....this worked and said zip flash was successful however, couldn't find the MD5...??? (weird)
The phone has now rebooted with sense 5.5 android 4.3 and all seems ok...so far!!!
rebooted to bootloader and phone still s-off and rooted...All seems fine and in working order.
slightly concerned about the md5 as i thought this should have some implications
but so far so good.
thanks to nelvinchi for his support and magio for his custom roms....cheers guys
Click to expand...
Click to collapse
Don't worry about the md5 hash fail..... If you do a manual check of md5 key for downloads, and all is ok, it's fine to ignore local fail
yep! cheers all seems fine nelvinchi...thanks again
Now to see about slimming down this rom, either rom cleaner or TB. with xposed!!
oh... i know wrong thread but anyone tried gravity box with One mini ?
Braddison said:
yep! cheers all seems fine nelvinchi...thanks again
Now to see about slimming down this rom, either rom cleaner or TB. with xposed!!
oh... i know wrong thread but anyone tried gravity box with One mini ?
Click to expand...
Click to collapse
Gravity box is not a good idea - it's for aosp roms.
Romcleaner is my De-bloatware of choice - check my post in the q&a forum....
yeah just checked out the gravity box thread ,,,ill give that a miss lol.
sure i had a reply from you on the q&a about debloating...cheers again
Hi Guys,
i have bought as second hand used an htc one mini. I live in Italy, so no Us.
The device report the following info, made by the previous owner:
TAMPERED
RELOCKED
M4_UL PVT S-OFF RL
CID-VODAP102
HBOOT-2.19.0000
RADIO 1.20.40d.00.05
It has TWRP recovery and Android 4.2.2.
I would like to restock it, deleting "tampered" and "relocked"
anybody that can help me please? thank you in advance
Hey buddy don't be a **** and post the same question in 3 different non related threads! Make your own thread instead of hijacking others. And READ what's already here in the XDA forum, it's already been discussed!
Sent from my HTC One using Xparent Green Tapatalk 2
Hey guys,
Tonight I went to install cleanrom on my Verizon HTC One M8. I made a nandroid backup as I always do before flashing a new ROM and then proceeded to flash the new ROM. That went great but then I did something I wouldn't normally do I wiped my data just because I wanted a fresh start and all of my important stuff was backed up online. But when I went to boot I'm stuck on the HTC logo. I have an OTG cable so I proceeded to put the ROM on a flash drive and flash it. Same problem. So I put my old ROM ViperOne 2.4 on the flash drive and flashed it. Now I instantly boot into fastboot. This all seems really strange to me but I'm sure its caused by me stupidly formatting data. I need a bigger flash drive to install the original nandroid backup I found online so I will get one today and post my results. I'm almost positive that will fix my problem but I know there might be an HTC guru out there that knows exactly what my problem is and it may be more then what I'm thinking. Sorry this is scattered ive been messing with my phone all night and kinda tired now. Any help is greatly appreciated and thank you in advance for taking time to help me with this issue. And if I missed anything let me know and I will be sure to post it.
Edit
Sorry I completely forgot to add that I put my nandroid backup on my flash drive but when I went to use it it did not work. I believe this is because I did not have a big enough flash drive so it did not completely back up. LOL! Tonight was not my night.
radiowavedev said:
Hey guys,
Tonight I went to install cleanrom on my Verizon HTC One M8. I made a nandroid backup as I always do before flashing a new ROM and then proceeded to flash the new ROM. That went great but then I did something I wouldn't normally do I wiped my data just because I wanted a fresh start and all of my important stuff was backed up online. But when I went to boot I'm stuck on the HTC logo. I have an OTG cable so I proceeded to put the ROM on a flash drive and flash it. Same problem. So I put my old ROM ViperOne 2.4 on the flash drive and flashed it. Now I instantly boot into fastboot. This all seems really strange to me but I'm sure its caused by me stupidly formatting data. I need a bigger flash drive to install the original nandroid backup I found online so I will get one today and post my results. I'm almost positive that will fix my problem but I know there might be an HTC guru out there that knows exactly what my problem is and it may be more then what I'm thinking. Sorry this is scattered ive been messing with my phone all night and kinda tired now. Any help is greatly appreciated and thank you in advance for taking time to help me with this issue. And if I missed anything let me know and I will be sure to post it.
Click to expand...
Click to collapse
Did you flash newest "firmware" as well? The 2.xx.xxx.x ROM's need newest firmware to boot correctly. (Radio, hboot). Old hboot would cause it to hang at boot.
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
andybones said:
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
Click to expand...
Click to collapse
+1
andybones said:
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
Click to expand...
Click to collapse
That is why this was so strange to me. The hboot firmware sounds promising though.
bigblueshock said:
Did you flash newest "firmware" as well? The 2.xx.xxx.x ROM's need newest firmware to boot correctly. (Radio, hboot). Old hboot would cause it to hang at boot.
Click to expand...
Click to collapse
Thank you for the response. I never even knew it was necessary to flash hboot. I've flashed a couple of ROMs before and never flashed hboot. I will try this tonight. Is this just as simple as flashing a zip? And I pick the newest available version?
radiowavedev said:
Thank you for the response. I never even knew it was necessary to flash hboot. I've flashed a couple of ROMs before and never flashed hboot. I will try this tonight. Is this just as simple as flashing a zip? And I pick the newest available version?
Click to expand...
Click to collapse
not just hboot my friend.
the whole firmware.
if you were to take the OTA you would get this firmware installed.
since we are S-OFF and we don't want to take the OTA, as it's MUCH easier to just fastboot the firmware.zip once someone takes the OTA and pulls all the needed files..
here is the thread you want - here
here is a direct copy and paste from the thread full credit to the OP
"4.4.3 DOWNLOADS BELOW no boot or recovery included in this (what this means is that you won't have to re-flash a custom recovery after the firmware, they removed it to make things easier on us.)
https://www.androidfilehost.com/?fid=23622183712470028
CREDIT TO dottat as he posted it 1st so no need for me too well just use his. Be sure to thank him if you see if around.
Flash via fastboot or Sd card method. Flash at your own risk.
directions for flashing firmware via fastboot an radios below.
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Then fastboot reboot-bootloader��
FYI on my m8 i did not need to be reflushed on 1.55 but on the new update it did.
credit for these directions also come from santod "
andybones said:
not just hboot my friend.
the whole firmware.
if you were to take the OTA you would get this firmware installed.
since we are S-OFF and we don't want to take the OTA, as it's MUCH easier to just fastboot the firmware.zip once someone takes the OTA and pulls all the needed files..
here is the thread you want - here
here is a direct copy and paste from the thread full credit to the OP
"4.4.3 DOWNLOADS BELOW no boot or recovery included in this (what this means is that you won't have to re-flash a custom recovery after the firmware, they removed it to make things easier on us.)
https://www.androidfilehost.com/?fid=23622183712470028
CREDIT TO dottat as he posted it 1st so no need for me too well just use his. Be sure to thank him if you see if around.
Flash via fastboot or Sd card method. Flash at your own risk.
directions for flashing firmware via fastboot an radios below.
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Then fastboot reboot-bootloader��
FYI on my m8 i did not need to be reflushed on 1.55 but on the new update it did.
credit for these directions also come from santod "
Click to expand...
Click to collapse
Thank you for all of the useful information I will give this a shot tonight.
radiowavedev said:
Thank you for all of the useful information I will give this a shot tonight.
Click to expand...
Click to collapse
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
andybones said:
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
Click to expand...
Click to collapse
Yeah I'm quite used to the ways of XDA but honestly had no idea about hboot. And I definitely will be thanking them. I'm now home and will test it out. I'll post my results afterwards.
andybones said:
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
Click to expand...
Click to collapse
Okay so I downloaded m8.443.firmware.zip does this have to be flashed via fastboot? And once I flash it should I flash my custom rom cleanrom 2.0 rc and that should be it for my issue?
radiowavedev said:
Okay so I downloaded m8.443.firmware.zip does this have to be flashed via fastboot? And once I flash it should I flash my custom rom cleanrom 2.0 rc and that should be it for my issue?
Click to expand...
Click to collapse
well in bootloader/fastboot yes.. but you DO NOT run the fastboot command..
this is exactly what you do
1) the file you downloaded, m8.443.firmware.zip - rename this to firmware.zip
2) adb reboot bootloader (or however you get there)
3) fastboot oem rebootRUU - this is the important part you will be brought to a black screen with a gray HTC logo IIRC, run the next command - the green bar may stop 3/4 of the way this is because you when you run the last command it will finish it.
4) fastboot flash zip firmware.zip
5) fastboot reboot-bootloader
Im sorry this might be stupid but what do you mean by not running fastboot command? And you say reboot-bootloader shouldn't I do reboot-recovery and flash my custom rom after factory resetting of course. Sorry im just trying to make sure im thorough. I would think messing up hboot would permanently brick my phone.
andybones said:
well in bootloader/fastboot yes.. but you DO NOT run the fastboot command..
this is exactly what you do
1) the file you downloaded, m8.443.firmware.zip - rename this to firmware.zip
2) adb reboot bootloader (or however you get there)
3) fastboot oem rebootRUU - this is the important part you will be brought to a black screen with a gray HTC logo IIRC, run the next command - the green bar may stop 3/4 of the way this is because you when you run the last command it will finish it.
4) fastboot flash zip firmware.zip
5) fastboot reboot-bootloader
Click to expand...
Click to collapse
Would it just be easier to use a nandroid backup?
I figure in the meantime ill fill you in on everything I know about my phone. I was previously running the newest version of ViperOne which was 2.5.0 This problem came up after flashing cleanrom 2.0 RC. I am S-off and unlocked of course and I am running CWM-based Recovery v6.0.4.8 and my hboot stats are as follows:
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
I have searched the forums looking for anything related to my issue and cant seem to come up with anything. I have come across a few people with the same issues as me but there questions go unanswered which makes me very nervous... I do believe it is related to my hboot firmware but I cant seem to find a thorough explanation of hboot. Sorry I am a former Motorola guy. This HTC stuff is really mixing it up for me. LOL!
I really appreciate all of the help you have given me and am grateful that you are hanging in with my HTC stupidity and phobia of bricking this 700 dollar piece of aluminum and magnesium.
radiowavedev said:
I figure in the meantime ill fill you in on everything I know about my phone. I was previously running the newest version of ViperOne which was 2.5.0 This problem came up after flashing cleanrom 2.0 RC. I am S-off and unlocked of course and I am running CWM-based Recovery v6.0.4.8 and my hboot stats are as follows:
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
I have searched the forums looking for anything related to my issue and cant seem to come up with anything. I have come across a few people with the same issues as me but there questions go unanswered which makes me very nervous... I do believe it is related to my hboot firmware but I cant seem to find a thorough explanation of hboot. Sorry I am a former Motorola guy. This HTC stuff is really mixing it up for me. LOL!
I really appreciate all of the help you have given me and am grateful that you are hanging in with my HTC stupidity and phobia of bricking this 700 dollar piece of aluminum and magnesium.
Click to expand...
Click to collapse
Separate the terminology "ROM" and "Firmware" for a moment. Firmware should/will never change regardless of what ROM's you flash. Think of firmware as a computers BIOS, And ROM as your computers operating system.
First, turn your phone off. Second, hold volume down + power button and do NOT let go of volume down until you're in the boot loader screen. Step 3) switch the boot loader into fast boot within that screen(Fast boot or fast boot USB may come up by default it will be highlighted in red). If you're plugged up to your computer via USB, it should automatically say "Fastboot USB". Then you can execute the commands in the command prompt andybones was talking about.
Did i loose you anywhere?
You could just nandroid back to your previous ROM... but that defeats the purpose. You'll never be able to go to a newer Sense ROM without the firmware upgrade anyway. You might as well get it done because it may improve your network signal, boot times, etc. Usually only benefits you,
After you upgrade firmware, it will say hboot 3.18.0000, Radio: 1.09.20.0702,
radiowavedev said:
Would it just be easier to use a nandroid backup?
Click to expand...
Click to collapse
I didn't just waste my time to write you up a STEP BY STEP FOOL proof guide.
I am not doing this for my benefit...
You made a thread.
You asked for help.
I gave detailed, if you mess up you didn't follow them exactly..
Why would you have me give you exact directions to fix your phone, then ask about a nandroid?
NO. If it were that simple my friend, don't you think I would have let you known this?
I'm sorry if this comes off rude, but I went out of my way to give you exact detailed instructions and you blow them off.
Why make a thread and then not take the advice from a Recognized Contributor to this site!?
I hope you can understand how frustrating this is.
I don't do this because it's fun for me to help get your phone fixed, I do it because you asked for help, and I like to help, but when my help goes un-heard and blown off - I walk away. - Best of luck my friend.
I am still going to help because that's the kind of guy I am..
Run the RUU since you are S-OFF if nothing else works.
You are a SOFT-brick. Very easy to fix.
Andybones, I totally understand. I wasnt trying to be rude im just confused and trying to come up with ideas. I understand it was dumb to mention the nandroid now. I hope you can accept my sincerest apology. I appreciate everything you have done for me and understand if you dont want to help me any longer. Like I said it was not my intention to be rude but I see how it can look like that. I just dont know what im doing.
Hi there, I believe I may have been in the same position as you at some point. What actually is happening is that you are trying to flash a new ROM (4.4.3 I believe) with the old hboot. The ROM should still boot but it will take up to 20min.
How to fix this:
1. Boot into boot loader, (manually or adb)
2. Choose fastboot
3. Connect to USB
4. Open command prompt
5. Fastboot devices
6. fastboot oem rebootRUU
7. You should see a black screen with a dark HTC logo.
8. fastboot flash zip (nameofzip).zip
9. When it finishes type fastboot reboot-bootloader (hyphen required)
10. You just flashed the new firmware but it has no os. You now need to flash a ROM or restore a nandroid backup.
Sent from my HTC One M8 GPE converted using XDA Premium mobile app
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?