Develop Bugs

Official HTC 2.2 upgrade failed.

Hello everyone!
I've got an issue with HTC OTA 2.2 upgrade.
My Desire is unbranded but was still running latest HTC 2.1 OTA.
On my scheduled upgrade check new version was discovered so I went for upgrade. Everything seams to went fine. The ROM file was downloaded, installation went fine until device booted for the first time. After reboot I've had spinning wheel and progress in %. Device was rebooting about 20 times as soon as it reached 93-97%. During that process I've received error message: system service error: FC or Wait. Finally after about an hour the system decided to start eventually but it was loading for about 10 minutes. Now system reboots randomly every 5-10 minutes. No network connections available, no bluetooth, no SD card access and still the same error message: Process system is not responding, FC or Wait. What I suppose to do now? Please for step by step guide as I'm quite a newbie.

I see your desire was running 2.1 OTA but was it rooted...??

No it wasn't. Well to be absolutelly honest it was rooted to install custom 2.2 ROM then unrooted to install HTC OTA 2.1. During the update the phone wasn't rooted. To make it even more odd I've tried to install RADIO rom but recovery-windows script is unable to connect to device. And last thing 3G internet is working fine but can't make any calls!

ortonnorth said:
Hello everyone!
I've got an issue with HTC OTA 2.2 upgrade.
My Desire is unbranded but was still running latest HTC 2.1 OTA.
On my scheduled upgrade check new version was discovered so I went for upgrade. Everything seams to went fine. The ROM file was downloaded, installation went fine until device booted for the first time. After reboot I've had spinning wheel and progress in %. Device was rebooting about 20 times as soon as it reached 93-97%. During that process I've received error message: system service error: FC or Wait. Finally after about an hour the system decided to start eventually but it was loading for about 10 minutes. Now system reboots randomly every 5-10 minutes. No network connections available, no bluetooth, no SD card access and still the same error message: Process system is not responding, FC or Wait. What I suppose to do now? Please for step by step guide as I'm quite a newbie.
Click to expand...
Click to collapse
Have u tried a factory reset ?..
poweroff phone
hold volume down and press power
clear data ?

Yeap. I've done that. Still no luck at all.
I've also renamed downloaded ROM to update.zip and run recovery but the phone still acts the same.
I think that it's because I'm still running update not a new installation.
Is it possible to use this ROM to perform full brand new installation?

U need a goldcard and then use an ruu to downgrade ur phone
Sent from my HTC Desire using XDA App

philicibine said:
U need a goldcard and then use an ruu to downgrade ur phone
Click to expand...
Click to collapse
I'm just about to finish 2.1 OTA ROM download. So you reckon that the upgrade should be possible afterwards?

It might....
But I used a base WWE ruu.
Hope it does work for u... keep trying if not!
Sent from my HTC Desire using XDA App

Ok, back to 2.1 again. Everything seems to work absolutelly fine. Flashing 2.2 again.

Root first and then flash a rooted ota froyo
Glad I could help!
Sent from my HTC Desire using XDA App

Update successful. Hell knows what was wrong. But to anyone who'll meet similar problem the solution is to install fresh 2.1 ROM and then upgrade it.
Thanks for all your help!

Worked for me too guys, thanks!
Looks like I'll be going to work in the morning now I have an alarm clock again..

[Q] Problem with ROM HD Revolution NO SENSE

Hi,
I flashed the ROM to my Desire HD and the ROM boot correctly. If I want to restart the phone I got the message that I will loose all temp files.
After I restored all my applications and data with titanium bake up I rebooted phone. After phone booted I got the message of an unexpected interruption of the process android acore and can't do nothing else than restore to my previous ROM.
Obviously my phone is rooted with radio S-off, I followed the procedure for flash the ROM as shown on the instruction but I don't really know why I got that error message.
Any help?
Thanks

[Q] Black screen cyanogenmod

Hi there!
After almost 2 days from my holydays trying to install cianogen beta3 in my defy I lost almost all my hopes. Than I made my last call, I tried a version older, and GOTCHA! I have cyanogen working.
So the problem is, if i try installing beta3, all that I get is a black ugly screen after moto logo.
And with a test version before beta3 cyanogem works like a charm.
I already tried with the nordic, korean and uk roms, and tried too patching pays rom 3 and 5.
Also i got some weird error with SuperOneClick2.1 than i used SuperOneClick 1.65
Also, again, i tried to update beta3 from the test with and without wipe, and no luck.
Any sugestions to me to get the beta3 working?

I'm guessing you have, because you got an earlier release working, but are you doing the 2nd INIT boot with the boot menu thingo? cuz thats why i copped a black screen when trying to get it to work

I suppose he already has 2ndinit working considering he has it working before though?

Thanks for the answers. Yeah i needed the second init thing to make the test build work. The only strange thing that i see is a error message that sometimes i got whenever i install beta 3 saying that xbin/su dont exist. when i got this message i try install it again and says that it was completed. But when i install the test build i never get this message.

[Q] CM11 snapshot/nightly stuck at boot... now can not even rollback to 10.2

Hi,
I had CM 10.2 running fine on my HOX. A couple of weeks ago I decided to test out CM11, since this is not my primary device, stability wasn't that big of a concern for me. The first few tries CM11 installation was a failure with some error (I can't recall) occurring when installing the zip in Recovery (if i remember correctly it had something to do with version of recovery I was using).
Anyways, I searched online, found a solution and was able to install the CM11. I have flashed the boot, erased the cache, tried wiping/factory resetting the device, in all kinds of orders (wiping/installing/flashing boot.img, flasing boot.img/installing CM11, etc). but no matter what I try my phone always stays stuck at the boot animation.
I found multiple threads on the forums with similar problems, but in most cases the OP was either missing flashing boot.img or erasing the cache helped. not so in my case.
Also, weirdly enough, now even if i try to reinstall CM 10.2 (which was working earlier), I get the same issue.
any further guidance on troubleshooting / overcoming this issue is highly appreciate
HOX International H__J15
HBOOT 1.31
CWM Touch Recovery 6.0.4.8
(btw, just tried Beanstalk ROM, same issue... I dont know what I F'd up on this phone!! )

nabeelmoeen said:
Hi,
I had CM 10.2 running fine on my HOX. A couple of weeks ago I decided to test out CM11, since this is not my primary device, stability wasn't that big of a concern for me. The first few tries CM11 installation was a failure with some error (I can't recall) occurring when installing the zip in Recovery (if i remember correctly it had something to do with version of recovery I was using).
Anyways, I searched online, found a solution and was able to install the CM11. I have flashed the boot, erased the cache, tried wiping/factory resetting the device, in all kinds of orders (wiping/installing/flashing boot.img, flasing boot.img/installing CM11, etc). but no matter what I try my phone always stays stuck at the boot animation.
I found multiple threads on the forums with similar problems, but in most cases the OP was either missing flashing boot.img or erasing the cache helped. not so in my case.
Also, weirdly enough, now even if i try to reinstall CM 10.2 (which was working earlier), I get the same issue.
any further guidance on troubleshooting / overcoming this issue is highly appreciate
HOX International H__J15
HBOOT 1.31
CWM Touch Recovery 6.0.4.8
(btw, just tried Beanstalk ROM, same issue... I dont know what I F'd up on this phone!! )
Click to expand...
Click to collapse
Your HBOOT is to low you must to upgrade ti 1.39 or 1.72 but 1.31 is tooo low and for this the CM11 don't boot

Actually I think 1.31 is the latest version which came out with jelly bean rom for the htc__15 id.
what's frustrating is that I can't even get the 10.2 version of CM working again either...which should be fine with this hboot version

nabeelmoeen said:
Actually I think 1.31 is the latest version which came out with jelly bean rom for the htc__15 id.
what's frustrating is that I can't even get the 10.2 version of CM working again either...which should be fine with this hboot version
Click to expand...
Click to collapse
try restore stock and chek for update restore nandroid and see I am not sure J15 is only 1.31

Will give it a shot tonight and report back. ...what's grinding my gears is none of the other roms including jb ones I tried are working either

i finally managed to resolve my issue. I tried changing recoveries, tried multiple ROMs and also tried to run RUU (which failed since i have a later version of the ROM vs. what's available in RUU).
finally decided to try formatting the boot, System and Cache partitions and installing CM11 again.
I had never used the 'format <partition>' feature before. Apparently this did the trick and now i am running CM11 .!!

nabeelmoeen said:
i finally managed to resolve my issue. I tried changing recoveries, tried multiple ROMs and also tried to run RUU (which failed since i have a later version of the ROM vs. what's available in RUU).
finally decided to try formatting the boot, System and Cache partitions and installing CM11 again.
I had never used the 'format <partition>' feature before. Apparently this did the trick and now i am running CM11 .!!
Click to expand...
Click to collapse
is HBOOT still the same version or did you upgrade it?

I am curious about the order in which you did things. After formatting boot, system and cache partitions, did you flash the boot image again or did you do that prior to the formatting.
Thanks

[Q][Xperia M Dual][C2004][CM13]Can't get network in CM 13[ROMs][STABLE]

I started with unlocking bootloader using minimal ABD and fastboot. Once done my device went into bootloop.Then I download the stock frimware from sony's software called xperifirm which said that it is 15.5.A.1.5 but was 15.5.A.0.18.And wanted me to update using my laptop. tried doing that to but every time a error 12 came up.then i found someone's thread with .ftf file for 15.5.A.1.5 that to generic_IN. flashed it and then booted into it,got network working.then updated to CM13 and still it says sim card not detected.then flashed the same ftf file checked for software update and this is what i got:
Settings>about phone>bulid number:15.5.A.1.5
Update center>system::15.5.A.1.5 Ready to download 104.4MB
still downloaded it and tried to install.but,while installition when phone goes into recvery mode the screen stared blinking and the installition failed .then flashed cwm recovery and tried again but this is what comes up:
CWM-based Recovery v6.0.4.9
E:invalid command argument
Finding update package. . .
Opening update package. . .
Verifying update package. . .
E:footer is wrong
E:signature verification failed
Install Untrusted Package?
THIS CAN NOT BE UNDONE
- Yes - Install untrusted zip
E:Can't open /cache/recovery/fota/update_package(bad)
Installation aborted.
Rebooting. . .
Note:bold text is recovery log
pls someone help me out I want cm 13 with network working (only one sim working is ok for me but two will be better)

just the same problem
Hi,
I came here looking for a solution to this same problem. I have a C2004, and I have to admit I didn't really know what I was doing, but at this point I'm sure I've followed the right steps at least once. I only followed the official wiki.
I
- unlocked the bootloader
- flashed CM13
- booted, no GApps
- installed GApps (phone unusable due to popups)
- Re-flashed CM13 and GApps before first boot, phone works beautifully but I did all my tests without the SIM, when I rebooted to insert the SIM I noticed the phone was not detecting it. Eventually I found a post detailing what the problem was: CM13 required a previous Android 4.3, but my phone was on an older version.
So I downloaded the radio firmware and the image of the stock Sony OS on 4.3:
- wiped all data
- flashed radio firmware
- restored OS backup with CWM
- booted: SIM card is detected, no idea whether dual sim works because I'm not interested on it, GPS doesn't work
- wiped all data
- flashed CM13 again, still no network.
I repeated the above process several times, always get a working stock OS (except for GPS) but never got CM13 to connect to the mobile network. So, right now I'm stuck on that Sony OS, because it even detects an OS upgrade but can't install it because CWM doesn't know how to handle the upgrade package.
I'd like to know if it is possible to get a copy of the original recovery partition, so that official upgrade can be installed.
Or, better, to get CM13 working, somehow it seems my issue is not common because everything I find on the web points to the same above steps...

After installing CM13 , Did u flash the dual sim patch?
Steps :
First install a custom recovery,
then wipe/format everything
install cm13,dual sim patch and gapps(if u need) in one go because after that your recovery will be replaced by the cyanogenmod recovery and you will have to reinstall another recovery.

I don't know where, but I read that was not needed anymore, and that idea was fixed in my head. Maybe I mixed comments about the dual patch with comments about the radio patch, I can't recall at this point.
Anyway, patching that additional zip fixed the network access for me. Let's just see if its get fixed for the OP as well
Thanks!

You need to flash a patch for enabling dual sim, without it you will get no network ... This is because the official cyanogenmod gives no support for the xperia m dual and so an extra patch has to be flashed before you can really access the sim card's network! hope this helps ! so go on flash the cm13 and then the patch and share the results!!