Develop Bugs

[Q] Weird problem installing custom ROMs

I've rooted my phone for the first time the other day and started venturing into the custom ROM's realm, but so far all I got were dramas and failures.
I started by downloading Cyanogen 6.1.1 and 7 RC1. I thought I'll try each to see how they perform. So I copied them to the sd-card, along with the radio update that was recommended on the Cyanogen 7 RC1 thread, and rebooted to Clockswork recovery. I wiped my data and cache and went on with the ROM installation followed by the radio update (notice that I skipped the backup stage. stupid, I know).
Upon booting, I immediately noticed that I have no signal, and a force close message that says: "the process com.android.phone has stopped unexpectedly. Please try again" pops up every 2 seconds. Nothing happens when the message is dismissed, mind you, but it still comes up constantly every couple of seconds. This, along with the 'no signal' thing, rendered the phone unusable.
At this point I'm thinking that maybe my phone is just not reacting well to the non-final build of the Cyanogen 7, so I gave the stable Cyanogen 6.1.1 a go. Lo and behold, same thing happens with it also. Now panic kicks in when I realize that I have no backup, and no stock ROM to go back to.
Eventually, I downloaded the latest rooted Desire 2.2 ROM, got it into my sd-card and installed it. Thankfully, everything was working properly again. After some asking around in the Cyanogen forum, it got to my attention that the update to the radio might have caused all of this trouble, and that the installation of the stock ROM brought the previous radio version with it, which solved the problem. But when I tried to install Cyanogen again, without tinkering with the radio, same thing happened. I then tried Oxygen 2, thinking that maybe my device just doesn't like Cyanogen, but the exact same problem persisted.
Anyone have any idea what's the deal here?

Did you wipe dalvik cache after flashing the roms?
Sent from my HTC Desire using Tapatalk

I wiped the cache partition before I flashed. It didn't say 'dalvik' specificaly, just 'cache partition'. I never wiped any type of cache *after* the flashing process.

You should wipe the dalvik cache after (or just before) flashing roms.
You can find it under the advanced menu in clockworkmod recovery.
Sent from my HTC Desire using Tapatalk

Alright, tried wiping the Dalvik Cache after flashing, problem still persists.

You could try downloading another radio and trying it. Even if it's not the recommended one, an older radio works better for some people. There is no such thing as 'the best radio to use', since result may have large variations for different people (in different locations, using different phones and ROMs). Just browse the radios post and pick one
Btw, since the dalvik cache is stored at /data/dalvik-cache, wiping the /data partition implies deleting the dalvik cache

Well, since the radio that I have installed now works, and since it stays the same one after installing a different ROM, it seems to me that the radio is not the problem here. I really would like to stay away from tinkering with the radio stuff...

Bump.
This really bugs me that it wont work. I feel like I'm missing out on the biggest feature of having a rooted phone...

Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?

If all else fails you could always trying flashing the RUU for your phone then start from the beginning and root again if you've tried everything else.
Sent from my HTC Desire using XDA App

Ok, I'll try that.
Just a quick question. After I run the RUU and the device is unrooted, will I be able to recover my nandroid backup fully after I re-root?

[Q] LeeDroid HD V3.0.3 GB crash after install

Having trouble with the latest LeeDroid HD ROM have flashed many LeeDroid roms before without issue but for some reason aftering clearing all caches and running the latest rom it will install ok but on reboot it just hangs on the White HTC screen and won't boot in.
Any Ideas what could be causing it?
Currently Running LeeDroid HD v3.0.1, LeeDroid Kernel v3.1.1 radio 12.54.60.25_26.09.04.11_M2

Make sure you're deleting all data do a full factory reset (deletes all data does not actually restore to factory condition) then clear the dalvik cache, re apply the ROM make sure its CLEAN and you haven't modified it, don't apply any themes or anything, then let it boot and be patient.
Try downloading it again also it could be a corrupt download.

m3t4lh34d said:
Having trouble with the latest LeeDroid HD ROM have flashed many LeeDroid roms before without issue but for some reason aftering clearing all caches and running the latest rom it will install ok but on reboot it just hangs on the White HTC screen and won't boot in.
Any Ideas what could be causing it?
Currently Running LeeDroid HD v3.0.1, LeeDroid Kernel v3.1.1 radio 12.54.60.25_26.09.04.11_M2
Click to expand...
Click to collapse
I had similar issue few days back. But i had the Leedroid rom (same rom,kernel as urs) already runing flawlessly for a few days. It decided just to hangs at the same HTC Screen... tried to clear caches(all), hard reset, reflash same rom... still stuck same place. I finally had to flash stock 1.32 image, root all over again, etc. ... and flash Leedroid (same) again... works fine now
I got the feeling that I made my friends with their stock DHD and Iphone users drooling and jealous of my phone(csutomised with sense 3.0 stuffs), and they collectively jinxed my phone, and had this crash! lolz
btw. i flashed SAME rom i had on my sdcard, so I think the rom fine(mine at least). just something triggered that crash!
all the best...

Yea i tried reflashing from stock rom the other day loaded up one of the RUU exe's and rerooted etc and tried to reflash with no luck so i'm all out of ideas

raidenxl said:
Make sure you're deleting all data do a full factory reset (deletes all data does not actually restore to factory condition) then clear the dalvik cache, re apply the ROM make sure its CLEAN and you haven't modified it, don't apply any themes or anything, then let it boot and be patient.
Try downloading it again also it could be a corrupt download.
Click to expand...
Click to collapse
Have also done factory reset and cleared dalvik cache etc. no joy

Just managed to find a copy of LeeDroid HD V3.0.2 have installed and found it also crashes but.... it gets to the LeeDroid Android screen, little further but unfortunately still crashes

Managed to get 3.0.3 working on my DHD turns out it was just down the cwm version i had, updated to 3.0.2.5 and boom worked first time =D only problem i have had with both 3.0.1 and 3.0.3 is the camera keeps dropping out, app doesn't force close but the screen keeps going black and all buttons dissapear then all comes back... =( Atleast i'm up to date though
Any Idea's on the Cam issue?

have run logcat and noticed the following in the log
W/mm-camera( 1400): config_proc_CAMERA_STOP_SNAPSHOT: state is not correct ctrl->state = 25 W/mm-camera( 1400): VFE_RESET_ACK illegal ctrl->state 24
dunno if that makes any sense to anyone

tinkered with it a little last night didn't seem to make a difference so left it over night and for some odd reason works fine this morning i think the issue was down the camera app itself but it looks to be working fine now thankfully
UPDATE:
Ok looks like the issue is still there found out what is causing it thought, the camera works fine but...only when wifi is off, if you turn wifi back on you get the same issue as before,
Please anyone got an idea on wtf?
UPDATE2: have worked out it must be the camera app due to the fact i download a different app which appeared to work fine. Not sure why there's a glitch though

[Q] 3g data issues

i have tried following the instructions on another thread i found here about trying to fix a 3g issue with the incredible and new roms, but i have not been able to get my 3g back. currently i am running a stock ruu. my system info reads s follows...
Android ver
2.2
baseband ver
2.15.00.07.28
Kernel ver
2.6.32.15-gb7b01d1
htc-kernel @and18-2 #1
build number
3.21.605.1 CL231334 release-keys
software number
3.21.05.1
ClockworkMod Recovery v2.5.1.2
i have rooted again since i ruu'd and have more or less just lived with it while trying to figure it out on my own. it seems to be random sometimes i will be able to look stuff up other times not so much. i know it isn't my service area as i have a work blackberry on verizon and that is fine. does anyone think this could be a software issue or does this sound like hardware. i am really hoping it is software as i have had my incredible since launch and really don't want to get it replaced, lol. i appreciate any help you guys can give me.
could it be the radio i have flashed? i dont know a whole lot about them so i havnt done a whole lot of troubleshooting there. can i go backwards with radio flashing? i just want to be sure before i try that as to not brick.

Does your 3g disappear or drop down to 1x often? You say you tried another thread, could you link me to it so I know what you did OR could you explain what steps you have done to alleviate this?
The typical solution is to flash a stock rom then boot into the rom itself and leave it running for a minute or two, even make a call and check 3g to make sure it's working. Then restore your backup rom and enjoy life. I'll provide you a stock rom link with steps to follow in a few minutes.

found it. i followed this thread and reverted back to stock. still hasn't helped my 3g woes. could having the wrong radio cause these problems?
http://forum.xda-developers.com/showthread.php?t=817487&highlight=3g+fix
***Edit i generally don't even have the 3G symbol in my notification bar or if it is there like now it just wont connect sometimes. in settings it says mobile network is connected as well

undeclared said:
found it. i followed this thread and reverted back to stock. still hasn't helped my 3g woes. could having the wrong radio cause these problems?
http://forum.xda-developers.com/showthread.php?t=817487&highlight=3g+fix
***Edit i generally don't even have the 3G symbol in my notification bar or if it is there like now it just wont connect sometimes. in settings it says mobile network is connected as well
Click to expand...
Click to collapse
Aight, the rom link in my instructions is this one from RMK40. His link has since gone down. It is the first leaked OTA from last May prior to the flood of gingersense roms.
1. Boot into recovery and perform a Nandroid
2. In recovery, do a Factory reset/Wipe Cache/Wipe Dalvik Cache
3. Flash this
4. Boot into the rom and make a test call. Also check your 3g connection and see if it works. You can run it for ten minutes or an hour if you want to see if the connection fails, although it shouldn't.
5. Reboot into recovery and do Nandroid restore
6. Enjoy.
Post back with your results.
Edit: Here is a reference thread from where I obtained my instructions. I believe you are in the same scenario.
http://forum.xda-developers.com/showthread.php?t=1229732

i did a back up, wiped and flashed the rom, twice, both times i got boot loops :-/
maybe it's my radio?

undeclared said:
i did a back up, wiped and flashed the rom, twice, both times i got boot loops :-/
maybe it's my radio?
Click to expand...
Click to collapse
I would flash the froyo ruu thru hboot and then reboot. Then go back to hboot and select factory data reset, or boot to the os and go to Menu Settings Sd & phone storage and select factory data reset. Let it do its thing and then reboot. Once it boots up do the ota programing and your 3g should be fixed. Then you can flash cwm recovery thru hboot, and the su binary thru recovery and you will be rooted and ready to flash roms again. I have had this happen several times when using sense 3/3.5 roms ported from sprint phones.
Also that radio is old, from froyo, but that shouldt be the issue. If a factory reset dosent fix it i guess it wouldnt hurt to try updating to the newest radio. Im 95% positive factory reseting the phone from hboot or the settingd menu will fix your 3g. You have to have the stock recovery for the reset to work, that is why you need to ruu again, unless you are already on the stock recovery.

thanks i think this is working i just got done with programming and now i have 3g! gonna stress test it till later tonight i think and then it is off to flashing a new rom! any rom either of you suggest that shouldn't give me these 3g issues?
again thanks so much for your help

undeclared said:
thanks i think this is working i just got done with programming and now i have 3g! gonna stress test it till later tonight i think and then it is off to flashing a new rom! any rom either of you suggest that shouldn't give me these 3g issues?
again thanks so much for your help
Click to expand...
Click to collapse
It usually happens to me on roms ported from sprint phones, mostly after doing a *228. I would highly advise not to do a *228 on a sprint rom. If you want to be extra cautious i wold just stay away from sprint ported roms all together.

[Q] Problem that needs fixing!!

I have been searching throughout this forum and across many other websites to no avail before asking this.
For the last month, WiFi and Bluetooth has not been working on my Desire HD, and no matter what I do I cannot get them to work again - I have tried factory resets, many different roms, restoring my first nandroid backup (just after the phone had been rooted, still stock rom), replacing the bcm4329.ko driver with a couple of others, but no joy.
My logcat reports:
Code:
E/rmt_storage( 3308): rmt_storage wait even ioctl failed
I/WiFiHw ( 1465): wifi_load_driver end error 2
E/WiFiService( 1465): Failed to load Wi-Fi driver.
I desperately need help with this, it is becoming incredibly frustrating as I used to use WiFi a large amount on a daily basis - any help would be extremely useful!!

what rom are you currently running? have you done a full cache/dalvik/full wipe before installing and make sure u restore nothing before testing? what radio are you running? a corrupted radio img file is possible
also, what did you do RIGHT before you lost your wifi?

Darunion said:
what rom are you currently running? have you done a full cache/dalvik/full wipe before installing and make sure u restore nothing before testing? what radio are you running? a corrupted radio img file is possible
also, what did you do RIGHT before you lost your wifi?
Click to expand...
Click to collapse
I am currently on Android Revolution HD 7.0.3, but just before that I was on Playground ICS and before that SmartDroid, and the problem has occurred on all of them.
I haven't been restoring any backups at all, I always do a full wipe before installing a new rom and I have tried cache and dalvik cache wipes as well.
Currently the radio I am using is 12.62.60.27U_26.13.04.19_M but I have tried a couple! Do you have any suggestions of any particular radios, or anything else worth trying?
Thanks for the assistance!

sam_w said:
I am currently on Android Revolution HD 7.0.3, but just before that I was on Playground ICS and before that SmartDroid, and the problem has occurred on all of them.
I haven't been restoring any backups at all, I always do a full wipe before installing a new rom and I have tried cache and dalvik cache wipes as well.
Currently the radio I am using is 12.62.60.27U_26.13.04.19_M but I have tried a couple! Do you have any suggestions of any particular radios, or anything else worth trying?
Thanks for the assistance!
Click to expand...
Click to collapse
im at work currently so forgive my quick typed replies. Dumb idea, turn off your phone, remove the sd card and then boot up without it. Ive seen cases where the sd card has caused connectivity issues.
the radio i use is 12.56.60.25U_26.10.04.03_M
been using it a long time, not the greatest d/l speeds, but most reliable (yes we all know its case by case basis for radios)
other thing i would try, is check all you antenna connections. each door functions as an antenna for a different device on the desirehd.
if it is repeating this same error across the board, it becomes more possible its hardware.

Hmm, this is very bizarre:
Clearing the cache and dalvik cache seems to make the WiFi work for a while (it lasted for about 3 or 4 hours yesterday), but after a while it will go back to saying "WiFi error".
I have tried formatting my memory card, but it still goes back to not working again, so I am going to see what happens when I leave the card out entirely and then report back on my findings.
Thank you for all the suggestions, I just really want my WiFi working again permanently!

[Q] Can't turn wifi on. Tried with 5.1 and 4.4.4

I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..

stevenx37 said:
I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..
Click to expand...
Click to collapse
Hope you had read the posts, it should had said the Rom is not "stable"
If your friend are going use their phone for daily driver, then I recommend you not have the 5.1 Roms for now because it's not really suitable for that right now.....
I'm not sure the CM11 you have flashed is unoffical or is offical. Offical onces are still work in progress and have most of the things broke (I think)
Here is a Kitkat Rom for SGH-T989
If your friend really wanted to have a Lollipop running on his/her phone, then I will recommend this one. Make sure you read the instruction CAREFULLY if you do wanted to install this one since it's a bit complicated with it's "virtual partition"
Or, if you wanted it to be just stock. Odin it back to normal, here is a instruction (with video too).
This is all the possible way to fix your friend's phone that I can think of, if you have encounter any error or have anymore question, feel free to reply :fingers-crossed::good::highfive:
P.S: yes, wiping dalvik & cache is a way to prevent any error caused by another old Rom if you decided to flash a new one. It's a good way to prevent error during Rom flash process

Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.

stevenx37 said:
Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.
Click to expand...
Click to collapse
For the virtual partition, it's best for you to have it on the External SD card. Since TWRP transporting file to Internal Storage after that seems bugged (not working)