Hello all,
I just recently noticed the RC3 for CyanogenMod, and tried to flash it, I failed with the status code 7, and disregarded it, and went back to my old CyanFox ROM. Weirdly, i started to not be able to connect to AT&T and get no service for minutes at a time, about every 10 minutes. I flashed LiquidSmooth, same problem, flashed CarbonROM, same problem. i flashed the most recent modem baseband, but the problem persists. I cannot seem to find a solution to this, so is there anything that would hopefully help?
Status 7 can be due to using an outdated recovery to flash KK ROMs. I suggest updating your recovery, wiping, and re-flashing.
Related
I tried to post this in the development section, under the rom I flashed directly, but since I don't have 10 posts I couldn't. Anyway, I am having issues sinced I flashed this rom last night. I flashed the hellfire rom, and also the liquid smooth rom. In both roms, when I am using my phone it states that is has a 3g connection in the notification bar, but immediately once I start using the data (speed test, chrome, etc.) it jumps to H+. As soon as I close the application I am using, it reverts back to the 3g connection. Is that something that was done on these newer roms, possibly to conserve battery? I have never flashed any other roms with this phone and until recently was sitting on stock rooted UVLH2.
Also, another question I had is when I flashed both of these roms through CWM 6.0, everything installed correctly but the baseband stayed on UVLH2 and didn't update to the LI7 or LI8 that it was supposed to, and I had to directly install LI7. Is that normal? I came from the Vibrant and G2X and whenever I flashed a rom, it normally also changed the baseband itself. I have tried searching before starting this thread but haven't found an answer to either of these questions. Thanks for any help guys.
Hello everyone, just got a quick question to ask.
I was running CM10 stable and had a problem with my SD card a while back (which I never figured out), so I decided to preform a clean wipe of CM10.0 and a stock rom as a troubleshooting method.
I finally stuck back with CM10.0 and I've been rocking that install for some time, but have a problem. Every fifteen minutes or so the phone's cell connection would drop completely then pick back up a min or so later. It's very temperamental and I have no idea what was causing it. It never inhibited the utility of the phone, so I just dealt with it.
Today I flashed a clean install of Paranoid Android, gs2usr's unofficial version, and it still has the same issue.
I've flash different modems and the issue still remains, but I have no idea where to troubleshoot beyond that.
Any ideas guys?
|EDIT| Solution was taking it back to stock by flashing with Odin then re-rooting and flashing CM10 stable. No issues so far!
So I've recently been having an issue with my phone that I haven't been able to fix through various standard fix methods. I've tried searching for this exact issue but the only thing that seems to work for other people (albeit they were on different devices when they had this problem) hasn't fixed my issue.
Long story short, I went from SlimROM 2.2 (and many other 4.3 based ROMS) to ForkMyLife 4.4.2 to try out KitKat, and I eventually wanted to go back to SlimROM.
I always full wipe (System/Data/Cache/Delvik) and then flash my ROM (in this case it was Slim), a reboot netted me a bootloop/boothang on the bootanimation. Wiping Cache+Delvik cache will get me to Optimizing Apps, but then it hangs at Starting Apps. At which point I can battery pull, restart, and it will restart just fine (typically, I did have one time where this didn't work). But I'd have to do this series of events every single time I reboot. I've tried multiple ROMs, multiple kernels, but everything ends up doing the same thing after a reboot. I've even done a full Stock 4.2.2 Image flashing (full SDCARD/DATA wipe an everything) using mskip's Toolkit, re-rooted and re-did my entire phone to Liquid 2.37 booted up the first time no problems, but the boothang was back on the very first reboot.
What is somewhat odd to me, is that I can run a 4.4 based ROM with no boot issues though. I ran FML 4.4.2 for a few days and numerous reboots, and the same for OmniMetal 4.4.2 to see if it would lead to any boothangs and I had no problems with either.
Any ideas or thoughts from anyone on why reverting back to 4.3 after a 4.4 ROM would cause so many issues?
Hello,
I am facing a weird problem with my htc one v for 4-5 months. Several times I installed custom ROMs and KERNELs and also went back to original ROM using ruu. I did that because 3G was not working. I thought if I could get it back. But few months ago , I tried CM-10 KANGBANG and after that 3G started working like before. But now I could not install original ROM. Even I was unable to install kernel and recovery. because it always shows problem with pc connectivity. I tried other roms which require kernel flashing. but could not connect to my pc to flash kernel. so those ROMs became useless. Now I am using MIUI by rulling. thanks to that ROM. only this ROMs works now. It just happened after installing CM10 KANGBANG. its so irritating. What will I do now? I tried rumrunner. still negetive. no connectivity with pc.
Hello guys,
It's been a while since the last time I visited the SGS3 section, over a year ago I remember updating the bootloader in order to upgrade/flash to 4.4.4 which went very smooth and was a success. I gave the phone to a sibling who has been very happy with it for the last year and a half. Lately, the phone has been very unstable with the 4.4.4 KitKat ROM, WiFi doesn't turn on, Bluetooth is unstable, Unstable apps/Force closes. I tried a wipe/factory restore and re-flashed the ROM but the problems persisted.
I did a little research and liked what CyanogenMod is doing and since they are actively supporting the phone I decided to flash CM12.1 and the provided Open Google-Apps, CM12.1 flashed successfully but Open Google-apps refused to install, CWM displayed (Section 6) error which upon research it is common with CWM and the solution is to flash TWRP. I booted with CM12.1 in order to install TWRP Manager through the APK and flash TWRP but it force-closed when it searched for the device model. WiFi was working but Bluetooth was still unstable.
I would like to know what would be the best way to proceed in this case, I would like to upgrade the recovery to TWRP and flash CM12.1 or any other stable Lollipop ROM.
Thanks,
Oscar
absolute all credit to @audit13.
http://forum.xda-developers.com/showthread.php?t=3313734
perhaps this will help.
"err on the side of kindness"