Develop Bugs

Desire - Network Locked - Desperately need help :(

Hey all,
I've recently debranded my HTC Desire (Orange) with the generic HTC Rom, everything was working perfectly but then an OTA update arrived and was consequently installed, since then, the phone boots but says "Network Locked". From what I've read this is due to the 4.06 Radio update and the 2 solutions seem to be either downgrade the radio or request the unlock code.
Phone has Goldcard and has been rooted.
Radio Downgrade
Well I attempted this by downloading the generic radio 4.05, copying to MicroSD and renaming to update.zip and selecting the "Apply sdcard:update.zip" option on boot. This was tried MANY times and always stated the following
E:Can't open /cache/recovery/command
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
Reload Generic ROM
Have tried this, but get a "Bootloader Version Error" when installation is in progress.
BRAVO PVT1 SHIP S-ON
HBOOT-0.80.0000
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-4.06.00.02_2
I have requested an unlock code, but the 2 companies I have tried are having trouble getting a code based on my IMEI. I've verified the IMEI from the sticker under the battery as cannot get past the network locked message to enter *#06#.
Any ideas?
Desperately needing help here guys, need my expensive paperweight working as a phone again.
Neil

if you are rooted, just copy the radio to your sd card and flash it in your chosen recovery. There is no need to rename it.
A radio flash will reboot your phone twice and takes a few minutes. Do not interrupt it or pull the battery.

+1 previous post...
Simple terms...
Copy the file from this thread:
http://android.modaco.com/content/h...unching-recovery-on-your-device-without-a-pc/
Onto your SDCard, rename it to update.zip.
Also, copy the RadioUpdate.zip to SDCard (do not rename this to update.zip)
Now, boot into recovery (as you were) and select Apply update.zip as you were...
You will now be greeted with another menu.
Choose "Select File from SDCard to Flash" (or similar, I can't 100% remember and my Desire is currently in bits), and then choose RadioUpdate.zip
Reboot the phone
It should work

help
Hi
Sorry don't mean to hijack the tread but wonder if any body can help, I purchased a sim free desire from O2 UK before my contract expired, to use with my new 3UK contract.
I have routed and phone and updated the radio from stock to the following 32.37.00.32U_4.06.00.16_2.
Now phone displays Network locked. I have tried downgrading to the following radios without success :
32.36.00.28U_4.06.00.02_2
32.34.00.28U_4.05.00.30_2
32.30.00.28U_4.05.00.11
32.26.00.24U_4.04.00.03_2
if i am trying the wong radios, please can some one refer me to the correct radio?
Phone details:
BRAVO PVT1 SHIP S-ON
H-BOOT-0.80.0000
TOUCH PANEL SYNT0101
RADIO-4.05.00.30_2

can you not install the stock 3UK rom again with its radio?

tried to install the stock O2 RUU Rom but get error 140?
all networks were open before rooting.

It's Working!!!
Well, I put my sim into another phone as nobody could txt or call me, then booted Desire again out of curiousity, now it fully boots and although it complained that there was no sim inserted, it did allow me access to the menu's etc....
Whilst it was in this state, I tried to flash the Generic ROM again, and to my amazement, it worked! Radio and ROM are now back to how there this morning! Re-inserted sim, job done! Very weird how it worked in this mode, but nothing else.
I have also disabled the OTA updates until I can get the phone unlocked.
Finally, I did try to flash the radio back via the update.zip + recovery method, but this just resulted in the same problem.
Thank you all for your feedback on this, think I'm gonna leave it as is for the moment
Neil

Neilc28 said:
Well, I put my sim into another phone as nobody could txt or call me, then booted Desire again out of curiousity, now it fully boots and although it complained that there was no sim inserted, it did allow me access to the menu's etc....
Whilst it was in this state, I tried to flash the Generic ROM again, and to my amazement, it worked! Radio and ROM are now back to how there this morning! Re-inserted sim, job done! Very weird how it worked in this mode, but nothing else.
I have also disabled the OTA updates until I can get the phone unlocked.
Finally, I did try to flash the radio back via the update.zip + recovery method, but this just resulted in the same problem.
Thank you all for your feedback on this, think I'm gonna leave it as is for the moment
Neil
Click to expand...
Click to collapse
The radio is already in a zip format so just rename it to update and not update.zip n flash it.
It's not even necessary to rename it.

it was actually called update<version number>.zip , so all i did was remove the version number. I didn't call it update.zip.zip due to hiddent extensions lol
I did also try giving it no extension at all, but that didn't help either.
In any case, it's working now

Well done! this should be added to the rom guide. Recon this could help a few people.
Sent from my HTC Desire using XDA App

GREAT JOB.
Please ad to the tutorial / guide sticky

Wait: So this means that i can Unlock my Network-Lock flashing a new Radio????

If you flash your Desire with the Official HTC 2.2 update, then it will no longer be locked-out in any case due to the new radio not being locked by Orange. This is now an easy fix, unlike before

Stuck in boot loop and can't boot into clockworkmod recovery

Hey,
As the title says I am stuck in a boot loop and can't access clockworkmod recovery (only stock recovery). I can't do a restore from backup or flash a new ROM because I can't get to clockwork.
The solution I found is to run the RUU from fastboot. I have an HTC Desire from SK Telecom in Korea.
For some reason the SKT RUU linked in the Desire RUU thread does not work.
I tried a different site but the file is the exact same and doesn't work.
It tells me that the USB is not connected properly (Error 170). But when I try and run a different RUU it successfully connects to my device and starts the process but then of course fails and gives an error because the RUU and the device don't match (Error 140).
If you download the SKT RUU you will notice the update utility number is xx.xx.xx.
If someone could point me to a working SK Telecom RUU that would be great.
Also if there is a different solution to my problem that would be great also.
Any help would be greatly appreciated!

Create a goldcard and try to flash again:
http://www.nazriawang.com/2010/04/how-to-create-goldcard-with-ubuntu.html
No warranty for any damage.

Wildfire S digitizer and GoldCard

Hello!
I've changed digitizer but now it doesn't react on any touch. I tried to make GoldCard, but I can't enter to menu to change connection to debug mode. There is any other solution to make the GoldCard?
Thx for help.

haller said:
Hello!
I've changed digitizer but now it doesn't react on any touch. I tried to make GoldCard, but I can't enter to menu to change connection to debug mode. There is any other solution to make the GoldCard?
Thx for help.
Click to expand...
Click to collapse
Hi, did you solve the problem? I have the exact same problem.
If you have, please let me know how.

jocke888 said:
Hi, did you solve the problem? I have the exact same problem.
If you have, please let me know how.
Click to expand...
Click to collapse
I have had the same problem with the screen and the debugging, I did however find a kind of workaround for the debugging issue.
I searched for hours and hours for posts on how to enable debugging via ADB command line. The bottom line is that you can't. When I say you I mean "us plebs" can't. I have read the arguments about security and I say cool fair enough. I also noticed that when you run the RUU with the phone connected via USB the RUU activates "USB Debugging" on the handset irrespective of if it was enabled via the handset menu. I can understand this is done for obvious reasons as the RUU is supposed to be an easy way for end users to update their ROM's. It does however beg the question of how a stock ROM can alter the USB debugging switch on the phone via software/usb interface and the rest of the internet claims it is not possible via ADB/command line. Anyone who seems to ask about it is immediately suspected of being a phone thief and the forum responses become a mud slinging match.
So I did some experimenting with the HTC Wildfire S:
Basically I ran the RUU and left it on the Readme page running in the background I could then access the handset via ADB. I don't know ADB well but I was able to see the device listed using adb devices where as before I got nothing. When in Fastboot mode I saw that the handset was also receiving data via the Console on the PC using the fastboot reboot type commands.
It didn't really help me too much as all I wanted to do was update the stock ROM to see if it resolved my touchscreen issue. Unfortunately it didn't. So I'm still stuck with a fully functional handset minus the touchscreen.
I then decided to try and unlock the bootloader so that I could try with a custom ROM. Following the process on HTCdev I got a "Radio" update for the handset. At first I couldn't load it because the base ROM was too old. I found the latest update. It failed with a USB connection error. I found an older version about halfway back between what I had (X.1.33.X) and the new (X.2.16.X) this was (X.1.66.X). It worked but the "Radio" update still needed the latest version. I re-ran the latest RUU and it failed with the same error.
Determined to get it done here is what I did:
1. Re-Ran the (X.2.16.X) Installer
2. At Readme screen I navigated to the standard %TEMP% directory (it helps if u empty this first then you will see the dir the install creates easily)
3. I copied the entire contents to a folder on my desktop
4. Closed the (X.2.16.X) Installer and re-ran the (X.1.66.X) Installer
5. At the Readme screen I navigated back to the %TEMP% directory (it helps if u empty this first then you will see the dir the install creates easily)
6. I pasted and replaced all the files back. Now you get a lot of failures because the Intaller is runnning so I just skipped those files.
7. Went back to the installer running in the background and completed the process.
I used the older installer to flash the newer ROM. I have no idea which files (apart from the rom.zip) were critical but if you copy only the rom.zip it fails on the device when checking the security certificates.
After that I successfully flashed the "Radio" update. The next step in the HTCdev process is to get a device ID via a Flashboot command. I still couldn't do this because the touchscreen still wasn't working after the update. So I Re-Ran the (X.1.66.X) Installer and left it in the background. The phone went into debug mode and I could run the command. I got the info and completed the process with HTCdev. This gave me a unique file to unlock the boot loader.
I then used the same method to get into debug mode and used the HTC Wildfire S All-In-One Toolkit (http://forum.xda-developers.com/showthread.php?t=1809751) to unlock the bootloader with the file HTC sent me.
I now have an HTC Wildfire S with the latest stock ROM, Bootloader unlocked and still no working touchscreen. This took me the better part of 10 hours. When I have the energy to continue I'll try a installing Root and custom ROM.
I apologise in advance for the RUU version number above being severely shortened but they have so many versions of the RUU depending on where you are and who your provider is and such, you will need to do your own research on the specific RUU's you will need and where to get them. The method to get debug I have illustrated should not change if you use a different version of RUU. If you're lucky your stock ROM is also updated and you can skip that part or the RUU you do download works without the tweaking l had to do.

jocke888 said:
Hi, did you solve the problem? I have the exact same problem.
If you have, please let me know how.
Click to expand...
Click to collapse
You have to install a custom recovery (CMW). If you enter recovery mode you can choose mounts and storage, and then mount USB storage. This way you enable usb mass storage. now you are able to get your CID

[Q] HELP!!!!

Hello to All!
I'm new to the site and I hope that one of the local genius' can help me out.
I'm having a problem on my Original HTC Evo 4G - Getting the message: "SORRY. The application HTC Sense (proccess com.htc.launcher) has stopped unexpectedly",
In a constant loop.
History - I terminated my sprint service about two years ago. While with Sprint, I rooted my phone and it worked fine in the rooted condition. After leaving Sprint, the phone sat unused until now.
A few weeks ago I decided to renew service with Straight Talk. We had problems getting the servers to recognize my phone. After several failed attempts, we did a hard reset going back to the factory settings. That's when the launcher problems started (not sure if the phone tried to do an OTA upgrade during this process).
I started getting the message, "the application HTC Sense(process com.htc.launcher) has stopped unexpectedly. Please try again." Touching the "Force Close" button does nothing, just an endless loop. Also occasionally get "Sorry, com.android.phone has stopped working.
I have tried the following to no avail:- Taking the battery out - anywhere from 10 minutes to 2 hours - and after removing the battery holding the power button down for 10 or so seconds.
wipe data/factory settings
Wiping the Cache
Wiping the Dalvik cache
BASIC FACTS:
The phone is still rooted.
When I press the PWR AND VOLUME DOWN buttons I get the following on a WHITE SCREEN:
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.82.0000
MICROP-041f
TOUCH PANEL - ATMELC03_16ac
RADIO - 2.15.00.09.01
OCT 14 2010,19:14:47
HBOOT USB PLUG
<VOLUME UP> to previous item
<VOLUME DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
SIMLOCK
HBOOT USB
1. I think that there is a software problem causing the HTC Sense app to loop - FORCE RESTART DOES NOTHING.
2. There is a USB driver/connection problem that is causing the phone not to be seen by the Windows 7 DEVICE MANAGER - No Android in OTHER DEVICES.
3. I can't get into the applications screen
4. The phone is not responding (SORRY - process com.android.phone is not responding).
I went to the HTC site which was useless.
When I hooked the phone to my computer and started HTC Sync it said "No Device Connected".
None of this has stopped the com.htc.launcher looping at startup.
Cannot access the Home, Phone, search keys. I had read that by accessing search during the loop, one could then access HTC Sense and wipe that cache to fix the problem.
What I'd like to do is get access to the phone and add a new Launcher.
Are the any tools that will allow me to access the phone?
Does anyone have specific suggestions knowing that the phone is in a constant loop cycle and that there is no access to any of the keys.
I'm not taking a "shoot at anything that moves" solution to the problem and would sincerely appreciate any thoughts as to what a good approach might be. Thanks in advance for any helpful suggestions.
D

I didn't see any mention of it, but have you tried flashing another ROM? If not, I suggest flashing the one in the link below. Download, put the file on your SD card, boot into recovery and do a full system wipe. Flash the ROM, then reboot.
http://forum.xda-developers.com/showthread.php?t=1671395
Sent from my EVO LTE

Hi, well seeing how your rooted, u should have no problem flashing a stock Rom from recovery,
First when you hold volume down and power and you get into the bootloader use the volume keys to choose recovery, hit power button, does the phone boot to a custom recovery like clockwork or smelkus .
If so good.
Then just put your sd card in a micro sd card reader adapter and use it in your pc, then just put a stock Rom zip file on it,
Put your sd card back in the phone and boot in to bootloader again choose recovery, in recovery wipe everything except sd card, and system. Then choose install zip from sd card and u should be good.
If you don't have recovery then you need to put one on the root of your sd card and boot into bootloader again and choose yes when it ask to update. Then go back to what I said.
Do a search for recovery zip files I would use smelks
---------- Post added at 08:35 PM ---------- Previous post was at 08:27 PM ----------
Also do a search for HTC drivers for windows, 7 should be able to find them easy, that way u can just use adb and just try to push HTC launcher to system/app and do adb reboot that can solve your launcher problem, providing its stock Rom on your phone, if not just flash stock rom

I finally eliminated the [email protected]#$ing loop - i'm in!!!!!!!!
FinZ28 said:
I didn't see any mention of it, but have you tried flashing another ROM? If not, I suggest flashing the one in the link below. Download, put the file on your SD card, boot into recovery and do a full system wipe. Flash the ROM, then reboot.
http://forum.xda-developers.com/showthread.php?t=1671395
Sent from my EVO LTE
Click to expand...
Click to collapse
FINZ28, Thanks for the response. You brought up the point that I was going to attack next. Again, Thanks. I'll have a question in a minute. I solved my problem as follows:
As I suspected, the problem was software/OS related
I believe that the problem started when StraightTalk tech support had me do a hard reset and wipe the SD card
This wiped the file PC36DIAG.ZIP AND ALL OF THE ASSOCIATED FILES installed during extraction when I initially rooted
I think that dependencies between the rooted system and the HTC apps were broken at this point which caused the looping and the USB/driver issues
I feel like a DUMMY for not seeing this much earlier, but when I went into HBOOT and saw
Loading PC36DIAG.zip
No Image
Loading PC36DIAG.nhh
No Image or Wrong Image
Loading PC36DIAG.zip
No Image
Loading PC36DIAG.nhh
No Image or Wrong Image​during the booting process, I should have know that these files were missing, but the above was only on the screen for a very short time and the print is microscopic.
I found the EVO 4G PC36img.zip file
I rebooted and selected the DISC FILE option
I was then able to see the SD card from my PC, and I copied the zip file to my SD card
I rebooted to HBOOT and chose the RECOVERY option.
I CHOSE "INSTALL ZIP FROM SD CARD"
Next I chose "CHOOSE ZIP FROM SD CARD"
I then selected "EVO 4G pc36IMG.ZIP" AND THE INSTALLATION PROCEEDED
I then chose the REBOOT SYSTEM option and my screen came up as it should
​I now have access to all of my apps and settings
I want to bring tthe phone firmware up to date and I read elsewhere on the site that I should not accept OTA's or RUU's from Sprint lest I lose rooting capability FOREVER!
What the best course of action for me now? Should I flash the ROM you're recommending? Is there a newer ROM? What do you recommend as a replacement for HTC Sense?
Again, thanks for responding.

Flash the ROM I linked you to. It's a stock rooted ROM based off the latest OTA from Sprint. As far as the info regarding the text output in HBOOT, that's normal and shouldn't be confused with an error unless you actually are trying to install a PC36IMG.zip file on your phone (like you would when installing a recovery or updating firmware).
If you're interested in updating your firmware, check out the thread in the link below:
http://themikmik.com/showthread.php?8477-Radio-Update-2-15-00-01-15-2-16-13
Sent from my EVO LTE

Thanks
FinZ28 said:
Flash the ROM I linked you to. It's a stock rooted ROM based off the latest OTA from Sprint. As far as the info regarding the text output in HBOOT, that's normal and shouldn't be confused with an error unless you actually are trying to install a PC36IMG.zip file on your phone (like you would when installing a recovery or updating firmware).
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks Fin. I'll do it.
Any thoughts on a replacement for HTC Sense?

dmking99 said:
Thanks Fin. I'll do it.
Any thoughts on a replacement for HTC Sense?
Click to expand...
Click to collapse
You can go the AOSP route
Keep in mind that Sense is a user interface (UI). You can download a replacement launcher like ADW or Launcher Pro, but this really only replaces your home screen and Sense is still there. With AOSP (for example, CyanogenMod) you get the pure Android experience without things like HTC Sense getting in the way.
Sent from my EVO LTE

No Longer Have SU Capability
FinZ28 said:
I didn't see any mention of it, but have you tried flashing another ROM? If not, I suggest flashing the one in the link below. Download, put the file on your SD card, boot into recovery and do a full system wipe. Flash the ROM, then reboot.
http://forum.xda-developers.com/showthread.php?t=1671395
Sent from my EVO LTE
Click to expand...
Click to collapse
I flashed the recommended ROM. When I checked the Root status, it looks like I have lost SU capability and so it looks like NOW I'm "partially rooted" (BOOTLOADER - Supersonic EVT3 SHIP S-OFF)
Did System Wipe and reflashed back to the UnrEVOked3 ROM. Ran the following apps and still do not have SU capability.
ROOTCHECKER: "Sorry Device does not have proper root access"
SUPERUSER: SU Binary not found
Titanium Backup: Root Access Failed
In the Terminal Emulator: Cursor is $ and not #.
Any Ideas as to how to get SU capability back?
Can't run ADB because Device Manager does not see the device Via the USB cable.
TIA

Got it Working
dmking99 said:
I flashed the recommended ROM. When I checked the Root status, it looks like I have lost SU capability and so it looks like NOW I'm "partially rooted" (BOOTLOADER - Supersonic EVT3 SHIP S-OFF)
Did System Wipe and reflashed back to the UnrEVOked3 ROM. Ran the following apps and still do not have SU capability.
ROOTCHECKER: "Sorry Device does not have proper root access"
SUPERUSER: SU Binary not found
Titanium Backup: Root Access Failed
In the Terminal Emulator: Cursor is $ and not #.
Any Ideas as to how to get SU capability back?
Can't run ADB because Device Manager does not see the device Via the USB cable.
TIA
Click to expand...
Click to collapse
Looks like everything works now - Rooted, SU status OK, Radio updated, ROM Updated...
I am confused as to why Device Manager shows "Android Phone -->Android Composite ADB Interface" When I updated the driver with the Android USB Driver.
Also, my BOOTLOADER shows HBOOT - 2.02.0000. If I wanted to get a more recent bootloader, wwhere do i get it and how do i update it? Is this necessary or am I OK as is?
TIA

You're fine with the bootloader you have. No need to upgrade it. Also, regarding your previous post regarding having "partial root". There is no such thing. S-off and root are not dependant upon one another. You either have root access or you don't.
Sent from my EVO LTE

Everything Works Perfectly
FinZ28 said:
You're fine with the bootloader you have. No need to upgrade it. Also, regarding your previous post regarding having "partial root". There is no such thing. S-off and root are not dependant upon one another. You either have root access or you don't.
Sent from my EVO LTE
Click to expand...
Click to collapse
Fin,
My sincere thanks for all or you time and help. The phone works perfectly.
I'm planning on getting a Nexus or Galaxy and a tablet in the fall and wanted to practice getting the device to do what I want, so this was a valuable exercise.
The Evo is practically brand new, but it's dated and I don't know how much longer it'll be getting support. It's a great phone and I like it a lot so, I'll keep it as a backup.
I'm pretty easy on my equipment so I expect it to last a long time. As I said, it's like new.
Once again many, many thanks.
Dennis

Glad to be of help:thumbup:
Sent from my EVO LTE

posible brick, cannot pass google account check after firmware update

Hi.
International version, Europe, S-off, Unlocked.
I think that I managed to write a wrong firmware on a stock, but rooted rom (im not shure if this is the cause, i followed the instructions and the log was ok). The result is that if I flash a rom (with TWRP), no matter which (L or MM), the phone boots, the initial setup starts, language selection ok, wireless connection functional, but when i reach the google account checking, even the email and password are ok, it continuously throw me back to the google email checking...
The situation now is like this:
- can enter TWRP, fully functional
- can enter download mode
- can enter bootloader mode.
The problem is that the phone is recognized by the computer only when in TWRP, no connection on download/bootloader. So I cannot use adb to push commands. When in TWRP i can put anything on internal or external storage and flash...
Please, help me with some advice in order to fix this.
Thank you.

Dont bother. Found the lollipop oficial ruu zip, flashed from the external card in download mode, system fully operational in 5.1 now.

Its an odd one to say the least. I had a similar issue when rooting my phone last night. After installing twrp I couldn't speak the phone for love nor money.
Tried a sideload in twrp and it told me that my adb.exe was too old for my phone so I updated it and then I had adb control at least.
Changed my twrp from newer to older and then everything seemed ok.
Sent from my HTC One M9 using Tapatalk