So, I've been trying to fix this for what seems to be months now. OK I flashed to a ROM and bricked my phone. (Don't remember what ROM it was.) Then after a while, I flashed to another ROM while my phone was bricked, and it worked, however with no mobile data, only WIFI. Then I got the mobile data to work, and my WIFI just stopped working. Everytime I toggle WIFI, it says Error in the bottom of WIFI. I need help please!
[HTC-PG762]
I think your definition of bricked might be wrong. The most widely used definition of bricked is when you do something to the phone that stops it from turning on completely, hence the "brick".
What ROM did you flash? The Wi-Fi error you're experiencing is almost certainly caused by a fault in the ROM, not your phone.
Also, there's a Q&A section, post other questions there please
Like I said before I don't remember what ROM it was but I "think" it was a Buzz ROM not a Marvel ROM. And sorry bout the misuse of the word brick xD I mean that my phone wouldn't get past the HTC logo. I could only go to CWM recovery. I'm a noob at this, but I have a weird vibe that my WIFI "files?" are missing from my phone. And do I just copy and paste this thread to the Q&A section?
Geez, I'm so unlucky with all this flashing. I tried to flash to CM 7.2 for WFS to see if that might work... I'm back to square one, I'm stuck at the HTC boot logo again!!!! I tried to restore one of my backups, however it says MD5 sum mismatch or somthing like that.
FINALLY FIXED IT! It's all in this thread: http://forum.xda-developers.com/showthread.php?t=1531932
It restored my WIFI and works perfectly!
Related
Hi after days of searching the internet I have finally realised I need to post here and ask for help, sorry if this has been posted before though as I have really looked hard everywhere!
Anyway, after flashing a RCMix rom my desire started to drop calls as soon as I either picked up or answered one and only ever rarely got 2G signal in what I know is H signal zones. I changed roms but the problem persisted and after countless hours of searching and trying my sim in other phones, I have deducted that it is my desire which is the problem.
So I'm going to take it back to a t-mobile store, as I were unrooting using the RUU exe I got the 140 error, my phone will no longer boot but still has bootloader, fastboot and recovery working! Is my phone bricked, I can't find any help anywhere on how to put my desire back to stock
Please could any of you shine some light onto my situation?
Many many thanks
You have recovery? Did you try installing another rom to make the phone work again?
After that you can try to unroot it again, I think...
Okay, I will try installing a froyo rom now, will post the results of a second unroot...
Right very strange indeed, just flashed AceSMod007 and signal problems have seem to have gone away (although I had tried this before with many roms - maybe the unrooting process fixed my phone somehow?)... so this means there is no need to unroot and send back to t-mobile, hmmmm all seems to good to be true! thanks for the help though, wouldn't of tried flashing another rom if you hadnt mentioned it
Hi,
Im really hoping someone can help me here.
Yesterday my phone threw a wobbly and started to loop boot to the htc logo, it had happened before but i payed little attention. When i removed the battery to reset it i found that it had corrupted my whole sd card, stange file names etc was everywhere.
i decided it was time for a clean start and super wiped the lot then installed arhd,
everything went fine until i went to use bluetooth, nothing i say or do will enable it.
Ive since have wiped and flashed leedroid, arhd, and runny but cant get this little but one of the most used features on my phone to activate.
Ive also reflashed the radio, does it sound like a hard ware failure to you guys?
is there anything that i could have missed, i would also like to add that i havent re installed any previous apps etc and bluetooth still fails to activate.
thanks
sorry to reply to my own thread, but i think i just worked it out. After reading my own post i though about the sd card, i decided to remove the card and reboot, voilia!! the bluetooth is now functioning!!, totally confused now as to why an sd card can affect the running of a seperate piece of hardware!!
ok, it happened again a few time since i posted this thread.
it happened again yesterday and no matter what i done it wouldnt come back.
So i decided to do a nandroid backup and wipe, install a new rom then recover my nandroid backup.
this solved the problem, im not sure what is causing the bluetooth to just die like it does but now i have to keep another rom on my card and a nandroid back up just to get the bluetooth to work- seems strange as the backup is the same drivers etc and stops working. must be hardware...
this dosnt seem to be rom specific as well as its happened now on leedroid, runny, 3dmix, and anotherone i forget the name.
roll on htc edge as im pretty sure i may have a impending hardware failure on the bluetooth radio
Hey guys!
So. This is the first time I've been stumped enough to actually post, so I can't post to the actual ROM thread. I hope someone sees this and will help me.
Currently, I've succeeded (after many redos and restores) in getting AceSMod007 v41 onto my CDMA HTC Desire (BravoC). Fought with the patch for a while but it's functional. In case it's a needed tidbit, my radio is 0.93 CM7.
The problems I'm running into aren't the ones I'm seeing most people run into. I'm not having a problem with the lock screen or bootloops. My WiFi is acting up since I loaded the rom. It refuses to even turn on. It just says "Error" under the WiFi checkbox. At one point I found a "wifi_fix.zip" in the development forum from an earlier version, but when I flashed that for some reason my phone refused to go past the HTC loading screen so I had to restore.
The bigger problem I'm having is that I absolutely cannot update my APNs. On CM7 all I had to do was flash my "cellularsouth-mms.zip" and then restore default in APNs. That doesnt work. So, I tried to manually save a new APN with the appropriate information and it refuses to save the APN settings.
Other than that I'm running great though!
No one at all?
First of all, my English is not that good, so I hope everybody understand me
I'm a flashoholic (i think this is the right expression); i flash a new ROM almost every two weeks. And, from some days ago to now i'm experiencing some problems. Here's my problem:
Problem: my phone "stucks" when I let it locked for more than some 5, 10 seconds. I lock it now, and... dead. I have to press the power button until it restarts. My phone is having trouble to find operator's network and it's EXTREMELY lagged too. It almost stucks when i try to write something on the keyboard, or draw/write my passwords on my lockscreen.
Here's my "ROM timeline", too:
ROM Timeline: MIUIBrazil v4 [4.1.2] >> P.A.C MILESTONE [4.2.2] >> TigraROM/Hurricane [4.3 leaked] >> MIUIAndroid v4 [4.1.2] >> MIUIBrazil v4 [4.1.2]
Underline = i think that this is the point
Bold = problem started
So, let me explain my history: flashing ROM's as always, I decided to change things a bit and go AOSP for a while. So I flashed P.A.C. Milestone. Actually, I've flashed first the Nightly version, but it was a bit unstable. I went to P.A.C and everything went fine. But, hey, where are the Samsung functionality? I missed it. So, after some trouble finding the right ROM to me, the 4.3 from Samsung leaked. I tried it, then. First the Hurricane, afterwards the TigraROM (Note 3 functions ). And it was ok, but was lagging a lot. Too much launchscreen redraws to handle, so I went back to MIUI (not the first MIUI on the timeline, because I've decided to go right from scratch), and then, i've noticed a lot of problems.
It was not booting up.
I've flashed A LOT of ROM's trying to solve this problem. What it was? EFS folder. I went to the TWRP file manager on Recovery and noticed that the EFS folder was empty. And no backup. I went crazy until i found an old backup stored on my PC. Restored it right away, and everything was fine for a while... until it started doing some strange things like extreme lag and dead when locked.
And, when I went to recovery to look again to the EFS folder, it was always empty... i restored it again, again and after locked... BAM, disappeared. But some strange things are happening, like:
My bluetooth doesn't turn on.
My IMEI was fine, even with this EFS showing and hiding like that.
I'm almost finishing. Let me put here some basic questions that I know everyone will ask:
Q: have you tried to wipe everything and go from zero?
A: yep. It didn't worked.
Q: is your IMEI ok?
A: yep. But some things that are on the EFS folder doesn't wok, like Bluetooth. The MAC address of the bluetooth is there, but it doesn't show up when I write *#*#232337#*# on my Phone app (this code shows up Bluetooth address and try to turn it on... to me it tries to turn on forever).
Q: do you know that thing about the new modems? Click here to go to the post
A: yes, but only read it when i've had the problem. But i've restore that backup, and it was from the original ROM. So it doesn't seem to be this, because the backup was before this leak. Very very very before, actually.
I hope you guys can help me, and that I don't need to go to the Samsung support with the phone wiped. Thanks,
~imatheussm
When you say you've tried from zero, do you mean you've flashed a stock rom?
Sent from my GT-N7105 using xda app-developers app
3vo3d said:
When you say you've tried from zero, do you mean you've flashed a stock rom?
Click to expand...
Click to collapse
When I had this problem, the second/third thing I did was flashing the stock ROM. But it was with these problems too, and with some other weird things: the S Note and the Samsung Keyboard giving FC almost every second.
~imatheussm
Well I guess if you're getting these issues when completely on stock I reckon you need the service centre?
Sent from my GT-N7105 using xda app-developers app
Have you try formatting your internal sd? I got similar problem too when flashing 4.3 mj5 leak.
Also got a uid mismatch when the phone start. I format my internal sd then flashing 4.1.2 firmware back.
Not a problem after that.
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)