yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Q&A, Help & Troubleshooting] Athrun88:
I would call customer support and demand a supplementary phone or threaten to cut your service. If they won't hook you up with a rental during the time you're apart from your phone that THEIR update broke, then IMO, they're not worth your business.
[G2 and Desire Z Q&A, Help & Troubleshooting] David Dee:
Try q&a in the android development section. Make sure to provide all info.
[G2 and Desire Z Q&A, Help & Troubleshooting] PaganAng3l:
There is a pc10img of the gingerbread update that may unbrick your phone as long as it wasn't on it already, because this one's build number is lower and your bootloader wouldn't accept it being s-on
[G2 and Desire Z Q&A, Help & Troubleshooting] jaetelha:
If possible, try contacting HTC's support and see if they can send you a PC10IMG.zip file you can put on your SD card.
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
HTC support just defacto sent me to Bell Technical support.

Bell Technical support is supplying me with a replacement smart phone while mine is in for this warranty "repair". I was just hoping to avoid the process entirely.

Admittedly I'm very green when it comes to all the lingo (rooted/unrooted, etc) so I'm afraid I'll make things worse by attempting to fix this myself unless I can find a specific solution to my problem.

Any of the threads that have been recommended won't let me post until I have 10 posts but I'll get there eventually.

Thanks.
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
Where would I go about getting it? How would I get it onto the phone seeing that it is s-on and doesn't seem to get picked up by adb? What about the rest of the files it is complaining are missing or wrong image?
[G2 and Desire Z Q&A, Help & Troubleshooting] ptesmoke:
it should flash a proper pc10img, just pull your sdcard, pop it in a pc and copy the pc10img to the root and pop it back in. someone with a little more knowledge would have to point you towards the right pc10img tho. not my expertise there..
[G2 and Desire Z Q&A, Help & Troubleshooting] PaganAng3l:
You're stock on bell canada right? What version of android did you have before the brick?
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
Honestly, I don't know. It was stock as I have never tried to replace it but I believe there was a previous update of 2.2 sometime between when I bought it and when this latest update came down on Friday.
[G2 and Desire Z Q&A, Help & Troubleshooting] Athrun88:
probably was the 1.34 version then, i don't recall bell ever pushing the 1.82(?) version of 2.2. i don't recall the exact version of 1.34 though =(
[G2 and Desire Z Q&A, Help & Troubleshooting] PaganAng3l:
I'm having trouble finding a full bell canada ruu, I know I'm just not looking in the right place. Everything you've described can be fixed by reflashing the software.... if only you had s-off and supercid this would be a cakewalk
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
Thanks for the effort. I'm such a newb that I'm really not much help.

Rots me that this happened. I've never messed with the phone so far as I'm concerned the update they pushed out should have worked flawlessly as it appears to have for many many other people.

I had to have my phone in for service to get the screen replaced back in December (that was my own fault). I wonder if they had to do anything with the software at that time that made it incompatible with this latest update.
[G2 and Desire Z Q&A, Help & Troubleshooting] David Dee:
Bell pushed out a Froyo update on March 30. Here is the thread: http://xdaforums.com/showthread.php?t=1145163&highlight=bell

Could this be the solution?
[G2 and Desire Z Q&A, Help & Troubleshooting] David Dee:
I purchased my DZ the day it was launched by bell and it had 666.5 so I am assuming that is the version Bagadonitz has.
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
I got the phone a couple days after the bell launch and I've installed everything that came down since.

I'm real nervous about trying anything here unless I can get specific instructions. I'm a technical person but haven't done anything with phones before and I'm a little reluctant to jump in on my own :(
[G2 and Desire Z Q&A, Help & Troubleshooting] David Dee:
It should be quite simple: Place the OTA on your SD card and launch it through the phone's bootloader. You enter bootloader by shutting down the phone, holding the volume down and power button at the same time. If you have "fast boot" enabled, then you have to do a battery pull and then turn on with the volume down.

I would wait for PaganAng3l to confirm that the OTA (that is associated with the thread I posted above) would work with s on and a non-rooted phone.
[G2 and Desire Z Q&A, Help & Troubleshooting] David Dee:
About "bootloader", here is an excerpt from gtrab's DZ easy rooting guide, located here http://xdaforums.com/showthread.php?t=835777:

1.- What is "Bootloader" ??

The Bootloader is a firmware management tool included on every stock ROM, it lets you reset to factory default, use "Fastboot" to flash official images, or launch the Recovery utility.

From the Bootloader you can also check your S-ON or S-OFF state, your firmware and Radio version, etc.

You don't need root or S-OFF to enter the Bootloader because every HTC phone has it.

2.- How do I enter the Bootloader ??

Power off your phone, then, hold the volume down key and the power key.

(You need to disable "Fast boot" from Settings -> Applications, or remove the battery to really power off the Desire Z. Otherwise, power off will just hybernate the phone, and when restarting you will not be able to enter the Bootloader).

To exit Bootloader you have to remove the battery.
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
Ok I've been in the "bootloader" which is where I was able to get the information I got in the first couple of posts in this thread.

Some reading I did in another thread linked to in this one indicated if the phone was not rooted and was s-on, then there wasn't much I could do that would be on the simple side.

If it is as simple as putting files on the SD card and going through the bootloader to boot them then I'll take that chance. I gather however there is some issue with knowing exactly which files should be put on there since it is not really known what was on there before this issue?

I'll repost this info here to make it easier to reference. Does this make it any easier to figure out exactly which files I might need?

Briefly comes up when I go into the bootloader initially:

SD Checking…

Loading…[PC10DIAG.zip]

No image!

Loading…[PC10DIAG.nbh]

No image or wrong image!

Loading…[PC10IMG.zip]

No image!

Loading…[PC10IMG.nbh]

No image or wrong image!

Info from the main bootloader screen:

Vision PVT SHIP S-ON

HBOOT-0.05.0009

MICROP-0425

RADIO-26.06.02.25_M2

eMMC-boot

Dec 13, 2010,14:30:18
[G2 and Desire Z Q&A, Help & Troubleshooting] David Dee:
Your radio version above is the one that was released with the OTA I have referenced above, here is the link: http://xdaforums.com/showthread.php?t=1145163&highlight=bell. You must have had version 1.84.666.2.

S On is basically a security that stops you from installing "unauthorized" roms. My understanding is if you install an "authorized" Rom by installing an RUU, S on / rooting should not matter.

Where I am not so sure is how to install the RUU onto your phone (I have done all mine through rom manager as I am s-off/rooted). Also, ensuring the RUU and OTA in the link above are the same. I think HTC Sync may do this. Anyone?
[G2 and Desire Z Q&A, Help & Troubleshooting] PaganAng3l:
Try downloading the .zip from the thread the post above me references, the download you need is the first link in the first post on page one. Once done rename it update.zip and put it on the root of your sdcard. Boot into your bootloader then select recovery and hopefully an option to apply update.zip will come up, select that. If it works it will begin the process of flashing your radio, hboot, system... but I'm skeptical that it will allow it to install. Anyway give this a go while I look for a bell canada official 2.3.3 ruu
[G2 and Desire Z Q&A, Help & Troubleshooting] whistlerGreg:
My phone is also now in paper-weight mode! Not sure what happened, but now I have a red warning icon on my screen. Any suggestions before I have the pleasure of calling up Bell?
[G2 and Desire Z Q&A, Help & Troubleshooting] whistlerGreg:
Any way to access the SD card from bootloader? I don't have a micro SD card reader
[G2 and Desire Z Q&A, Help & Troubleshooting] PaganAng3l:
No there isn't. Sorry
[G2 and Desire Z Q&A, Help & Troubleshooting] David Dee:
Interesting, same procedure as pc10img for radio. Please post experience either way.
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
Born loser. I have one SD card reader in this house. On the side of a Dell 2407 monitor. Guess which monitor Dell didn't bother releasing Windows 7 Drivers for.

<sigh/>
[G2 and Desire Z Q&A, Help & Troubleshooting] nooge9:
Have you tried the RUU from this thread?

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

A while ago (probably in January?) I had to send in my unit back in (phone calls were garbled) after rooting, getting S-OFF etc. This restored it to stock without a hitch for me.
[G2 and Desire Z Q&A, Help & Troubleshooting] nooge9:
Sounds like you're in stock recovery mode. Press and hold VOLUME-UP, then press POWER. You'll get a menu -- navigate using the volume rocker and select using the power button. There should be an option to restore factory settings.
[G2 and Desire Z Q&A, Help & Troubleshooting] David Dee:
Post removed.
[G2 and Desire Z Q&A, Help & Troubleshooting] PaganAng3l:
That sucks hard man. If you're anywhere near Toronto I have a friend who could help. Be warned she's mean, lol.
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
Nope, I'm in NL.

I'll pick up a card reader while I'm in the city tomorrow and give the suggestions here a shot.
[G2 and Desire Z Q&A, Help & Troubleshooting] PaganAng3l:
I found the .exe RUU!!!!!! Go here: http://shipped-roms.com/index.php?category=android&model=Vision

Download the 9th one from the bottom, it says BellMobility somewhere in the long title. Once downloaded plug your phone into your cpu, boot into your bootloader and run the .exe from your computer, and assuming you have the correct drivers on your computer it should take over and get it done... i think. I've never done it this way but it can't hurt! Try it and post back, no need to put anything on your sd!
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
Downloading now....
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
The phone is connected to the cable is connected to the PC. Check.

The phone is in the bootloader and HBOOT USB PLUG is displayed on the screen.

There is no sign of anything having been connected by USB however. Nothing shows up under computer in terms of removable devices.

I tried to run it again with the phone sitting on the white hTC splash screen where it gets stuck and got a different error telling my the battery is too low for the utility to run. I will try and charge it for a while if my phone will do so (if my phone won't I'll pop it in my wife's phone and give it a shot).

I'll update when I have something new to report.

Thanks for the effort.
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
One last thing....

Not to doubt but are you sure this RUU_Vision_BellMobility_WWE_1.34.666.1_Radio_12.28b.60.140e_26.03.02.18_M2_release_154437_signed.exe is for this phone?

The radio that is currently on the phone appears to be 26.06.02.25_M2.

The radio that seems to be listed in that file name is 26.03.02.18_M2.

Not that this means anything to me.

From this thread I read that this new update has the following radio:

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

12.57.60.25U_26.10.04.12M

So confused.
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
Now that the battery is a little bit healthier I get the following screen when running RUU_Vision_BellMobility_WWE_1.34.666.1_Radio_12.28 b.60.140e_26.03.02.18_M2_release_154437_signed.exe with the phone stuck on the HTC splash screen:

In your learned opinions, is it safe to click Update?
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
I went ahead and tried it and it failed.

ERROR [155~159]: IMAGE ERROR

One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
[G2 and Desire Z Q&A, Help & Troubleshooting] PaganAng3l:
Ah, I see. Is your Desire Z branded to bell? I mean did you buy it from them or off ebay or something? Also, I believe our problem is that this ruu is older than the version your phone had, in which case it will abort installation

Edit: Sorry for the long response time, I'm at work presently. I'm pounding pavement looking for a newer ruu, and it's always gonna be safe to try updating whenever possible because worst case we'd get stuck at the white htc screen, lol
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
Yes, bought from bell, never rooted or modified in any way.
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
Tomorrow I'll try getting "OTA_Vision_BellMobility_WWE_1_84_666_2-1_34_666_5_release_172473wagbpno61mgwg4k0.zip" renamed as "update.zip" onto the sd card and use the recovery in bootloader and see if that works as was suggested earlier.

http://xdaforums.com/showpost.php?p=16456257&postcount=23
[G2 and Desire Z Q&A, Help & Troubleshooting] PaganAng3l:
Well promise me you'll get s-off and root next time :-p, we'd have had you running ages ago if you did. Anyway we need an ruu with a higher version than 1.84 to make this work
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
That other thread has the following warning:

Warning! DO NOT flash it unless you are running official Bell 1.34.666.5 rom.

This radio HAS NOT been tested on other Desire Z/G2 versions.

Since I'm on some dead version of 1.84.666.2 it is probably not a good idea for me to even attempt this?
[G2 and Desire Z Q&A, Help & Troubleshooting] PaganAng3l:
Nah, you'd be fine. It's just warning people that the .zip checks your version and won't install on any other which hoses us.....
[G2 and Desire Z Q&A, Help & Troubleshooting] David Dee:
As per my earlier post, repeated below, based on your radio, you were on 1.84 before trying to install the gingerbread update. The do not flash warning is with respect to the installation of 1.84, a recent bell froyo upgrade which you had done. I believe you need to get your hands on an RUU from 1.84. The 666.1 RUU you tried to flash was a pre-release version but I have not come across any bell dz users that have ever had that, all had 666.5 prior to the 1.84 update. Hopefully someone will find the correct RUU for you but I would advise you to get your replacement phone and when your phone is repaired, root & s-off so this doesn't happen again.
[G2 and Desire Z Q&A, Help & Troubleshooting] PaganAng3l:
Yeah I can't find a 1.84 ruu, or ideally the gingerbread ruu. Hit google up and search for "desire Z ruu", or I can when I leave work tomorrow morning

Edit: is a replacement from Bell out of the question? When my ribbon cable broke tmo had me a new phone at my door the next day complete with a box to mail my defect back in
[G2 and Desire Z Q&A, Help & Troubleshooting] whistlerGreg:
Can you use ADB to install the rom? I've got it sitting on my PC good to go but don't have a card reader for a mini sd...
[G2 and Desire Z Q&A, Help & Troubleshooting] ptesmoke:
fyi the bell gb ruu is out, ill try to link if u still need it
[G2 and Desire Z Q&A, Help & Troubleshooting] whistlerGreg:
I tried this method - no luck :-(
[G2 and Desire Z Q&A, Help & Troubleshooting] jaetelha:
Please do post it somewhere, I'd like a copy. If it's the full RUU (an .exe), you might try and get it uploaded to Shipped ROMs (http://shipped-roms.com/upload.php)
[G2 and Desire Z Q&A, Help & Troubleshooting] bagadonitz:
Yes, please upload it somewhere.

A replacement from Bell is on the way along with shipping materials to send my phone in. They have to charge $45 a month for a replacement while mine is in for "repair" but have agreed to credit my account $50 for two months as the repair time is an estimated 6-8 weeks.

I'm just hoping to resolve the issue on my own in the mean time and avoid all the hassle.

I'm not glad to see other people have the same issue but at the same time it is validates that I didn't mess something up. Far as I'm concerned I should be able to walk into any bell store and get this replaced with a new phone when this sort of crap happens.
[G2 and Desire Z Q&A, Help & Troubleshooting] TelusHTCHero:
I'd love to have a copy of the Gingerbread RUU for the Bell DZ. My father has been asking me to get his phone unlocked, and I've not been wanting to do that until there's a decent Bell RUU available to put on his phone. I'm aware of 1.34.666.1, but that just seems like a testing ROM as there's no upgrade from it to any newer versions...
[G2 and Desire Z Q&A, Help & Troubleshooting] Merzennary:
bump for ruu update.
[G2 and Desire Z Q&A, Help & Troubleshooting] mhonmun:
I have the same problem.. failed after the system files update :(
[G2 and Desire Z Q&A, Help & Troubleshooting] dotzev:
I have the very same problem After updating some apps through the market app, my phone started freesing and after a few tries of removing the battery it got stuck in the logo screen. I haven't tried to root it or anything at all, it's completely stock rom-wise and as far as I'm conserned it will stay that way. I can move arround in the menu when pressing down volume key and power key combo, but when I try to resstore, it just vibrates 7 times after it goes into the black screen with the green arrows, and if I try to hard reset it, it just freeses and I have to remove the battery again...

I really am hoping for someone who can help to answer this post. I've posted this in another simillar thread for maximum coverege, hpoe it's not against the rules. Also my version is:

VISION PVT SHIP S-ON

HBOOT-0.85.0013

MICROP-0425

RADIO-26.10.04.03_M

eMMC-boot

Apr 11 2011, 23:36:27
[G2 and Desire Z Q&A, Help & Troubleshooting] 'cooleagle':
Thread moved to the Q & A section.
[Android Software/Hacking General [Developers Only]] nunosilva10:
hey guys, do you know some apk that allows me to see anonym calls number ?
[HTC EVO 3D] Morkai Almandragon:
Does it work on the Evo 3D?
[HTC EVO 3D] Morkai Almandragon:
Can someone download it from the market and give it a try? Please?
[Motorola Droid X2] KurioHonoo:
Both the Droid X and Droid 2 are locked down, but both can be overclocked, why is that?

Sent from my DROID X2
[Motorola Droid X2] magneticzero:
Requires a custom kernel
[Motorola Droid X2] slowz3r:
which requires an unlocked bootloader
[Motorola Droid X2] mistawolfe:
As far as I know, neither the X or D2 have an unlocked bootloader or kernel access...

Sent from your Mom's house using Tapatalk
[Motorola Droid X2] KurioHonoo:
Exactly, yet both can be overclocked

Sent from my DROID X2
[Motorola Droid X2] mistawolfe:
I love the default answer people give to this question. Both are as locked down as this phone.

Sent from your Mom's house using Tapatalk
[Motorola Droid X2] kdaz:
Not sure, has moto released their source code? Without source from moto it is damn near impossible to make a custom kernel (at least the way i understand it). No custom kernel means no overclocking. Also it seems development on this phone has been pretty limited to newcomers. Once we start getting more experience support, things should take off. Nitro just released his first x2 rom and ThatDudeButch is working on his rom...these two guys alone are great resources but also with Butch we also get TeamBamf support and they can really make things happen. Not to mention, we all saw what p3droid was able to do in about a day. So to sum this all up..I guess we just have to be patient and hope more developers jump on board.
[Motorola Droid X2] juhde:
The droid 2 and the droid x can be overclocked because they actually made dev versions of those phones that were unlocked, which afforded a developer a peak under the hood so a kernel module could be written. With root that module can be installed on the locked kernel and over clock abilities are accessible. The X2 had no developer version, no way to write the proper module. Soooooo we're screwed until Moto and Big Red decide to give us the keys to our own phones.

Sent from OH MY GOD IS THAT A SQUIRREL!
[Motorola Droid X2] TheMavic:
Disappointing to say the least. I have been happy with my rooted GB X2 so far but I still feel so... limited with it. A change to a different brand is surely resurfacing again in my head. Been drooling over the DINC2 for a while now but have been holding strong for the X2 waiting for some kind of miracle soon.
[Motorola Droid X2] zetsumeikuro:
I'd love to see a 1.4-1.5 ghz OC on this bad boy along with AOSP GB D:.
[Motorola Droid X2] mistawolfe:
This is the kind of answer we needed, although it isn't a happy one.

Sent from your Mom's house using Tapatalk
[Motorola Droid X2] EvilTim:
Damn you for making sense and crushing all our dreams, jerk <3
[Motorola Droid X2] juhde:
*pops a vicodin*

Blame motorola for not making a x2 dev phone, but mostly for encrypting the bootloader keys so well. If we could just get Geohot interested he'd probably have the keys faster than a junkie diving into the pool for a crack rock.

Sent from OH MY GOD IS THAT A SQUIRREL!
[Motorola Droid X2] EvilTim:
Make sure he knows its not made by Sony. and no its a rabbit, I think it lives under the doghouse
[HTC EVO 3D] xSpAzzZAttAcK:
Hi.. I cannot seem to root my evo 3d. I have rooted it before, but since i havent gotten completely rid off it, and i have s-on again. I did this for a personal problem. But now.. revolutionary will not root my phone. It just says "This device is not supported." Im not sure why this happens, because I used it before. Any help?

And when I type adb devices in a command prompt, it shows my device. So im pretty sure its not because of my drivers.
[HTC EVO 3D] iamthespoon:
what version is your hboot? It's my understanding that Revolutionary uses the hboot version to decide whether or not to work. If your hboot version is 1.xx.1000 instead of 1.xx.0000, then it will not work.
[HTC EVO 3D] -Torres-:
i don't mean to thread jack, but i'm having the same sort of problem with my sensation. going to copy a post from another thread to here:

i hope i'm not SOL. or maybe i'll just have to wait for the HTC update
[HTC EVO 3D] xSpAzzZAttAcK:
i figured it out.. i dont have s-on :P
[HTC EVO 3D] -Torres-:
mind posting what you did? or PMing me? i swear it started to work, now all of a sudden says it won't work. i think i'm just overlooking something
[HTC EVO 3D] -Torres-:
ah wait i think i took your post wrong. phone was already S-OFF? damn haha
[Desire Q&A, Help & Troubleshooting] kuljit55:
APP To Move Internal APP To System?

i understand this can be done manually by adding the apk to system but oxygen 2.2.2 does not let me do this (no paste option in system folder with astro.

titanium always crashes on my oxygen 2.2.1 when converting to system app

any ideas?
[Desire Q&A, Help & Troubleshooting] davebugyi:
Try Root Explorer.

But remember, that you have to be S-OFF, otherwise it won't work.

(or you can try the ADB in recovery way, if you are S-ON).
[Desire Q&A, Help & Troubleshooting] k3lcior:
I already told you earlier... Move apk's before flashing to the ROM .zip file or use titanium backup pro (you cannot do it with free version)
[Fascinate Q&A, Help & Troubleshooting] Kingali1997:
im thinking about adding speakers on the back of my fascinate, kind of like the ones they do for my psp. any advice, tips or anything useful you could give me.

if all goes well ill post an in def tut.
[Fascinate Q&A, Help & Troubleshooting] ghostv7142:
Why? and Where ? i would think making a cover that attaches to rear of the phone that plugs in to the 3.5 mm jack would be better ,so you can use the 5.1 ch surround sound thing ..