yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] redd12345:
Hi all,

Here are the two files that you will need to have onscreen ICS buttons and disable the capacitive buttons on the bottom.

Directions and Disclaimer:

I have only used this on Alien ICS 4.0.4 Stock/DeOdexed/Zipalign/Root/Busybox

I am not responsible for your efforts/errors

- THE FILE BELOW IS NOT A FILE THAT CAN BE FLASHED.

- copy both files from the .zip file to /sdcard

- enable debugging on your phone, from a command prompt type the following

- from a command prompt, pull the two original files and save them as a backup!

adb pull /system/framework/framework-res.apk

adb pull /system/usr/keylayout/Generic.kl

- then do the following

adb shell

su

mount -o remount,rw /dev/blk/mmcblk0p24 /system

cp /sdcard/framework-res.apk /system/framework/framework-res.apk

chmod 644 /system/framework/framework-res.apk

cp /sdcard/Generic.kl /system/usr/keylayout/Generic.kl

chmod 644 /system/usr/keylayout/Generic.kl

reboot recovery

- from recovery, wipe cache and wipe dalvik under advanced

- after device reboots, I Highly recommend using Rom toolbox to change your DPI to 190

- you will need to download exDialer and CameraICS from the market

- also, the stock SMS app will NOT allow you to change your settings, so either turn off the notifications first and switch to a different SMS app that supports ICS or set it the way you want and then do this.

- I personally use Apex Launcher, but other Launchers that resize are fine. I believe that TouchwizUX is ok to use, but haven't tried that yet.

Hope this helps, and developers please use this, as I have taken from you all as well. Thanks to Evilisto for his tutorials.

Redd.

Skyrocket - UCLE2 Alien Stock with ICS onscreen keys and APEX launcher
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Grut:
Thanks for the work, this should be good! Can't wait to try this out!!!!!! :D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] CAYCE_VII:
Is there anyway to do this on the t mobile galaxy s ii? I'm on aokp so even just disabling the capacitive buttons would be nice
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Khizar:
+1
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] aSquard:
Interesting and I would love to try this, BUT the computers at the job have disabled the USB ports (except for charging) so no command prompts can be run :(

Does this mod add a "Menu" button with the on-screen keys like the Galaxy Nexus? So we can still do Menu>Settings and such?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Jessical:
I know I sound like an a for asking, but can you please make this flashable? :) My Mac does not like Su and always denies her.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] john9:
That's great. thanks for share.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] redd12345:
Responses to questions.

I will try to work on a flashable .zip file soon. As far as working on a SGS2, my recommendation would be to go into the /system/usr/keylayout/ and copy General.kl file. Make sure to have a backup of this file. Download Notepad++ to edit this file on a computer and look for the following

MENU

HOME

SEARCH

BACK

and put a # in front of each of those "key 103 (whatever number it is)" lines

then save the file and push it back to the /system/usr/keylayout directory like I mentioned in the directions and chmod 644 /system/usr/keylayout/General.kl to fix the permissions on it and make it the same as other system files. Also, reboot your device and clear dalvik and wipe cache.

As far as making a menu key, no, this will not do that. This is purely AOSP stock options that are enabled by decompiling and reverse engineering. The menu button will make itself available in the upper right corner of almost every app, with the exception of the stupid samsung sms, which i mentioned before.

Hope I answered everyone's questions!

Redd.

Skyrocket -- Alien UCLE2 Stock/Rooted/blah-blah

PS. Samsung shelved the Skyrocket HD and called it the Galaxy S3 because the quad-core didn't pass FCC in the united states. So make sure NOT to rush to your local stores to get a phone THAT YOU ALREADY HAVE! kthxbye. :p
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Jessical:
Any update on this? :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] lunchbox201:
Hi OP,

Any update on the progress at making a flashable zip ?
[HTC Sensation] Mr-YC:
i would like to ask whether anyone can help me with this or at least tell me whether it is possible to edit or not.

Volume Step sound in Sense 4.0 is "do re mi fa so la ti", total/max 'steps' count is 7. Original files name in '/system/media/audio/ui' are 'Volume-1.aac' to 'Volume-7.aac'

But after changing Volume Step in Tweak to "Finest", the max count became 15. Then the Volume Step sound became "do re mi fa so la [(ti) x 9]"

I wish to customize/add Volume Step sound of 8th step and above, so i played around with those "Volume-*.aac" in '/system/media/audio/ui/'. I tried duplicating those files and rename up to "Volume-15.aac" and restarted device, but there is no effects.

Which file (for example build.prop) in '/system/' should i edit, in order to make 'Volume-8.aac' to 'Volumn-15.aac' work?

Thanks in advance.
[HTC Sensation] GROGG88:
In order to add that resource I'm guessing you'll need to edit Settings.apk>res/xml/soundsettings.xml

The device will not play a resource that doesn't exist in the base.
[HTC Sensation] GROGG88:
I'd need to search around for it. Keep looking for now, I won't have time until the weekend.
[HTC Sensation] Mr-YC:
GROGG88,

after cross-checking titles in '\res\xml\sound_settings.xml' with '\res\values\strings.xml', I found out that editing sound_settings.xml doesn't help.

Can you please check it out?

Thank you very much =)
[HTC Sensation] GROGG88:
I'll put it on my list of things to do. I'm out of town right now...
[HTC Titan] barikatdiss:
you get the device was installed from Turkey android htc titan: D

prepared by video sinan friend ctrlpda site

[YOUTUBE]chw-xJjjV5k[/YOUTUBE]
[HTC Titan] titi66200:
Yes but http://xdaforums.com/showthread.php?t=1695242
[HTC Titan] JigsterNL:
Is my dream coming true?
[HTC Titan] GuestK00161:
I really think this is fake...maybe possibly the cases were switched???
[HTC Titan] Haos:
how to put out the board ftom the screen i think is real but i wont a link only videos lets speak the developers;)
[HTC Titan] olyloh6696:
If you wanted android, why not just get the Sensation XL?

Desire S • Fallout V2.0.0 • xda premium
[HTC Titan] tai4de2:
Choice is bad. Android on WP hardware is an abomination.
[Sprint HTC EVO 4G LTE] cubbieswin:
Ladies and gentlemen,

I just watched this YouTube video about the founder of Fark.com and his fight against a "patent troll". Although it has nothing to do with Apple, HTC, or Sprint, I found it interesting given what we went through with our phones. I thought you guys might appreciate this as well. :)

http://www.youtube.com/watch?v=E_lb3D7Ay-M&feature=youtube_gdata_player

Sent from my New School EVO LTE
[Sprint HTC EVO 4G LTE] starplaya93:
Wow this was very insightful... I really don't understand how a patent system can be as terrible as what's currently in place. It kind of parallels how major corporations spend a ridiculous amount of money on lobbying to sway things in their favor. It's soooooooooo far from ideal or even slightly fair, but the smaller guy never stands a chance /: Capitalism at its best I suppose
[HTC Vivid, Raider, Velocity] bobmutch2:
Its not clear to me if I need recovery my soft-bricked HTC Raider by doing a PH39DIAG.zip or running the right RUU???

With the RUU I get the following error:

"RUU, Security fail! Update fail!"

With the PH39DIAG.zip I don`t know where to get one.

Heeeeeeeeeeeeeeeeeeeeeelp!
[HTC Vivid, Raider, Velocity] RagnarDanneskjold:
If the RUU isn't working you probably need to flash the appropriate kernel. Were you using the all-in-one-toolkit? Try flashing back to the stock kernel, and run the RUU.
[HTC Vivid, Raider, Velocity] bobmutch2:
>>>If the RUU isn't working you probably need to flash the appropriate kernel.

I bought the phone soft-bricked to hboot. RUU is giving me the error I posted. I don`t know what ROM is on it so I don`t think I need to flash a kern.

Here are the things I have tried so far.

My HTC Raid (I am in Canada so don't know if this is a Bell or Rogers or who knows, I bought it white screened) is stuck in white screen with HTC logo. I took

the following steps:

Downloaded RUU_Holiday_Rogers_WWE_1.65.631.1_Radio_1.11.1020.03_30.77.551061.02L_release_219561_signed.exe

from

http://hotfile.com/dl/145619873/245....77.551061.02L_release_219561_signed.exe.html

--Ran RUU and the program noted I have image version 1.65.566.3 on my Radier

--Selected Update and tried to update to 1.65.631.1

--The Raider came up in the HTC/black backgroup and then gave the following ERROR[155] UNKNOWN ERROR.

--After exiting RUU and disconnecting the cable the phone shows along with the general hboot information on the phone "RUU, Security fail! Update fail!"

--Restarted phone with volumn down and power and it came up in hboot and showed the following error:

SD Checking

Loading...[PH39DIAG.zip]

No Image!

Loading...[PH39DIAG.nbh]

No image or wrong image!

Loading...[PH39IMG.zip]

No image!

Loading...[PH39IMG.nbh]

No image!

Loading...[PH39IMG.tar]

No image!

Loading...[PH39IMG.aes]

No image!

--I tried re-locking the bootload with "fastboot oem lock" and I get a "..." after the command and nothing else happens. Waited for 10 minutes.

--Also "adb devices" shows no devices.

--Installed HTCSync, started HTCSync, pluged in hbooted HTC Raider, Drivers Software Installation diolog box shows "My HTC" driver installed, still nothing when

I run "adb devices"

--Ran "fastboot oem lock" and get the following.

(bootloader) Lock successfully...

FAILED (status read failed (No such file or directory))

finished. total time: 0.026s

--When I run Hasoon2000s HTC Vivid AIO Kit v1.2 Relock Bootloader I get the following.

INFOLock successfully

FAILED (status read failed (Too many links))

finished. total time: 0.022s

--With Hasoon2000s HTC Vivid AIO Kit v2.0 I get.

INFOLock successfully

FAILED (status read failed (Unknown error))

finished. total time: 0.023s

--reboot into hboot and status still "*** UNLOCKED ***"
[HTC Vivid, Raider, Velocity] Cor-master:
hmmm, I haven't messed with this sort of thing of the Vivid so much, but I have on the flyer, and I've gotten the soft brick white HTC screen too, and typically what it means is the Hboot version doesn't support the firmware on there. I got no link but perhaps the developers have the Hboot version your looking for with the firmware you got.

Can you get into fastboot? If you can its just a matter of flashing the Hboot with ADB and then running the RUU
[HTC Vivid, Raider, Velocity] bobmutch2:
yes I can get into fastboot.

The hboot version i have is the same as my other Raider that is on rogers. On the working Raider I have 1.65.631.1 software number, 2.3.4 android version, 3.0 Sense, 2.6.35.13-gc1166ee kernel version, 1.11.1020.03_03.77.551061.02L bb, 1.65.631.1 CL175411 release-keys build number.

So the hboot is the same on both of them, they are both unlocked, and the working one has HOLIDAY PUT SHIP S-ON RL

don`t know if that helps or not.
[HTC Vivid, Raider, Velocity] Maqical:
The Reason You Are Getting That Error is because your bootloader is still unlocked, go into hboot go into fastboot and plug in via usb and it should say "Fastboot USB" in red then run the ruu.... once completed do a battery pull, go back into hboot unlock bootloader again, then install a custom recovery (i recommend WildChild's) then if you plan on using a custom rom... use a kernel supported or use the rom's kernel in the zip "Boot.img" flash that kernel put the rom on your sd card or go into wildchilds recovery go to enable usb-ms and enable internel sd card and put the rom in there disable usb-ms go to wipe clear the two caches then go into the main menu flash zip menu internel or externel sd card select the rom and install and you are good to go ! anymore help pm me i can help greatly

---------- Post added at 03:36 AM ---------- Previous post was at 03:24 AM ----------

Hmm sounds like you do not have the right htc drivers installed download the all in one tool kit and run the first few steps ! Download your ph39img.zip here http://goo.im/private/iomonster/htcvivid/roms/ics-ota/PH39IMG.zip
[HTC Vivid, Raider, Velocity] bobmutch2:
>>>The Reason You Are Getting That Error is because your bootloader is still unlocked

no it is *** UNLOCKED ***

>>>go into hboot go into fastboot and plug in via usb and it should say "Fastboot USB" in red

Yes

>>>then run the ruu....

times out with an error, here is my RUU

RUU_Holiday_Rogers_WWE_1.65.631.1_Radio_1.11.1020.03_30.77.551061.02L_release_219561_signed.exe

>>>Download your ph39img.zip here

what do I do with it. I put it on the sdcard and did a bootload and it gives the following errors.

SD Checking

Loading...[PH39DIAG.zip]

No Image!

Loading...[PH39DIAG.nbh]

No image or wrong image!

Loading...[PH39IMG.zip]

No image!

Loading...[PH39IMG.nbh]

No image!

Loading...[PH39IMG.tar]

No image!

Loading...[PH39IMG.aes]

No image!
[HTC Vivid, Raider, Velocity] Hunt3r.j2:
Flash a proper recovery, then flash an gingerbread Vivid custom ROM and immediately flash the appropriate boot.img to go with it.

If it boots, you know you're on GB. Relock the bootloader in fastboot and run either the Telus or Bell ruu for GB. Try both before coming back.
[HTC Vivid, Raider, Velocity] bobmutch2:
>>>Flash a proper recovery,

I have flashed a number of proper recovery images.

From Vivid all in one kit v2.1 http://xdaforums.com/showthread.php?t=1498003 I have tried to flash

recovery-cwm-vivid-5.5.0.4B2.img

wcxrecovery.img

and recovery.img from a back up by cwm on my other working Raider

"fastboot devices" gets me "HT1ALVJ03540" and when I go to fastboot on the hboot menu I get "FASTBOOT USB" in red.

I have used "fastboot flash recovery filename.img"

After all these flashes when I boot into hboot and select RECOVERY and press the power key it show a white screen with a green htc and then with in 1 sec goes back into hboot.

Prehaps is is of interest than when I run the RUU RUU_Holiday_Rogers_WWE_1.65.631.1_Radio_1.11.1020.03_30.77.551061.02L_release_219561_signed.exe it tells me I have image version 1.65.666.3 installed and wants to put 1.65.631.1 -- you can see that from the image name and the getvar all output below

Also I have extracted the rom.zip following http://www.htcsensationforum.com/htc-sensation-rooting/how-to-extract-rom-zip-from-ruu/ from this RUU and renamed it PH39DIAG.zip and when it loads it hboot gives an "Wrong zipped image!" after "Checking..[PH39IMG.zip]"

Here is my fastboot getvar all info

INFOversion: 0.5

INFOversion-bootloader: 1.83.0014

INFOversion-baseband: N/A

INFOversion-cpld: None

INFOversion-microp: 0360

INFOversion-main: 1.65.666.3

INFOserialno: HT1ALVJ03540

INFOimei: 358730040049371

INFOproduct: holiday

INFOplatform: HBOOT-8260

INFOmodelid: PH3915000

INFOcidnum: BM___001

INFObattery-status: good

INFObattery-voltage: 4075mV

INFOpartition-layout: Generic

INFOsecurity: on

INFObuild-mode: SHIP

INFOboot-mode: FASTBOOT

INFOcommitno-bootloader: ccb23700

INFOhbootpreupdate: 11

INFOgencheckpt: 0

all: Done!

finished. total time: 0.514s

The image that is on this bricked Raider appears to be a bell ICS ROM.

OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip

http://xdaforums.com/showthread.php?t=1672800

When I run RUU I get a "ERROR 155 UNKNOWN ERROR" in the RUU program and if I unplug the phone it shows RUU Security fail! Update fail!

>>>then flash an gingerbread Vivid custom ROM and immediately flash the appropriate boot.img to go with it.

I cant get a recovery to take so I am guessing I need to fix that before going on to a custom ROM?
[HTC Vivid, Raider, Velocity] RagnarDanneskjold:
I had a similar problem with bell ics bootloop. I flashed kozmicks r2 from fastboot, and used darkraider 1.5.4.zip from recovery. Device was s-on at the time.
[HTC Vivid, Raider, Velocity] bobmutch2:
@RagnarDanneskjold you have links to those two files
[HTC Vivid, Raider, Velocity] Maqical:
Kernel http://xdaforums.com/showthread.php?t=1572015

Dark Raider http://xdaforums.com/showthread.php?t=1586613
[HTC Vivid, Raider, Velocity] RagnarDanneskjold:
@Maqical

Thanks.

If you are still having trouble you can PM me.
[HTC Vivid, Raider, Velocity] bobmutch2:
The kernel didn`t take.

>>>flash the kernel from fastboot

Here is what I get when I flash the kernel

"fastboot devices"

gets me "HT1ALVJ03540"

"fastboot flash boot Kernels/KozmiKKernel-RC2.zip"

gets me

sending 'boot' (5480KB)... OKAY [1.332s]

writing 'boot' ... FAILED (remote: image error! (BootMagic check fail))

finished. total time: 1.652s
[HTC Vivid, Raider, Velocity] Maqical:
Not exactly sure so dont depend on me for this.. but when i flash my kernels i have a "boot.img" and you put it in with the files for fastboot and i open a command window and type "fastboot flash boot boot.img, you're flashing a zip
[HTC Vivid, Raider, Velocity] RagnarDanneskjold:
Refer to this link:

http://xdaforums.com/showthread.php?t=1416836

Find the boot.img file for kozmicks kernel. You can download it or extract it from

darkraider.zip.

Place the boot.img file in you fastboot folder on your computer.

Run the following commands in fastboot

fastboot flash boot boot.img

fastboot reboot

Now you must flash a custom recovery. CWM, or WCX will work.

You can use all-in-one-toolkit to do this.

From recovery install darkraider from .zip.

Folllow instructions, use defaults.
[HTC Vivid, Raider, Velocity] bobmutch2:
@RagnarDanneskjold

In darkraider_v1.5.5.zip there is 5 kernels faux, holics, kozmikb7, kozmikrc2, and stock, they all have boot.img but kozmik b7 and rc2?

Which one would I use?
[HTC Vivid, Raider, Velocity] bobmutch2:
I am not sure if have read all I have posted. I cant write stuff to this device. kernels dont take, recovery images dont take, the PM39IMG.zip doesn`t take. There is some issues here more than just finding the right files to flash.
[HTC Vivid, Raider, Velocity] RagnarDanneskjold:
I used 1.5.4 because s-on compatibility has been dropped in newer versions, (so I understand?), so I would use that version. Take the boot.img from kozmiksrc2. Make sure you select it when installing darkraider.
[HTC Vivid, Raider, Velocity] Maqical:
A Kernel of your choice.. but for now just until you get the phone working i would use stock
[HTC Vivid, Raider, Velocity] RagnarDanneskjold:
http://xdaforums.com/showpost.php?p=25676147&postcount=6
[HTC Vivid, Raider, Velocity] bobmutch2:
I am wondering if you guys are reading my posts at all.

Like I have noted over and over that I cant flash a rom, a kernel, a recovery, and I have shown the errors that happen when I do.

So like I said before it appear there is issues more than just flashing the wrong files.

"fastboot flash boot Kernels/KozmiKKernel-RC2.zip"

gets me

sending 'boot' (5480KB)... OKAY [1.332s]

writing 'boot' ... FAILED (remote: image error! (BootMagic check fail))

When I run RUU I get a "ERROR 155 UNKNOWN ERROR in the RUU program and if I unplug the phone it shows RUU Security fail! Update fail!

Downloaded RUU_Holiday_Rogers_WWE_1.65.631.1_Radio_1.11.1020.03_30.77.551061.02L_release_219561_signed.exe from

http://hotfile.com/dl/145619873/245....77.551061.02L_release_219561_signed.exe.html

SO lets figure out the first file I am to flash and deal with that one and why it is not taking.

So is it a boot.img, a keneral, a ROM, a RUU, what is the first and how do I do it, and then lets deal with the error that will produce.

Keep in mind while I am not an android expect I have been in IT for 25 years. I have about 13 hours in on this project, I have read parts of about 50 xda threads, I have had a couple of people from irc freenode android-root try to walk me through this one.

But having said that thanks for all you help so far.
[HTC Vivid, Raider, Velocity] bobmutch2:
Here is my fastboot getvar all info:

INFOversion: 0.5

INFOversion-bootloader: 1.83.0014

INFOversion-baseband: N/A

INFOversion-cpld: None

INFOversion-microp: 0360

INFOversion-main: 1.65.666.3

INFOserialno: HT1ALVJ03540

INFOimei: 358730040049371

INFOproduct: holiday

INFOplatform: HBOOT-8260

INFOmodelid: PH3915000

INFOcidnum: BM___001

INFObattery-status: good

INFObattery-voltage: 4075mV

INFOpartition-layout: Generic

INFOsecurity: on

INFObuild-mode: SHIP

INFOboot-mode: FASTBOOT

INFOcommitno-bootloader: ccb23700

INFOhbootpreupdate: 11

INFOgencheckpt: 0

Here is what my phone says at hboot:

*** UNLOCKED ***

HOLIDAY PUT SHIP S-ON RI,

HBOOT-1.83.0014

MICROP-0360

eMMC-boot

Sep 21 2011, 15:34:37
[HTC Vivid, Raider, Velocity] RagnarDanneskjold:
I'm not an expert. I've been looking for a solution to your problem.

I think you are using the wrong the HBOOT.

Check out this link.

http://xdaforums.com/archive/index.php/t-1543190.html
[HTC Vivid, Raider, Velocity] bobmutch2:
@RagnarDanneskjold

Here is the image that is current on the bricked Raider so I am guessing the phone is a bell mobility phone hence the BM.

OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip

http://xdaforums.com/showthread.php?t=1498003

the "fastboot getvar all info" on the bricked phone shows version-main: 1.65.666.3

here is the hboot info on my bricked Raider

*** UNLOCKED ***

HOLIDAY PUT SHIP S-ON RI,

HBOOT-1.83.0014

MICROP-0360

eMMC-boot

Sep 21 2011, 15:34:37

here is the hboot info on my Rogers working Raider

*** UNLOCKED ***

HOLIDAY PUT SHIP S-ON RL,

HBOOT-1.83.0014

MICROP-0360

eMMC-boot

Sep 21 2011, 15:34:37

The only difference is the S-ON is RI on the bricked Bell Mobility??? phone and RL on the working Rogers phone.

So I am wondering if this means anything, also I am wondering what the RI and RL mean.

So I am thinking unless you need to have a different hboot on a bell then a rogers that my bricked hboot version is fine.

Here is the "fastboot getvar all info" on the bricked phone...

INFOversion: 0.5

INFOversion-bootloader: 1.83.0014

INFOversion-baseband: N/A

INFOversion-cpld: None

INFOversion-microp: 0360

INFOversion-main: 1.65.666.3

INFOserialno: HT1ALVJ03540

INFOimei: 358730040049371

INFOproduct: holiday

INFOplatform: HBOOT-8260

INFOmodelid: PH3915000

INFOcidnum: BM___001

INFObattery-status: good

INFObattery-voltage: 4075mV

INFOpartition-layout: Generic

INFOsecurity: on

INFObuild-mode: SHIP

INFOboot-mode: FASTBOOT

INFOcommitno-bootloader: ccb23700

INFOhbootpreupdate: 11

INFOgencheckpt: 0

all: Done!

finished. total time: 0.514s

Here is the "fastboot getvar all info" on the working Rogers phone...

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.83.0014

(bootloader) version-baseband: N/A

(bootloader) version-cpld: None

(bootloader) version-microp: 0360

(bootloader) version-main: 1.65.631.1

(bootloader) serialno: HT1AVVJ18594

(bootloader) imei: 358730040304362

(bootloader) product: holiday

(bootloader) platform: HBOOT-8260

(bootloader) modelid: PH3915000

(bootloader) cidnum: ROGER001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4185mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: ccb23700

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.516s
[HTC Vivid, Raider, Velocity] RagnarDanneskjold:
RI means radio-intermediate. The RL you are seeing on your Rogers phone means radio-loud. I do not think this is the source of the problem, but may hint at how your device was soft-bricked?