I've just received an update to android 4.2.2 with Sense 5 on my rooted HTC One SV (Vodafone Spain), and I'm not able to perform. After rebooting appears fastboot :
****TAMPERED***
***RELOCKED***
*** Security Warning ***
K2_U PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40a.00.04
OpenDSP-v9.2.0268.1214
eMMV-boot
Mar 29 2013.20:55:40:20204
and the menu for bootloader.
What's wrong? Is there any way to solve?
Security warning? Were you by any chance S-Off with any custom kernel, boot.img, custom hboot.img, etc???
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 12:52 AM ---------- Previous post was at 12:49 AM ----------
You said CWM in your thread? Do you by any chance still have a custom recovery on your device?
I will have to look into this personally as I have never seen this 'security warning' before. I find it very interesting
Sent from my C525c using XDA Premium 4 mobile app
re
Sorry, previously i've tried to perform upgrade, but CWM gives me an error reffered to access file and can't mount device, so i tried to install a boot.img from a backup. Then, the problem I exposed.
Thanks for your attention.
You can't upgrade with cwm from an over the air update. You must have your stock recovery for it to work. You can't install a boot.img with S-On unless you flash it through fastboot command, and not with a custom recovery. You have to unlock your bootloader before you can do any of this. Then relock your bootloader after you flash your boot.img and stock recovery.img.
Sent from my C525c using XDA Premium 4 mobile app
re
Modding.MyMind said:
You can't upgrade with cwm from an over the air update. You must have your stock recovery for it to work. You can't install a boot.img with S-On unless you flash it through fastboot command, and not with a custom recovery. You have to unlock your bootloader before you can do any of this. Then relock your bootloader after you flash your boot.img and stock recovery.img.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's the question, I flashed boot.img and recovery img (from a backup) using fastboot command.
And there's more: I see the red text in bootloader after apply the OTA, so applied the info on "[MOD][4.1.2] Remove Red Text in HBoot/Bootloader (for k2u & k2ul) - S-Off only!" http://forum.xda-developers.com/showthread.php?t=2289357 with the same result as taking an aspirine. Then the same with
TUTORIAL: Remove *TAMPERED* & *RELOCKED* flag / HBoot w/o unlock_code.bin http://forum.xda-developers.com/showthread.php?t=2541843 . Guess the result??
yes, the same: none. I'm getting amused trying to get my phone having 4.2.2 and sense 5 from 4.1.2 and 4+, but I will not having a brick (nice brick anyway, but useless).
Ahhh, I forget to tell you, after applying remove tampered, and rebooting to fastboot, the warning has dissapeared, but tampered and relocked remains. Is not funny ?
As you can guess, I'm not a guru in this matter. I wish it were MS-DOS , then there will be a chance.
You CANNOT FLASH A CUSTOM HBOOT while you are S-On and with a locked bootloader. My tutorial which you posted requires that you are S-OFF which you are not. You are currently S-On. Had you read my instructions in that tutorial you would had seen that.
In addition, you currently have a CUSTOM recovery on your device with a LOCKED bootloader which was a huge mistake.
You HAVE to unlock your bootloader to fix your problems. Once you unlock your bootloader you will be fine. YOU CANNOT FLASH ANYTHING IF YOUR BOOTLOADER IS LOCKED.
1.) Unlock your bootloader with your unlock_code.bin file, then restore your phone with your backup. If you do not have your PERSONAL unlock_code.bin file then you need to head over to HTCDEV.com and follow their guide to receiving one which will be sent via email to you.
2.) Insure you do not have a custom hboot, custom boot, custom kernel, custom recovery installed on your device - if you do then RESTORE them with your stock IMG's.
3.) After you have unlocked your bootloader, restored your device with your backup, and insured you have no custom .imgs on your device...... THEN, AND ONLY THEN, will you relock your bootloader. After which you will be able to upgrade your phone.
Sent from my C525c using XDA Premium 4 mobile app
Modding.MyMind said:
You CANNOT FLASH A CUSTOM HBOOT while you are S-On and with a locked bootloader. My tutorial which you posted requires that you are S-OFF which you are not. You are currently S-On. Had you read my instructions in that tutorial you would had seen that.
In addition, you currently have a CUSTOM recovery on your device with a LOCKED bootloader which was a huge mistake.
You HAVE to unlock your bootloader to fix your problems. Once you unlock your bootloader you will be fine. YOU CANNOT FLASH ANYTHING IF YOUR BOOTLOADER IS LOCKED.
1.) Unlock your bootloader with your unlock_code.bin file, then restore your phone with your backup. If you do not have your PERSONAL unlock_code.bin file then you need to head over to HTCDEV.com and follow their guide to receiving one which will be sent via email to you.
2.) Insure you do not have a custom hboot, custom boot, custom kernel, custom recovery installed on your device - if you do then RESTORE them with your stock IMG's.
3.) After you have unlocked your bootloader, restored your device with your backup, and insured you have no custom .imgs on your device...... THEN, AND ONLY THEN, will you relock your bootloader. After which you will be able to upgrade your phone.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's a help
. No problem with 1 and 3, but 2... I think it will be a little difficult. I've just no idea how to do this, specially how and where to get stock images.
You don't have any idea about how much patient and helpfull you are. Thanks very very much
Pull the boot.img from your backup and copy it to your computer. Insure you name it boot.img.
Now go I into CWM and restore your device with your backup.
Now go into fastboot so you can flash your boot.img
fastboot flash boot boot.img
Now go into your recovery to confirm if it is stocked or custom. If shown a black screen with triangle then you are back to stock recovery. Otherwise it will still be CWM. If still CWM you will need to go to the link I will be providing in the below post and find a recovery.img suited for your device and flash it just like I told you to do with your boot.img
fastboot flash recovery recovery.img
At this point, I can only HOPE you do not have a CUSTOM HBOOT on your device but from the sounds of it you do not since you attempted that with a LOCKED bootloader which ultimately failed during its process.
So with that said, go ahead and relock your bootloader.
fastboot oem lock
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 10:39 AM ---------- Previous post was at 10:34 AM ----------
http://forum.xda-developers.com/showthread.php?t=2317379
Sent from my C525c using XDA Premium 4 mobile app
Let's have some fun:
I did everything as you told me, everything. So assume there's a stock boot and a stock recovery. Also CWM dissapeared from recovery.
entering in fastboot after reboot I get the same message except ****security warning*****.
including S-ON !!!
Well, at this point, using again fastboot oem lock, the future brick says "device was already locked".
Is it not fun?.
Awesome, I'm really having fun while learning. I hope not to annoy you, in that case I promise to be more serious an read much much posts here and other forums before have any question.
I know it would be silly, but will try to install by itself the OTA. I find it could be interesting to see what will happend
I'll tell you
Ohhhh! , at this moment it seems to work, thanks .
If is there any thing I could do for you, tell me please, need some file from the ota or backup??
just tell me.
Related
I bought it yesterday and when I tried to go with the rooting process, when I rebooted into the bootloader, it said ***UNLOCKED*** and above that it said ***TAMPERED***. I figured that it was already unlocked so I resumed with the process. I installed the CWM recovery and the SuperSU.
However, it still say "Ship S-On" in the bootloader. Am I free to flash ROMs or am I supposed to get it to S-Off somehow?
S-Off rooting has not been achieved yet. Unlocking bootloader and rooting with the current methods will allow for custom ROM installation.
hTc One S
One s doesnt have S-off yet,but you can flash rom s anyway .you will just have to fastboot the boot or use twrp recovery ,
I would stick to fastboot tho as twrp doesn't always flash the boot for me.
Enjoy
Sent from my HTC One S using xda premium
pushtostop said:
One s doesnt have S-off yet,but you can flash rom s anyway .you will just have to fastboot the boot or use twrp recovery ,
I would stick to fastboot tho as twrp doesn't always flash the boot for me.
Enjoy
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
So I flash the ROM first. Then If i want to install a kernel, I install through fastboot? In that order?
For example: I flash This ROM first and then I reboot into fastboot in the bootloader to flash This Kernel?
Ya you can flash kernel first or last doesn't matter , just fastboot boot.IMG reboot to recovery and flash Rom
Sent from my HTC One S using xda premium
Its my sisters phone, currently stucked at bootsplash screen
I shall post the bootloader information first....
** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHOP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.0909_L
OpenDSP-vs29.1.0.45.0662
eMMc-boot
Jun 11 2012
CID returned is HTC_044... No matter how i flash recovery, the phone simply reboots... means i cant get into recovery mode.
I tried reflashing boot.img from vipers and relash recovery... doesnt work.
Right now, im trying to flash RUU via zip..... I have relocked my bootloader... Current status is that I managed to send the zip file over... but its stucked at writing for the past 10 mins...
This is the RUU where i extracted the rom.zip from
"RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed"
It should be the same as my current rom... which if i read correctly, it will not get updated? that I should use the newer 3.17 RUUs for asia in order to fix?
************************ Update ************************
Okay great... now after waiting for 4332 seconds for the writing part to finish... I knew its not going to work via waiting any longer... I unplugged the USB... the command prompt shows up an error (FAILED, too many links)... I attempted to restart the phone from the HTC logo and now it doesnt start at all... cant even get into bootloader... =.=
************************ Update ************************
Okay I've managed to save my phone using this method http://unlimited.io/qhsusbdload.htm
So now im back to square one... I can go bootloader... i unlocked it again... but i still cant go recovery...
************************ Update ************************
Now its back to being bricked again... as I was working on the phone outside when i managed to unbricked it. I choose to power off the phone from bootloader menu, thinking that I could work on it when I get home... alas, when i got home... the phone doesnt turn on... and i saw the dreaded QHSUSB_DLOAD thingy again...... omg... And the above method no longer works..........
kedirakevo said:
Its my sisters phone, currently stucked at bootsplash screen
I shall post the bootloader information first....
** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHOP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.0909_L
OpenDSP-vs29.1.0.45.0662
eMMc-boot
Jun 11 2012
CID returned is HTC_044... No matter how i flash recovery, the phone simply reboots... means i cant get into recovery mode.
I tried reflashing boot.img from vipers and relash recovery... doesnt work.
Right now, im trying to flash RUU via zip..... I have relocked my bootloader... Current status is that I managed to send the zip file over... but its stucked at writing for the past 10 mins...
This is the RUU where i extracted the rom.zip from
"RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed"
It should be the same as my current rom... which if i read correctly, it will not get updated? that I should use the newer 3.17 RUUs for asia in order to fix?
Click to expand...
Click to collapse
Stuck in a similar problem not sure what to do...
I dont understand why you guys want to relock and run the ruu... why not just flash a stock rom? Less headache
Sent from my One X using xda app-developers app
If you're relocked then you can't flash the zip. The ruu is an exe you need to run it with your phone in fastboot usb
Sent from my VENOMized HoxL
exad said:
I dont understand why you guys want to relock and run the ruu... why not just flash a stock rom? Less headache
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
how do i flash rom when recovery aint working?
area51avenger said:
If you're relocked then you can't flash the zip. The ruu is an exe you need to run it with your phone in fastboot usb
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1952426
Program says phone's bootloader must be locked in order to flash ruu zip
kedirakevo said:
how do i flash rom when recovery aint working?
Click to expand...
Click to collapse
Unlock boot loader again if its relocked and just fastboot flash twrp.. use the one click tool if you don't know how to flash recovery but as long as boot loader is unlocked you can flash recovery. Once you do, recovery will work again.
Sent from my One X using xda app-developers app
exad said:
Unlock boot loader again if its relocked and just fastboot flash twrp.. use the one click tool if you don't know how to flash recovery but as long as boot loader is unlocked you can flash recovery. Once you do, recovery will work again.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
which i stated in my first post that before relocking my bootloader... I have been reflashing the recovery many times but i cant boot into recovery mode....
kedirakevo said:
which i stated in my first post that before relocking my bootloader... I have been reflashing the recovery many times but i cant boot into recovery mode....
Click to expand...
Click to collapse
When you flash recovery is it successful? When you select recovery from boot loader what happens?
Which recovery and version are you flashing?
Sent from my One X using xda app-developers app
exad said:
When you flash recovery is it successful? When you select recovery from boot loader what happens?
Which recovery and version are you flashing?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
yea command prompt claimed its sucessful... I used the latest all in one toolkit where the creator claimed to use TWRP 2.4.1.0
kedirakevo said:
yea command prompt claimed its sucessful... I used the latest all in one toolkit where the creator claimed to use TWRP 2.4.1.0
Click to expand...
Click to collapse
Maybe A bad download. Download the latest twrp.
Make sure boot loader is unlocked and you have fastboot usb on in bootloader
Then within toolkit pick flash other recovery and manually select the one you downloaded. Then try selecting recovery in bootloader.
Sent from my One X using xda app-developers app
kedirakevo said:
Program says phone's bootloader must be locked in order to flash ruu zip
Click to expand...
Click to collapse
RUU is an exe the fact it creates a rom.zip is fairly well hidden. Are you running the exe or doing some other crazy thing?
You should not be flashing anything to your phone if you are confusing zip and exe's, it means you lack the basic understanding of computers to be able to complete these tasks without failing.
How did you try to flash the recovery? What recovery did you try to flash? What were the errors given?
EDIT: you should not be using one click tools.
Use fastboot and flash recovery yourself, it is a simple task.
exad said:
Maybe A bad download. Download the latest twrp.
Make sure boot loader is unlocked and you have fastboot usb on in bootloader
Then within toolkit pick flash other recovery and manually select the one you downloaded. Then try selecting recovery in bootloader.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
wish I could try that... it bricked now.
twistedddx said:
RUU is an exe the fact it creates a rom.zip is fairly well hidden. Are you running the exe or doing some other crazy thing?
You should not be flashing anything to your phone if you are confusing zip and exe's, it means you lack the basic understanding of computers to be able to complete these tasks without failing.
How did you try to flash the recovery? What recovery did you try to flash? What were the errors given?
EDIT: you should not be using one click tools.
Use fastboot and flash recovery yourself, it is a simple task.
Click to expand...
Click to collapse
the zip file can be obtained via temp folder of the windows directory when you run the exe file.
The all in one toolkit requires the zip so I got it done via that method...
Yes I know how to do it via command prompt but the toolkit is handy...
And lastly you can say my understanding of mobile phone system isnt complete but dont insult me saying I dont understand whats zip and exe......
Bricked? Exactly what is happening.
Sent from my One X using xda app-developers app
exad said:
Bricked? Exactly what is happening.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
beats me man... Told you, was trying to flash RUU through zip then it just hung there... but I managed to save my phone... I redownloaded and reflashed recovery as you advised but still no avail! Basically, back to square one....
kedirakevo said:
the zip file can be obtained via temp folder of the windows directory when you run the exe file.
The all in one toolkit requires the zip so I got it done via that method...
Yes I know how to do it via command prompt but the toolkit is handy...
And lastly you can say my understanding of mobile phone system isnt complete but dont insult me saying I dont understand whats zip and exe......
Click to expand...
Click to collapse
I know it can be obtained from temp folder.
Why go to the effort of getting the rom.zip to use in the toolkit when you could simply just run the RUU, which you had to do to get the rom.zip in the first place? Especially when it was failing, why push on with trying to use the toolkit instead of just using the RUU as it was intended by HTC?
I have not much knowledge of the toolkit, but when it flashes zip's is it for normal ROM's or for RUU rom.zip? The rom.zip is not in a format that can normally be used by most tools, it is not the same as flashing a custom ROM.
The toolkit is likely only for installing custom ROM's via pre installed TWRP and not compatible with rom.zip.
You said you were using a RUU zip and complaining it was failing, it appeared at face value you were confusing what the RUU even is.
I am still lost why running the RUU and grabbing the rom.zip from temp folder and then flashing in a toolkit was your chosen method. This just points more towards you are confused about what a RUU is.
I am sure the RUU would work if you just let it run like it is supposed to.
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
kedirakevo said:
was trying to flash RUU through zip then it just hung there.
Click to expand...
Click to collapse
Why?
Personally because of the state you have got the phone in to I would:
1)go get the correct tools. eg fastboot, unlockcode, twrp and rom
2)Ensure phone is charged
3)fastboot oem lock
4)Run RUU.. and try actually running it which means just click next and yes a lot.. no fancy going to temp folders and trying to incorrectly install rom.zip via random tools
5)fastboot flash unlocktoken Unlock_code.bin
6)fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
7)fastboot flash boot boot.img (from desired rom)
8)boot into recovery
9)mount USB and transfer desired ROM
10)wipe data and system
11)install ROM
12)reboot in to ROM.
twistedddx said:
I know it can be obtained from temp folder.
Why go to the effort of getting the rom.zip to use in the toolkit when you could simply just run the RUU, which you had to do to get the rom.zip in the first place? Especially when it was failing, why push on with trying to use the toolkit instead of just using the RUU as it was intended by HTC?
I have not much knowledge of the toolkit, but when it flashes zip's is it for normal ROM's or for RUU rom.zip? The rom.zip is not in a format that can normally be used by most tools, it is not the same as flashing a custom ROM.
The toolkit is likely only for installing custom ROM's via pre installed TWRP and not compatible with rom.zip.
You said you were using a RUU zip and complaining it was failing, it appeared at face value you were confusing what the RUU even is.
I am still lost why running the RUU and grabbing the rom.zip from temp folder and then flashing in a toolkit was your chosen method. This just points more towards you are confused about what a RUU is.
I am sure the RUU would work if you just let it run like it is supposed to.
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
Why?
Personally because of the state you have got the phone in to I would:
1)go get the correct tools. eg fastboot, unlockcode, twrp and rom
2)Ensure phone is charged
3)fastboot oem lock
4)Run RUU.. and try actually running it which means just click next and yes a lot.. no fancy going to temp folders and trying to incorrectly install rom.zip via random tools
5)fastboot flash unlocktoken Unlock_code.bin
6)fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
7)fastboot flash boot boot.img (from desired rom)
8)boot into recovery
9)mount USB and transfer desired ROM
10)wipe data and system
11)install ROM
12)reboot in to ROM.
Click to expand...
Click to collapse
well... as mentioned, would really love to follow your steps but.... its bricked now... again...
I did run RUU.exe once but it hung for 30 mins without activity... but then again that was when my bootloader was unlocked... then i read that i can relock and do it through ruu.zip instead.... so i went that route.......
Btw I did update my status on my first post...
kedirakevo said:
well... as mentioned, would really love to follow your steps but.... its bricked now... again...
I did run RUU.exe once but it hung for 30 mins without activity... but then again that was when my bootloader was unlocked... then i read that i can relock and do it through ruu.zip instead.... so i went that route.......
Btw I did update my status on my first post...
Click to expand...
Click to collapse
The least risky way would be to flash a stock ROM from here not an ruu. There are some untouched roms. I, myself have bricked running the telus ruu.
Sent from my One X using xda app-developers app
Hi,
I'd like to ask for your help. After an update to Android 4.2.2 and Sense 5.0 on my HTC ONE SV I'd really like to go back to the previous version, I know a lot of people are happy about the update, but I'd really like to go back to the older menus, look etc. I don't mind losing the data.
I'm new over here ... so please bare with me
What info should I provide?
Nina
I can't help you at the moment because I have to get ready for work but for starters you will need to unlock your device, acquire the proper ruu (4.1.2), or if its available on here then a nandroid backup (4.1.2) specific to your device. Then at this point the procedures to take would be based on whether you are S-On or S-off.
Hopefully someone else may chime in on this while I am at work.
Sent from my C525c using XDA Premium 4 mobile app
We need to know, what version of one sv you have (k2u, k2ul, or other).
And if you are S-off, which hboot...
To unlock your device or in simple terms the bootloader you will need to head over to HTCDEV.com and follow their instructions. If you wish to be S-Off you will need to get rumrunner for your phone and follow its instructions - otherwise you may remain S-On.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 07:38 AM ---------- Previous post was at 07:36 AM ----------
old.splatterhand said:
We need to know, what version of one sv you have (k2u, k2ul, or other).
And if you are S-off, which hboot...
Click to expand...
Click to collapse
Sounds like she is legit stock on everything lol. So this may in a sense be easy assuming instructions can be followed
Sent from my C525c using XDA Premium 4 mobile app
Thanks to both of you.
My version is:
K2_UL PVT SHIP S-on RL
HBOOT-2.00.0000
ninamalina said:
Thanks to both of you.
My version is:
K2_UL PVT SHIP S-on RL
HBOOT-2.00.0000
Click to expand...
Click to collapse
Then its quiet easy:
unlock your device at htcdev.com (follow the instruction on that side.
Then you need to flash a custom recovery (i recommend TWRP 2.6.3) with fastboot, and next you flash a 4.1.2 rom with recovery. Now you need to flash the boot.img that was inside your rom zip with fastboot and you are ready to go
All links you need, you will find in my index thread (look at my signature for it).
To flash a custom recovery with fastboot you will need to insure your custom recovery image file is located in the same folder as your fastboot file to keep this next part simple.
Go into your HBoot then select fastboot. Connect device to your pc and in the command window type:
Code:
fastboot devices
This should show that your device is connected. If you see nothing then you will need to resolve that before proceeding. Next , once connection is established type:
Code:
fastboot boot customrecovery.img
You are booting instead of flashing the custom recovery so your stock recovery will be persevered. Each time you reboot your device you will need to follow those steps again to access the custom recovery vice your stock recovery.
If you wish to flash it then:
Code:
fastboot flash recovery customrecovery.img
I don't recommend you flashing it yet unless you get a copy of your stock recovery first.
Sent from my C525c using XDA Premium 4 mobile app
old.splatterhand said:
Then its quiet easy:
unlock your device at htcdev.com (follow the instruction on that side.
Then you need to flash a custom recovery (i recommend TWRP 2.6.3) with fastboot, and next you flash a 4.1.2 rom with recovery. Now you need to flash the boot.img that was inside your rom zip with fastboot and you are ready to go
All links you need, you will find in my index thread (look at my signature for it).
Click to expand...
Click to collapse
Great, thanks!
I'll do everything when i come home
Modding.MyMind said:
To flash a custom recovery with fastboot you will need to insure your custom recovery image file is located in the same folder as your fastboot file to keep this next part simple.
Go into your HBoot then select fastboot. Connect device to your pc and in the command window type:
Code:
fastboot devices
This should show that your device is connected. If you see nothing then you will need to resolve that before proceeding. Next , once connection is established type:
Code:
fastboot boot customrecovery.img
You are booting instead of flashing the custom recovery so your stock recovery will be persevered. Each time you reboot your device you will need to follow those steps again to access the custom recovery vice your stock recovery.
If you wish to flash it then:
Code:
fastboot flash recovery customrecovery.img
I don't recommend you flashing it yet unless you get a copy of your stock recovery first.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, will follow your advice!
Although instructions are clear, I still have problems
I've tried using different computer, turned my av off, but still get this when i try to run the downloaded file from HTCdev.com:
This aplication has failed to start because AdbWinApi.dll was not found.
You are missing files.
You can get them from here: http://rom.android-host.de/DESIRE_C/tools/Android.zip
Okay so here is what happened i unlocked my bootloader and rooted my phone using the all in one toolkit, i tried to flash a custom ROM using the GooManager app. This is where things went wrong. After flashing the ROM my phone shut off and would only turn on to the HTC Quietly Brilliant page at the beginning of the boot cycle, i made a backup but dont know how to find it. I somehow managed to wipe the entire phone and now i have no operating system. I had TWRP installed but cannot access it because i relocked the phone. Is there anyway to get this thing working again? any help would be much appreciated
here is what my fastboot screen reads:
***TAMPERED***
***RELOCKED***
EVITA PVT SHIP S-ON RL
HBOOT- 2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
brenntard said:
Okay so here is what happened i unlocked my bootloader and rooted my phone using the all in one toolkit, i tried to flash a custom ROM using the GooManager app. This is where things went wrong. After flashing the ROM my phone shut off and would only turn on to the HTC Quietly Brilliant page at the beginning of the boot cycle, i made a backup but dont know how to find it. I somehow managed to wipe the entire phone and now i have no operating system. I had TWRP installed but cannot access it because i relocked the phone. Is there anyway to get this thing working again? any help would be much appreciated
here is what my fastboot screen reads:
***TAMPERED***
***RELOCKED***
EVITA PVT SHIP S-ON RL
HBOOT- 2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
FASTBOOT
to previous item
to next item
to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Click to expand...
Click to collapse
Since you are s-on, you need to fastboot flash boot boot.IMG from the ROM you want to use. While you're at it you may as well just s-off your device. It will make things simpler in the end. You're going to have to unlock the boot loader again to flash the boot image though. You will also want to flash recovery again via fastboot.
Sent from my One X using XDA Premium 4 mobile app
Black!Jack said:
Since you are s-on, you need to fastboot flash boot boot.IMG from the ROM you want to use. While you're at it you may as well just s-off your device. It will make things simpler in the end. You're going to have to unlock the boot loader again to flash the boot image though. You will also want to flash recovery again via fastboot.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you so much for the response...i have a couple questions. I am fairly new to android and these are the first real problems i have run into that i havent been able to solve on my own. how do i "fastboot flash boot boot.IMG"? i just want to use the stock ROM or CM10 which ever will get my phone running again. I have unlocked to bootloader again and now have access to TWRP
brenntard said:
Thank you so much for the response...i have a couple questions. I am fairly new to android and these are the first real problems i have run into that i havent been able to solve on my own. how do i "fastboot flash boot boot.IMG"? i just want to use the stock ROM or CM10 which ever will get my phone running again. I have unlocked to bootloader again and now have access to TWRP
Click to expand...
Click to collapse
Take a look at this thread
http://forum.xda-developers.com/showthread.php?t=2136172
It will answer many of the questions that you have and provides links to appropriate tools.
You should definitely s-off your device now. Just look for the question in the thread I linked for more detail. Bookmark it as well, or add it to your favorites, as it will provide a great reference point for future use.
Once you have s-off, you will just have to flash any ROM you want from recovery. It will make your life way easier.
If someone helps you, just hit the thanks button, or thumbs up from the xda app.
Sent from my One X using XDA Premium 4 mobile app
Black!Jack said:
Take a look at this thread
http://forum.xda-developers.com/showthread.php?t=2136172
It will answer many of the questions that you have and provides links to appropriate tools.
You should definitely s-off your device now. Just look for the question in the thread I linked for more detail. Bookmark it as well, or add it to your favorites, as it will provide a great reference point for future use.
Once you have s-off, you will just have to flash any ROM you want from recovery. It will make your life way easier.
If someone helps you, just hit the thanks button, or thumbs up from the xda app.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In the rumrunner instructions to s-off my device it says i need to have fast boot unchecked in settings. I am pretty sure i have it checked but there is no way for me to tell for sure...since i dont have an OS installed is this an issue?
brenntard said:
In the rumrunner instructions to s-off my device it says i need to have fast boot unchecked in settings. I am pretty sure i have it checked but there is no way for me to tell for sure...since i dont have an OS installed is this an issue?
Click to expand...
Click to collapse
You need to get a ROM booting brute trying s-off. Don't use Goo Manager to install ROMs, install manually through TWRP recovery. Once you've installed the ROM reboot to the bootloader and flash the boot.img. Here's how to flash the boot.img.
Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita.
timmaaa said:
You need to get a ROM booting brute trying s-off. Don't use Goo Manager to install ROMs, install manually through TWRP recovery. Once you've installed the ROM reboot to the bootloader and flash the boot.img. Here's how to flash the boot.img.
Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita.
Click to expand...
Click to collapse
Okay I was able to flash the boot.img but can't figure out how to flash the rom.. Should I do it through recovery? Or through a fast boot command prompt like the one used to flash the boot.img
timmaaa said:
You need to get a ROM booting brute trying s-off. Don't use Goo Manager to install ROMs, install manually through TWRP recovery. Once you've installed the ROM reboot to the bootloader and flash the boot.img. Here's how to flash the boot.img.
Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita.
Click to expand...
Click to collapse
This may go with out saying but when I'm in recovery and hit the reboot button and try to select "system" it comes up with a message telling me I have no OS installed and asks if I want to continue anyway..
Use the wipe menu in TWRP to do a full wipe (cache/dalvik/factory reset/system). Then use the install option to the install the ROM (and gapps if it's an aosp ROM). Then reboot to bootloader and flash the boot.img with fastboot. Then reboot your phone.
Sent from my Evita.
timmaaa said:
Use the wipe menu in TWRP to do a full wipe (cache/dalvik/factory reset/system). Then use the install option to the install the ROM (and gapps if it's an aosp ROM). Then reboot to bootloader and flash the boot.img with fastboot. Then reboot your phone.
Sent from my Evita.
Click to expand...
Click to collapse
How do i get the ROM onto my phone? that might be a stupid question but i am stumped
brenntard said:
How do i get the ROM onto my phone? that might be a stupid question but i am stumped
Click to expand...
Click to collapse
Mount your sdcard through TWRP. You should then be able to drag and drop the file from your computer to your sdcard. It should go without saying that your phone needs to be connected to your computer.
Sent from my One X using XDA Premium 4 mobile app
Black!Jack said:
Mount your sdcard through TWRP. You should then be able to drag and drop the file from your computer to your sdcard. It should go without saying that your phone needs to be connected to your computer.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i cant mount my sd card, i can put a little x by cache data and system but not sd card...
timmaaa said:
Use the wipe menu in TWRP to do a full wipe (cache/dalvik/factory reset/system). Then use the install option to the install the ROM (and gapps if it's an aosp ROM). Then reboot to bootloader and flash the boot.img with fastboot. Then reboot your phone.
Sent from my Evita.
Click to expand...
Click to collapse
i was unable to do a wipe of my phone. in twrp i went to wipe and "swipe to factory reset" it ran through and came back as failed..
Try to format your sd then (from recovery)
Gesendet von meinem Xperia Neo V mit Tapatalk 2
What ROM did you flash with Goo Manager?
You mount the sd card by going into the mount menu, then using the mount usb storage option.
Sent from my Evita.
Hi guys,
My sister sent me her HTC One SV aka K2-UL i offered her from expansys on june, it is stuck on Hboot
*** LOCKED***
K2_UL XA SHIP S-ON RL
HBOOT-2.00.0000
eMMC Boot
...
I can go to Fastboot USB ( or AC )
She 's worst than a noob so phone is stock, up to date but non-root non-unlock, still S-ON and so on.
just once phone reboot and stay stuck...
From here i can navigate but after reboot i'm still here.
I tried :
factory reset and recovery (with rom renamed PL80DIAG but would be too easy...)
RUU but RUU asked for bootloader so stuck on "waiting for bootloader"
go to htc dev to unlock bootloader but after flash unlock token ( unlock token check successfully) but : Nothing happens and still writtten ***Locked*** then if I "fastboot oem unlock" it says failed :<remote : loading custom splash failed>
fastboot flash boot.img but nothing works since still S-on and locked bootloader (superCID is out too)
flash custom recovey or even fresh stock recovery but nothing worked for the same reasons...
Do you guys have any idea of something i could do?
Thanks for your answer and forgive my English I'm French
As long as you are ***LOCKED*** you can quiet do nothing.
To use our available RUU you must also be unlocked & S-Off.
Somewhat the same situation
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
I can get into Fastboot as well as bootloader, I CANNOT GET INTO RECOVERY. I have tried to restore with the respective RUU files from the All things HTC ONE SV forum. I have also tried to flash the recovery boot and radio img files through fastboot usb. NONE of this has worked for me. I really enjoyed this phone before I went and made it all FUBR. If there is anyway to get it to boot to any recovery or rom, i will much appreciate it. Thanks for all your help from previous posts as well as any future help I get from information posted here.
Related to your hboot, you should be able to flash any recoveries, but i usually recommend this one.
What command do you use to flash recovery and do you get an output from "fastboot devices"?
Thedc24 said:
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
Click to expand...
Click to collapse
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.
eduardog131 said:
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.
Click to expand...
Click to collapse
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk
Modding.MyMind said:
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Well then I was right then I was wrong. Sorry. HBOOT versions for the Sensation are stuck in my mind.
Sent from my HTC Sensation
Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.
Thedc24 said:
Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.
Click to expand...
Click to collapse
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation
He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.
old.splatterhand said:
He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.
Click to expand...
Click to collapse
Wow! Awsome! This bad boy booted. I was able to flash the rom through recovery. This is much further than I expected to get with this device. Now when I try to go S-Off with either moonshine or rumrunner I get an error saying not able to make adb connection. When I use fastboot devices my device will show up...if i do adb devices nothing...Would love to have S-Off and SU installed. But like I said this is much further than I expected to get so anything further is icing on the cake. Thanks in Advance.
Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?
old.splatterhand said:
Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?
Click to expand...
Click to collapse
He can just use the Naked Driver for the adb driver. http://forum.xda-developers.com/showthread.php?t=2263822
Ok I DID have USB debugging enabled. After messing with the drivers and my Windows 8 computer, I have came to the conclusion that it is something with the drivers and their compatibility with Windows 8. Either way moonshine or rumnunner never worked for me in a windows 8 environment. I dual boot ubuntu 12.04 anyway, it saw my device just fine adb and fastboot. I ran moonshine and it went through all the testing stages, but was never able to completely run...so I still have no S-Off. Do I need to update Hboot or anything? Also am I able to load a custom rom on this device with S-ON? I have been looking but I do not see many out for this device at all, which is a shame because I feel as though it is very comparable to my GS3. It would be nice to see a nice AOSP ROM on this device. But all take any updates I can for the device, hopefully it will help with the issue I have will cell reception dropping all the time. Thanks
To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!
old.splatterhand said:
To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!
Click to expand...
Click to collapse
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
eduardog131 said:
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation
Click to expand...
Click to collapse
Yea that would be cool. I am assuming I would just flash it through recovery?
Thedc24 said:
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
Yea that would be cool. I am assuming I would just flash it through recovery?
Click to expand...
Click to collapse
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk
eduardog131 said:
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?
Thedc24 said:
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?
Click to expand...
Click to collapse
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)
eduardog131 said:
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)
Click to expand...
Click to collapse
Downloading now. I will let you know how it goes...thanks a million.
This is what I got when I tried to flash the rom:
sending 'zip' (691470 KB)...
OKAY [ 37.267s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 37.301s
I dont understand if I am S-Off and super CID.