Hello,
I recently encountered a problem whereby my wifi stopped working altogether. Did a lot of research on it and it seems the problem seems to happen across a lot of different devices for a variety of reasons and there is no one fix.
Tried to factory reset a couple of times, nothing worked. HTC suggested I send my phone back to Germany where it originated. I live in China, and do not want to do that...
The option that seemed to work for other people was to root and flash a custom recovery image and then flash a custom ROM.
I was well aware of the risks, but have been interested in rooting for a while. Among other reasons, being able to run Market Enabler and OpenVPN apps are very attractive to me.
So I did some more research and ended up flashign to ClockworkMod with unrevoked 3. Worked fine. Rebooted, had superuser ninja app in my app folder, could get a response when terminal was prompted with "su". All good. Wifi still didn't work but I was expecting that.
NExt step, custom ROM. So I do some more research and find that there are not too many custom ROMs for the Wildfire, but my options are basically wildpuzzle, or Vibe.
I download both of them just if one of them doesn't work, but err on the side of wildpuzzle. Bigger user base, seems to be more stable, and has a lot of the things that I am interested in.
Download, move to SD card, flash it, reboot, fine! Opens great, Wifi working again, everything's good.
Until I try to partition my Sd card with ROMManager. It force closes and nothing seems to be able to get it to start wosomething root. Terminal returns "permission denied", wireless tether returns permissions problems and market enabler won't work.
All things point to not having superuser access anymore.
So I decide to restore my backup and check to see if I still have root access on that. I do, great!
Then I decide to try flash Vibe jsut as a test. It gets stuck in a boot loop after flashing it and I can't seem to get it out of it so I re-restore to my old stock ROM and am now stuck again with no wifi, but root access.
Does anyone have any ideas/suggestions/tips/how tos as to go about gaining root access again on wildpuzzle? I'd really like to have my wifi back!
Sorry I am fairly noob on android stuff, but I assumed that after you rooted the device, that was it, it was rooted and you had superuser access from then on out...
Answered my own question, so thanks if you have answer but it's sorted! Wifi and Root both working on Custom ROM!
Related
To start off, I apologize for the lengthy post, but I figure if you have all the info, you could help me begin to troubleshoot. If there is a forum and I've missed it, please let me know where it is.
I have rooted using Unrevoked 3 and flashed CyanogenMod 7 a little while ago. Over the weekend, I was low on space and battery life, trying to use my Evo as a hotspot and taking pictures, etc. Well, it froze and I pulled the battery. When I went to reboot, it only showed the CyanogenMod splash screen. I didn't have internet access at the time, but really needed my phone. I had a PC36IMG.zip on my sdcard and flashed that. I was able to get back up and running, but I lost the ability to receive text messages. I could send texts and IMs, call, use data, etc. but not receive texts.
When I got internet access, I saw that I could download a Sense ROM, flash it up, update the PRL and should be okay. I flashed Fresh Sense ROM, updated, used the MSL code reader and did the ##????# thing, reset it, but still nothing.
Today, I tried re-flashing CyangogenMod and then lost the Market, Dialer and Contacts along with the ability to edit the CyanogenMod settings along with a bunch of other little things that I haven't fully explored.
I've tried unrooting it using the unrevoked forever s-on.zip, but it stuck and the system info message (and I downloaded it 3 times). I tried just flashing the PC36IMG.zip from xda and it wouldn't flash, either.
I'm at my wits end and need some direction because I know I've missed steps and made missteps. I have to have my phone for work and if I need to take it back to Sprint that's fine, I just need to unroot it! Any and all suggestions are welcome. Thanks.
Are you flashing the new ROM's right over the top?
I've never had the problems you've mentioned but anytime i've read the forums and seen others with these problems i've often seen people recommend doing a factory/data wipe from recovery. Have you tried that before flashing the new ROM.
What I would do...
1. DL CM7/Google apps and save it to the SD Card.
2. Boot to recovery
3. Factory/Data wipe
4. Flash CM7
5. flash Google Apps
6. Boot to CM7
Give it a go.
Hope this may have helped.
Does anyone know which is newer, and what changed between the two?
I have XXUAME2, and I've updated my firmware through Kies. I don't remember what I had before. This one must be newer.
Haven't noticed any change, apart from the blue default background in the wallpapers is now a bit darker without the sun flare. I might've noticed a few very minor things in the settings, though I don't remember what they were.
Well I was on XXUAMDC when I first got my handset, and flashed XXUAMDN via Odin when getting root access. I found it removed any carrier branding and fixed a bug with the standard launcher not allowing sorting apps in folders properly. Just wondering if XXUAME2 is newer and fixes anything else.
StuartTheFish said:
Well I was on XXUAMDC when I first got my handset, and flashed XXUAMDN via Odin when getting root access. I found it removed any carrier branding and fixed a bug with the standard launcher not allowing sorting apps in folders properly. Just wondering if XXUAME2 is newer and fixes anything else.
Click to expand...
Click to collapse
I'll tell you a sad story about XXUAME2.
I rooted my phone a few weeks after I got it, everything worked fine. Then I saw the firmware update in Kies, sure I'll download! I already knew updating stock firmware would remove root, but I could always flash it again. So after I updated my firmware, I flashed root again. This time the phone couldn't recognise the superuser app, and kept alerting that there was a threat (meaning the superuser app) every 5 minutes but root still worked. So I removed superuser completely. The threat messages didn't stop, though. I flashed a clean stock ROM, everything was fine.
Until, an ancient evil awakens! (not really ancient, but...) My Group Play app started acting weirdly. It was constantly 50-70% of my battery drain, even above the screen, on my battery page. I freezed the app and hoped for the best, but it didn't work. I couldn't remove it because my root messed up. BetterBatteryStats didn't recognise anything odd. I asked XDA, but my thread only got 1 answer telling me to look for updates, and none were to be found. Google didn't tell me anything. So I gave up, and did a factory reset. I didn't really mind, I got the phone back running and looking the same in one evening, it's not as if I had years worth of stuff in it yet. This was 2 days ago, and everything seems to be pretty much normal.
I probably messed up somewhere, but thought I'd still write a cautionary tale about updating firmware while rooted. As I mentioned, probably nothing of importance was updated, so it would be a little safer to not update. You won't miss out.
Tozenator said:
I'll tell you a sad story about XXUAME2.
I rooted my phone a few weeks after I got it, everything worked fine. Then I saw the firmware update in Kies, sure I'll download! I already knew updating stock firmware would remove root, but I could always flash it again. So after I updated my firmware, I flashed root again. This time the phone couldn't recognise the superuser app, and kept alerting that there was a threat (meaning the superuser app) every 5 minutes but root still worked. So I removed superuser completely. The threat messages didn't stop, though. I flashed a clean stock ROM, everything was fine.
Until, an ancient evil awakens! (not really ancient, but...) My Group Play app started acting weirdly. It was constantly 50-70% of my battery drain, even above the screen, on my battery page. I freezed the app and hoped for the best, but it didn't work. I couldn't remove it because my root messed up. BetterBatteryStats didn't recognise anything odd. I asked XDA, but my thread only got 1 answer telling me to look for updates, and none were to be found. Google didn't tell me anything. So I gave up, and did a factory reset. I didn't really mind, I got the phone back running and looking the same in one evening, it's not as if I had years worth of stuff in it yet. This was 2 days ago, and everything seems to be pretty much normal.
I probably messed up somewhere, but thought I'd still write a cautionary tale about updating firmware while rooted. As I mentioned, probably nothing of importance was updated, so it would be a little safer to not update. You won't miss out.
Click to expand...
Click to collapse
The reason for that is chainfire's root method doesn't work for newer versions (or should I say didn't, apparently it does now). The newer kernel didn't allow root access, making the su binary appear to be missing. The error messages are also normal on newer versions, since it detects something is trying to get root access. To get around the missing binary issue, you can use djembey's modified version of getting root instead, which afaik installs the older kernel again so it can actually get root. Then to get rid of the repeated error messages, you have to disable KNOX. Again, it says how in djembey's root thread.
XXUAMDN is one of the newer versions which didn't work via chainfire's method, yet I have root access with no issues after following djembey's thread. Might be worth a look to get yours sorted.
StuartTheFish said:
The reason for that is chainfire's root method doesn't work for newer versions (or should I say didn't, apparently it does now). The newer kernel didn't allow root access, making the su binary appear to be missing. The error messages are also normal on newer versions, since it detects something is trying to get root access. To get around the missing binary issue, you can use djembey's modified version of getting root instead, which afaik installs the older kernel again so it can actually get root. Then to get rid of the repeated error messages, you have to disable KNOX. Again, it says how in djembey's root thread.
XXUAMDN is one of the newer versions which didn't work via chainfire's method, yet I have root access with no issues after following djembey's thread. Might be worth a look to get yours sorted.
Click to expand...
Click to collapse
Interesting, very interesting. I might look into rooting one more time, then. Thanks!
Funny how you helped me instead of the other way around. Thanks again, I hope more people notice your thread and maybe you'll get your answer!
where is this new firmware xxuamdn, havent found anything about it..
im having camera, battery drain, slowness issuess still hope it fixes..
Sent from my GT-I9500 using xda app-developers app
I have none of those issues, but never did even on the older version. All I did was Google for galaxy s4 update and I found a download link for it along with Odin. But there's also XXUAME2 out there and I don't know which one I'd be better having. Unless the only difference is the radio depending on where in the world you are?
OK first, I will say that I have been reading for days and days and am getting nowhere at all. I am running out of time as I am leaving Monday backpacking from OKC to Portland to meet a friend, then proceeding immediately to about 35 national parks. I HAVE to get this thing functional so that I can depend on it on the road for communication. Its current state makes me nervous. I got this tablet already rooted, custom stock rom, and with an unlocked ICS boot loader version 0.3.11. The only problems with it were the common charger/screen response issue. For $100, I can deal with that.
I flashed the Lightspeed from from the main list, everything went well... Until it rebooted the first time. Since then, directly after the bootloader screen, it briefly shows what looks like semi-colorful TV static, then shows boot animation and boots into the OS. It has never frozen on either screen.
I decided Lightspeed was not at all what I wanted, so I flashed CM10. I have yet to find anywhere in the Aroma installer where I can choose the apps installed, ONLY THEME CUSTOMIZATION. After the flash, it kept the boot animation from CM, and loaded right back into what looked like Lightspeed, and shows Lightspeed in the about menu also. I reflashed it, choosing a different boot animation to test, and did the same thing again, except it loaded ZERO extra apps at all, not even the stock bloatware. Nothing from any of the 3 roms. I reflashed Lightspeed, same thing again. No extra apps and just bare basic stuff. EXCEPT SUPERUSER. THAT DID LOAD ONTO IT EACH TIME. I haven't lost root access, the recovery works fine.
I flashed the V8 bootloader, and tried the above again. Same issues still. All of them. I have read until I'm blue in the face. If there is a way to fix this without using a PC, that would be grand. I have very limited PC access.
Anyone have any ideas? I have followed every single step 100%, I'm positive. I'm not new to rooting, flashing, and jailbreaking (doesn't apply here I know),"so lay it on me.
EDIT- I downloaded the 4.0.4 FLEX-Reaper rom and going to try that now and then I give up for the night. Tomorrow is the last day I have to mess with this before I leave. I tried to upload screenshots of the problems, but it won't let me attach them. Maybe that is another problem. Ugh who knows. Help
EDIT- That rom bricked my tablet. Through that brick, I found a working solution for the SoD, found a way to recover without files on external SD, *THIS FIXES THE BRICKS CAUSED BY CM10 AND REFLEX!!!* and I didn't lose anything. This thing is back in pristine order. I can finally sleep! Will post later on how I did it. I need sleep now.
Okay guys, I need your help. I wanted to return to complete stock and update to newest version. So I downloaded a stock ROM and let it flash the stock recovery. I got a notification for 4.3 update and went ahead and flashed that sucker. During the installation, up popped "Error". It stayed frozen on that screen, so I hard rest it, and restarted my nexus. Well, the installation went through fine. Disabled super user and went about trying to force the 4.4.2 update. Sure enough that kicked in as well. Now, I also got the error on installation of that as well, but this time, when I rebooted, it was still 4.3. I've gone through it about 10 times now. And it gives me the error every single time and remains 4.3. I did a little googling and found out how to get there error log, and it says unexpected content in boot animation.zip.
Unfortunately one of my data pins is busted in my Nexus's USB port, so connecting to PC is not an option for me. Plus my PC is down for the count until I can get a new motherboard in her. Is there anyway to obtain root without connecting to a PC on 4.3 or at least get the update to take?
Is there possibly anyway to wirelessly adb from another android device? Would that even help in my situation?
I've tried " root master" and it seemed to work, even made the Chinese root permissions manager(as a system app) for me, but I can't grant access to anything, nor am I even give the option to. Also, when I tried that, it kicked SuperSU out of system and into regular old data apps.
I suppose I can just stick with 4.3, but if you guys could, I'd love some help.
Hello,
I have a MB525 that I purchased retail in the United States so it was never locked to any carrier. Currently I'm a T-Mobile customer and have no interest in changing that. I have to say I love this phone, mainly because it seems indestructible. Even years later the battery life is still good, but the stock 2.2.2 Froyo has become something of a problem because many of the Apps I would like to use have started requiring newer versions of Android.
I can't stay in the past forever, but I'm not quite ready to give up on this device so I started looking around at my options, and would you believe I found lots of other people who have this device and have worked very hard to produce updated Android OSes for it, and who have reported reasonably good success updating the device. I figured, Its already out of warranty, so I can't void a warranty I don't have. I also figured I'm a reasonably intelligent individual and have enough experience with Unix like operating systems that even if I get in trouble, I'll be able to ask the right questions to get out of trouble. Guess what point I have gotten to?
I started following the guide wikiDOTcyanogenmodDOTorg/w/Install_CM_for_jordan The Framaroot Gimli exploit worked great. I installed bootmenu 6.1 and Clockwork Mod Recovery. Fantastic. At this point, I was able to enter CMR and backup my mostly still factory ROM. If I understand correctly this is a nandroid backup. I copied that backup off of my SD Card to my PC. From this point I felt reasonably confident I could try things and in a worst case scenario restore to this backup.
Now I happen to have a stock ROM that seems to be a bit rare online, Blur_Version.34.4.806.MB525.Latam.en.01, so I figured at this point I'd do a service and create a backup using CWM after having done a factory reset. So I booted into the stock recovery, did a factory reset, restarted, and the OS was in a like new state. Perfect. Rebooted into CWM, and made a second backup of the factory reset state. I copied this off the SD Card to the PC. Now I figured I was ready for real fun.
I figured, I might as well put the most recent Android version I could find that people were reporting success with. This appeared to be @quarkx Kitkat build. The thread is almost a year old and has 500+ replies and so I guessed that most of the major kinks would have been worked out by now. I followed the directions on quarx2kDOTru and installed cm-11-20141015-NIGHTLY-mb52x.zip from Quarx2k.ru, and low and behold it worked. CM11 booted and everything looked great. WiFi worked. Gapps worked. Play store started installing my apps.
There was one small problem. The phone refused to connect to T-Mobile at all. So I did the reasonable thing. I searched and learned about base band switching, and consulted T-Mobile on what would be the correct APN settings. Occasionally it would connect to AT&T for emergency calling, but it never connected to T-Mobile no matter what I did. From my home I was normally getting excellent signal on the stock ROM, so I am reasonably certain that the actual signal in the area was not the problem, and that this had to be some kind of configuration or software issue. A wiser person probably would have gotten on the forum and asked for help, but wisdom be damned, I wanted to do it for myself.
So more research and at some point I thought, Well, I'll go back to the Stock ROM so the phone will be usable again, and I'll take another crack at CM11 again later. It was at this point that I realized that CMR had been replaced with Team Win Recovery Project. This recovery looked to be more feature rich and easier to use, so I accepted that. I backed up my CM11 install. then went to restore my original backup. Well you might have guessed by now that TWRP and CMR don't use exactly the same backup formats. I saw no obvious way to get back to my backup and couldn't find information that would allow reinstalling CMR. This was the first warning signal I foolishly ignored.
At this point I started looking around for slightly earlier builds of CM11 that might not have had the the problem connecting to T-Mobile. Here is where things get fuzzy about how things got into this state, since the work was spread over two days at this point. Somehow between all the flashing backing up and restoring, the device got to a state where the OS never actually finished could do here is yank the battery and reboot into TFRP.
At this point, attempting to restore would just result in the messages 'E: Unable to mount '/cache' and 'E: Unable to mount '/data' in the terminal. So After searching around I learned that I probably needed to format /cache and /data because somehow they were broken. Terminal commands, I can handle this. I start reading up and find the correct command and parameters for the format, and I type into the terminal inside TWRP and low any behold format can't be found. I start looking around the directories in my file system from inside TWRP and I've got a complete directoty structure, but no files in any directories other than on /sdcard. Well fuuuu.
Not sure what made me even try, but copying any file from my sdcard into /data somehow put /data into a state where a TWRP restore would work. So at this point I was able to restore the CM11 backup, and my phone now boots into CM11, 11-20141007-NIGHTLY-mb526. But.... the cellular network still doesn't work.
But now I am wiser and I am back to the point where a wiser person would have asked for help. So... Help?
Is 11-20141007-Nightly-mb526 the best rom an appropriate rom for my device? I'm guessing I missed something because other discussions on this forum mention newer builds, and also, my device is definitely a 525 not a 526.
Is my baseband version EPU93_U_00.60.03 right? The baseband selector allows me to pick from three T-Mobile settings: 3.4.2.-107-4, 3.4.2.-107-9, and 6.xx.0, none of which seems to allow me to connect to the cell network.
Thanks in advance for any assistance offered.
Sorry for the long potato.
Here is what I did to fix my problem.
I started with the original backup of my stock rom, and I used the unyaffs.exe from this thread: http://forum.xda-developers.com/showthread.php?t=1199416 to convert my CMR backup into individual files. I then went into those files, and found \system\etc\motorola\bp_nvm_default\ and pulled out the original radio firmware from my device. From there I used advice from several pages to create my own update.zip, copied it to my SD card and I booted into TWRP and installed the zip there. Reboot and Voila, It connected right at startup to T-Mobile with the normal speeds I get from my home.
Bonus, I attached my zip in case anyone else comes across this and needs it.
My Device has an FCC ID of IHDP56LC1 if that helps anyone match their hardware.