• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root bricked HTC One SV (boost mobile) - HELP!!!

metlhed0

metlhed0

Lurker
Hello! I have succussfully rooted many times, and I am at a COMPLETE loss...can anyone help unbrick this phone with a functional bootloader?
 
Hello metlhed0. I've moved your thread to the HTC One SV root forum for more specialized help. I don't particularly have much expertise with HTC devices, but I know another staff member that does. I'll shoot him a PM and direct him here to help you out.
 
Hey there,

I don't have this device but have some HTC experience so I'll try to get the ball rolling. If I can't help, maybe the information I ask for below will help someone else help you.



Can you post a couple things here?

1.) Any specific information you have about the issue... What state was your phone in before the "brick" and what were you doing when it happened. If you were rooting, what method/guide were you using? If you were already rooted were you changing roms, modifying a system file, etc...? The more information we have the better we can get you fixed up.

Good news is, if you can still access the bootloader you will most likely be fine.



2.) Can you post the information on your bootloader screen? 4 or 5 lines of text, whatever it is on this device.



3.) Can you put the phone in fastboot mode from the bootloader? If so, can you run a fastboot getvar all and copy/paste that information from command prompt?


Without knowing most of this information, I can't really tell you where to start or what might be the best first step to take. Even if we have to run an RUU to repair the device, I don't know which one your phone would need.


Thanks!! :)
 
Thank you so much for responding, guys!
Ok, here is what's going on. I wanted to root this phone, so step 1 is the bootloader unlocking procedure. I used HTC Bootloader Unlock v0.1.0.1800.
This went ok and it unlocked the phone, but it was then "tampered" and still S-ON. At this point I still had the OTA update of JB 4.2.2 and HBOOT 2.21, along with a working recovery of TWRP v2.7.1.0.

I tried a variety of things to remedy the S-ON situation - (moonshine, HTC One all-in-one, but these programs all seemed to require S-OFF. Somewhere down this path, I decided that maybe I could flash a rom through recovery. this was my downfall.
As near as I can determine, the HTC OTA update not only updated the android version, but the HBOOT as well. Every rom I can find seems to demand S-OFF and an ICS HBOOT version. I got very frustrated with this knowledge which let me down yet another dark path.
I used the All-in-one tool to flash the factory RUU .zip.This was a HUGE failure, I guess because then I had NO recovery, S-ON, tampered, AND security warning!
Since then I now have a working recovery(the aforementioned TWRP, and am unlocked.
Here is my bootloader info:
***TAMPERED***
***UNLOCKED***
K2_CL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.12.50.0516
OpenDSP-v10.2.0268.0401
OS-
eMMC-boot 1024MB
Apr 14 2014,18:55:20.0

Any help to root this thing would be greatly appreciated!!!!!!!!!!!!!!!
 
Here is the getvar all information:

version-baseband: 1.12.50.0516
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HTxxxxxxxxxx
imei: [REMOVED]
meid: [REMOVED]
product: k2_cl
platform: HBOOT-8930
modelid: PL8011000
cidnum: SPCS_003
battery-status: good
battery-voltage: 4246mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dc34ae5
hbootpreupdate: 11
gencheckpt: 0
 
Sorry, I just caught this and I'm on my way out the door. The thing about the RUU failing, is that because you are s-on, you have to re-lock the bootloader first.

I'd have to do some research about s-off but someone else will probably chime in that knows more about it for this device.


The most likely cause for you getting stuck after the rom flash is because of s-on. As long as you're flashing a compatible rom, you just need to flash the boot.img separately.

There are two ways to accomplish this:
1.) Make sure your recovery.img is in the fastboot directory on your pc. Connect the device and use this command: fastboot boot recovery.img [make sure recovery.img is the exact name of the img file or rename the file to recovery.img...

2.) Place a copy of the rom.zip on your pc. After flashing the rom, extract the boot.img from your rom.zip and place in the fastboot directory. Use this command: fastboot flash boot boot.img

The rom should boot after that. With s-off, this isn't an issue. I prefer method one as both require a PC and it's easy to just leave the recovery.img in the proper directory. Plus it saves a step. You don't have to transfer the boot.img every time. There is no need to flash the boot.img separately if you boot recovery using method 1.


In case it's needed, I think this is the correct RUU: AndroidRUU | The #1 source for Android RUU files

I'd hold off on that though, and only RUU as a last resort.


My guess is after you flashed the rom the first time, you would have been fine had you flashed the boot.img.
 
Thanks Brian, that is indeed the correct ruu.

Couple of things to add. :)

With our current bootloader
Code: 
fastboot boot recovery.img
isn't working. There's an additional command we need to use (that hasn't been figured out yet)

I have also made a thread with a flashable, rooted stock rom.zip

http://androidforums.com/showthread.php?t=854609

Is that the rom you tried? Because, currently is the only fully functional rom we (boost users) have for 4.2.2

I think i read somewhere (i believe a post by moddingmymind) that said we need a specific version of rum runner for s-off (however i can't find that post, I'm going to ping him for confirmation)

Another option is to ruu back to 4.1.2 and then use moonshine to get s-off and take the ota update to the newest firmware.
 
Brian706 said:
Lv, can he ruu back while s-on? Or can you get away with lowering the main version or something?
Click to expand...

Hmmmm, that's actually a good question. When I did it I was s-off. I suppose since its official and signed, it should work (in theory)

No :o

Thanks moddingmymind
 
The only way an RUU will work for someone who is S-On is if the RUU is based on the same OS that your device is currently using or greater. If the RUU requires a downgrade (more specifically a downgrade with the HBoot) then this will not be possible unless you are S-Off. Certain images must be written and the HBoot will not allow the change.

To S-Off your device click the link below for the prerequisites:

http://rumrunner.us/instructions/

When you are ready then click this link and search for HTC Universal Downloads. If using linux download the version made for linux. Or if windows then the one which is made for windows.

http://rumrunner.us/downloads-2/
 
metlhed0, you will not be able to use the ruu while S-On because the RUU for our device is based on 4.1.2 and after reviewing your shared info, your bootloader currently displays that you are on 4.2.2
 
as far as wich version of rum runner,what board layout does this device have? if the security flag is in p3,use the universal,if its in p7,youll need to use the one v download. i can help you guys figure it out,if need be(tho sounds like modding has some experience with it)

as far as the bricked phone,seems like 2 options:
1)flash LVs rom,with the boot image seperately as described by brian (the #2 way)

2)if one of you guys with a working JB device wants to DD your boot and system images,we can pack them up and make a "mini ruu" of sorts he can flash with fastboot/ruu mode with the unlocked bootloader.

either should work,since hes still s on its unlikely anything important has been FUBARed ;)
 
Dear Lord.......SUCCESS!!!!!!!!!!! The phone lives again!Thank you so much guys! LV's rom flash along with flashing the boot.img through command window did the trick...and thank God, too!(my wife's phone). I will now attempt the rumrunner, as I am still S-ON and would like to flash a cool kitkat rom like I have on my old Galaxy S2 (VANIR AOSP 4.4.4). Does anyone know of such roms for this phone?

Much love,
MetLheD0
 
metlhed0 said:
Dear Lord.......SUCCESS!!!!!!!!!!! The phone lives again!Thank you so much guys! LV's rom flash along with flashing the boot.img through command window did the trick...and thank God, too!(my wife's phone). I will now attempt the rumrunner, as I am still S-ON and would like to flash a cool kitkat rom like I have on my old Galaxy S2 (VANIR AOSP 4.4.4). Does anyone know of such roms for this phone?

Much love,
MetLheD0
Click to expand...

awsome sauce! glad you are up and running :cool:

before you run rumrunner,we should determine a couple of things:
1)most importantly,does LVs rom have an insecure kernel? if not,well need to remedy that.
2)well,i guess this is prolly just as important ;) we need to determine wich download you need to use. modding,lv,do you know where the secure flag lives? or have you had success with the universal download?
 
metlhed0 said:
Dear Lord.......SUCCESS!!!!!!!!!!! The phone lives again!Thank you so much guys! LV's rom flash along with flashing the boot.img through command window did the trick...and thank God, too!(my wife's phone). I will now attempt the rumrunner, as I am still S-ON and would like to flash a cool kitkat rom like I have on my old Galaxy S2 (VANIR AOSP 4.4.4). Does anyone know of such roms for this phone?

Much love,
MetLheD0
Click to expand...

There is currently no custom Rom for this device. There has been no one as of yet with either the time/patience or skills required to build such roms for this device.

I am currently working on a mod for our device, but it is merely gaining f2fs support for the kernel, TWRP and the Rom being f2fs compatible. Currently our /system, /data, /and cache focus on ext4. I have the intention of changing this merely because of the reports I have heard in regards to f2fs being smoother and faster.
 
scotty85 said:
awsome sauce! glad you are up and running :cool:

before you run rumrunner,we should determine a couple of things:
1)most importantly,does LVs rom have an insecure kernel? if not,well need to remedy that.
2)well,i guess this is prolly just as important ;) we need to determine wich download you need to use. modding,lv,do you know where the secure flag lives? or have you had success with the universal download?
Click to expand...

It is my understanding that the secure flag lives in the radio while the HBoot communicates the flag. By modding the HBoot you could cause it to ignore the secure flag so that it thinks it is S-Off however, our device won't just simply let you write to your HBoot partition without some trickery involved and since RumRunner, Moonshine, etc, etc are closed sources I personally have not taken the time to look further in to this.
 
Oh, and Rumrunner Universal will work for 4.2.2 for our device. Moonshine won't work because the binaries used in it's source are constructed for a specific Rom version lesser than 4.2.2.
 
If anyone knows of any open sources in this regard let me know and I will tear it apart. Until then, good luck since people like to be stingy like Windows lol. I enjoy linux for it's open source, but cannot stand closed sources. A big pep peeve of mine.
 
ModdingMyMind said:
It is my understanding that the secure flag lives in the radio while the HBoot communicates the flag. By modding the HBoot you could cause it to ignore the secure flag so that it thinks it is S-Off however, our device won't just simply let you write to your HBoot partition without some trickery involved and since RumRunner, Moonshine, etc, etc are closed sources I personally have not taken the time to look further in to this.
Click to expand...

cool,thanks for the info.

its pretty much impossible to mod hboot on newer devices,as its signiture is checked by other partitions as the phone boots,and a modified hboot will throw a huge flag and put the phone into a processor "do not boot" mode(read: hard brick :eek:)

the secure flag used to live in the radio nvram,but has not for some time.

the one v download has worked on other devices containing the old layout(desire c for one) and the universal download has worked on many also,such as the rezound.

we dont really need to pry into rumrunners code... the important aspects of it are a new enuff kernel(ICS+ ),that kernel to be insecure,and to know wich download to use.

if you guys want to give me results of:

cat /proc/emmc

cat proc/partitions

and then dump p3 and p7,upload,and pm me a link i can take a look and tell you where the flag is/what download to use.

if we can get one of the tools to work,i can also help you guys with the lock flag(so you can set it back to stock locked) and remove your tampered banner :)
 
ModdingMyMind said:
Oh, and Rumrunner Universal will work for 4.2.2 for our device. Moonshine won't work because the binaries used in it's source are constructed for a specific Rom version lesser than 4.2.2.
Click to expand...

scratch the above... if the universal download has worked,we know what board layout you have. ninja posted! :o

but if youd like to dump some things,i can help you find the flags :)
 
The lock flag and tampered flag is already a go. I posted a guide on that a few months back over on xda and then when I joined up over here I decided to copy and paste. That was back when we were on 4.1.2 but the process is still the same with 4.2.2 so there was no need for me to update either threads.

Here is /proc/emmc from our K2_CL variant. The other K2 variants are slightly different.

Code: 
 u0_a71@android:/ $ cat /proc/emmc
dev:        size     erasesize name
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffe00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
mmcblk0p35: 54fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p36: 0dfffe00 00000200 "cache"
mmcblk0p37: 49fffe00 00000200 "userdata"
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p38: 1097fe000 00000200 "fat"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p32: 01900000 00000200 "carrier"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p23: 00400000 00000200 "modem_st1"
mmcblk0p24: 00400000 00000200 "modem_st2"
mmcblk0p31: 00040000 00000200 "skylink"
mmcblk0p32: 01900000 00000200 "carrier"
mmcblk0p33: 00100000 00000200 "cdma_record"
mmcblk0p34: 04729a00 00000200 "reserve"
u0_a71@android:/ $
 
You must log in or register to reply here.
Back
Top Bottom