Hi all
I have just installed TWRP 2.3.1 via goo manager to replace CWM . No problems so far, Boot into my Random rom then into TWRP which seems smoother but that is probably because I was just grateful it didn't crash after the problems reported with 2.3 .Haven't flashed anything yet but I am going to have a play and will report back if I have ANY problems.
What is the main difference between 2.3.1 and 2.2.0? Is it mostly smoothness and bug fixes? I've had zero problems with 2.2.0 so far.
Dang... I'm behind on this for my touchpad... (still running 2.1.1 while I'm on 2.3.1 on my phone...)
Related
Well I installed this version and 13 As with the wifi does not work, goes on but just does not work online.
Would greatly appreciate any help, and what they tried eh posted but still the same: S. Thanks in advance
Sorry for my English, a translator.
It happened to me too in v13. I updated to the v14 version and fixed it. Don't forget install the Wlan.zip (4.42 MB) (New Wlan Modules) with CWM Recovery!
http://forum.xda-developers.com/showthread.php?t=1201116
Hopefully, that fixes the problem, but don't get too excited
Tried reinstalling, wiping, new wlan modules hotfix etc etc, but the rom refuses to work properly with the wifi. I was able to use the web-browser by telling it which IP to go to, instead of www adresses, but still, the market function and other internet functions won't work.
If I were you, lojoko, I would go for GinTonic, earlier release of MiniCM7 rom or some other rom and wait for MiniCM7 to get fixed again. Hopefully, it will be fixed soon. Love that rom!
Had a really good hunt around for wifi fix. It seems some people get the "Error" when switching on wifi and then it sticks. Had to revert to GinTonic 2.0
i'm having the same issues with v19.
i switched to minicm7 because gingerdx was giving me the same trouble. i'm helpless. In fact i'm thinking about switching back to minicm6(froyo)... Gingerbread is not working for me.
lokinmodar said:
i'm having the same issues with v19.
i switched to minicm7 because gingerdx was giving me the same trouble. i'm helpless. In fact i'm thinking about switching back to minicm6(froyo)... Gingerbread is not working for me.
Click to expand...
Click to collapse
hi,
had the same issue with v19 wifi not working.
then i found out that it worked when the rom v19 was fresh installed, but stopped working after restoring missed apps and all system data with TITANUM backup (backup made on V17)
hope this brings you further with your wifi problem.
onlyime said:
hi,
had the same issue with v19 wifi not working.
then i found out that it worked when the rom v19 was fresh installed, but stopped working after restoring missed apps and all system data with TITANUM backup (backup made on V17)
hope this brings you further with your wifi problem.
Click to expand...
Click to collapse
I'm using fresh SE install from SEUS and wiping everything before installing MiniCM Pro v19. Still having the issues. I don't use any restoration option.
I apologize to everyone if this has been answered (I'd be surprised if it hasn't but couldn't find it using search).
I recently moved from a v1.1 bootloader ROM to a v1.2 bootloader ROM. While I was on the v1.1 bootloader I enjoyed using ClockworkMod .8 to do my flashing/installing/clearing/wiping/backing up and restoring. Now that I've have to rely on the Stock recovery to install my current v1.2 ROM I really miss having the ease of use of ClockworkMod. I am currently using Roebeet's Mountain Laurel 3.1.0 ROM but it's got the stock kernel and aside it from feeling sluggish (compared to VEGAn 5.1.1) I can't get VPN to work on it.
Using his instructions I "enabled" Clockwork that is supposed to be compatible with v1.2 ROMs on this tablet and actually succeeded in booting into Clockwork recovery. After Clockwork came up I flashed Pershoot's last Froyo kernel for the gTab and then rebooted. It came up stuck on the birds screen and I had to NVFlash back to where I started from.
So my question is has anyone successfully installed Clockworkmod v3.0.2.8 on the gTab running a v1.2 ROM and was able to flash a custom kernel and the tablet didn't get stuck on boot or suffer any other reboot related problems? My current experience is that only the Stock recovery is happy on my tablet with this ROM for some reason.
Any info that would get me to the point where I can run this ROM with Pershoot's last gTab FroYo kernel (7/27/11) successfully would be greatly appreciated.
Regards,
Steve
Update: I really owe everyone an apology for having overlooked such an obvious piece of information that would have made the hassle of the last few days of near-constant NVFlashing unnecessary. The instructions from Roebeet was fine, the problem was me (of course; user-error). ClockworkMod was working fine and is now still working fine on my gTab. The part that was the obvious thing that I should have noticed earlier was that the version of Pershoot's last FroYo kernal for the gTab had 2 versions (1 for the 1.1 bootloader and another for the 1.2 bootloader). Once I finally noticed that little discrepancy between the kernel zip file I had and the one he listed on his Droid Basement blog site it was smooth going. I was even able to install SetCPU to change my tablet's operating speed and as another bonus I was able to install the 5 VPN app from the Market to expose the VPN settings on the gTab using the Mountain Laurel 3.1.0 ROM and actually set it up to use my VPN account from my VPN vendor (StrongVPN). I am currently in Texas watching a program using the BBC iPlayer app as if I was in the U.K..
Now if I can get the VTL Launcher running on this ROM without it getting into a seizure of force closes I'd be out of things to want for on this ROM.
Anyway, let this be a lesson to everyone here that you don't have to be a noob to suffer a brain-fart.
I am writing to report that I am having trouble with the jockersax 3.3 beta. This is the first time that I have had a problem loading either one of the jockersax
CM 9 roms I hope this is of help. What I had to do was flash it twice going through fastboot into Android Recovery.
Any other ROMs tested after you failed with 3.3?
I'm starting to wonder if it's possible to burn out flash memory used for ROM.
My own Atrix works pretty well with 3.3.
I'd like to know how many times it's safe to flash a new ROM with respect to memory life?
flashed it once
flashed ver 0.3.3 only once and flashed gapps no issue.
even flashed 1.45 kernel
in the past had alternated between cm7 & cm9 without any issues. haven't gone back to CM7 ever since jokersax released 0.3
I have been using both turl's and jockersax's Kanged CM9s both work well but I have not been able to get the video to work which I use at times where I work. As I posted flashing jockersax 3.3 beta was the first time I had any issues with flashing a rom on my Atrix 4G, but it was a good learning experience as I learned how to use fastboot to navigate into Clockworkmod Recovery. Second on the issue of life span for memory I belive that pc solid state drives are supposed to be able to do over a hundred thousand rewrites so I would guess that you would buy a new phone before the memory was degraded. One thing I don't understand is why everything is not on removable media that way if you had a problem you could just flash onto a new chip and install, that is how the Raspberry Pi is and I don't see why it could not work for phones. But the truth is probable that it would work but then the "Providers" would have less control over us.
I'm sure people were getting pretty tired of hearing about the radio issues when people flashed cyanogenmod (ie, LTE worked, but no SMS, MMS, or voice calls, odin didn't fix, the only solution was to factory restore from WITHIN a TW ROM). After waiting a while for things to calm down, I'm ready to try to install Cyanogenmod again but I am naturally hesitant.
Has this issued resolved itself? I'm running rooted and unlocked MC3 with CWM installed. I heard somewhere that flashing the MJ9 radio BEFORE Cyanogenmod 10.2 / 11 fixed the problem?
I would really appreciate any input or personal experience here!
As far as I know, the issue has not resolved itself. I tried flashing the newest CM 11 a couple of days ago (I think it was the nightly build on the 22nd), and I still had the funky radio issues. However, I tried this, and it fixed all the radio issues with CM 11 (and any other Android 4.4 ROMS - I'm running Slim ROM at the moment)... Here is my post from another thread.
Hey all, I got it working (the data/network connection that is), with a little effort. Here is what I did in sequence...
1) Reflash the ORIGINAL VRALJB image via ODIN. I used the one found here. You want to make sure you get the one that replaces EVERYTHING, i.e., NOT the alternative restore.
2) I set up my phone and used it normally for about four hours. (This may or may not be necessary, I'm not entirely sure. I also rebooted the phone about five times during that time frame.)
3) I unlocked and rooted the phone via the method outlined here. After that was done, I installed CWM 6.0.4.3 via TWRP (which the unlocking process installs).
4) I then installed CM 11 and the respective Google apps. (I first did a backup, then a factory reset, then cache wipe, then dalvik wipe. The next thing I did was install CM 11, then Gapps.)
5) Restart the phone and success!
Click to expand...
Click to collapse
The reason why I found out that this method would work, is that I tried installing CM 11 on my dad's phone. He has had a TW ROM (Beans build to be exact) since the phone came out. And he has been running the stock VRALJB radio. With that said, I figured I would try flashing the stock ODIN files to restore my phone back to the VRALJB. (I think I was running the MJ9 prior to this) That worked, and the SlimROM has been working perfectly ever since!
[Also, if you wanted to check out SlimROM, you can find a link to it here.]
Still looking for some more feedback from users! Anyone successfully flashed CM 10.2 / CM 11 from MC3 without problems / fixed the problems?
Hi guys
My mido vibration stopped working a week back abruptly. I didn't flash anything new back then.
Tried diagnosing it with change of vibration motor (with a technician) as well but the new one didn't work either. He did attempt a temporary replacement of its underlying chip as well but again it didn't resolve the issue.
Attempted clean reflash RR. Then clean reflashed Havoc 2.9 build as well.
After reflash in both the builds, didn't install Magisk (just to be sure some version could have been conflicting with the motor may be)...No solution
Attempted firmware upgrade to notably stable versions 10.2.3 and then downgraded to 9.6.3 as well. No solution still....
Could anyone advise what I could attempt next..?
Current environment: Havoc 2.9
No magisk installed as of now.
Nothing works.
Magisk 20.1 was installed but removed now... Still doesn't work...
Please help.