Hi All
I have been using custom ROMs for my international Galaxy Note 2 - GT N7100 for around a year now and had not faced anything similar to this.
Recently, I installed the latest Omega ROM on my phone and it worked fine. But since then, I am unable to wipe and install any other ROMs like Kira, ROMOW, Hawkish, Monxdified etc, pretty much every ROM on 4.1.2 version, available. I have used both TWRP and Philz Touch Recovery to install these ROMs without any luck. One more thing, I always use, Android Revolution Wipe to wipe the internal SD before a fresh installation. But nothing helps now.
I am beginning to belive that there is something in Omega that is not allowing me to move on... :silly:
Or something has changed in the recent past - post this July.
I see many threads similar to this, but the solutions / suggestions go in different ways. So opening a new thread here, hoping to hear from anyone who knows what to be done.
Thanks for your help and time.
Related
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Did you do a full wipe ???
ryansinibaldi said:
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Click to expand...
Click to collapse
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
donhashem.dh said:
Did you do a full wipe ???
Click to expand...
Click to collapse
Full wipe as in? (sorry, still a bit new). I did do a factory reset in CWM before installing whichever ROM I was trying at the time. I wiped all caches too.
slack04 said:
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
Click to expand...
Click to collapse
I used the HTC One V AIO Toolkit to unlock the bootloader, get root, install CWM 6.0, create a backup and then install a kernel (I used the Super Sick JB one). From there I used CWM to gain access to my SD card and transferred over the CDMA Pacman ROM (after wiping everything clean) and then installed the ROM. It booted up successfully however as stated in a minute or so it would freeze up and restart itself. Even if I don't do anything after a reboot it'll still reboot itself anyways.
I did a bit of research and I'm thinking it could be due to the OTA Radio update from 2-3 weeks ago? I'm at my bootloader now and it says I have radio version 1.00.00.0928.
Any further help to resolve this issue would be greatly appreciated. It's worth noting that I've tried many different Kernels (repeating all the steps above with full wipes every time) and different ROMs that were supported by the kernels. I've even tried to restore my phone back to stock and it just starts skipping at the VM Boot screen.
Oh, and I'm running Windows 7.
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
donhashem.dh said:
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
Click to expand...
Click to collapse
Pardon my ignorance but that just doesn't make sense. I've tried several different ROMs with the correct kernel's (Pacman, CM9/10, AOKP JB) and it's all the same scenario. They all boot (or occasionally don't boot and restart themselves at the boot animation) and then reboot themselves once they're pass the lock screen.
Like I said even currently if I restore my stock rom file it just loops at the VM Boot animation (which doesn't play fluidly).
Figured out the issue . It was radio version 1.00.00.0928 messing up my kernel.
I tried to post this on cyanogen mods website but I was not allowed to post
I bought a AT&T Galaxy S III for my wife this weekend and ran into several problems installing cyanogenmod 10 on it.
Installing:
First the Heimdall program failed to "initialize interface" and no matter what I tried it failed to connect.
I managed to get it installed by using the ODIN to flash different clockwork mod (but that errored out on the when I went to flash cyanogenmod 10 )
So I used that to root it then installed cyanogenmod via rom manager by having that install the right clockwork mod then cyanogen 10.
It would be nice if they provided a ODIN Image for cyanogenmod
VoiceMail:
voicemail was missing its number after I installed cyanogen mod.
It took me forever to get this correct. Found out that you just forward to your mobile number. In the phone settings. or dial **004*PhoneNumber#
Also Google voice failed to setup correctly as well and had to use the **004 path.
Skype:
downloading via google play kept returning "package file invalid" (I cleared /cache and dalvik cache still failed) I ended up downloading it via the androiddrawer website and it installed (sideload?).
The problem with this is when using the voice or video chat the other side just hears very load static. Found someone claiming these problems came from cyanogenmod 10 not using the correct mics all the time. This is still an issue.
My questions are these issues fixed in the most recent version of Cyanogen the M releases? And if not are they known and someone working on them?
And does anyone have a fix for the static issue in skype?
JonoPorter said:
I tried to post this on cyanogen mods website but I was not allowed to post
I bought a AT&T Galaxy S III for my wife this weekend and ran into several problems installing cyanogenmod 10 on it.
Installing:
First the Heimdall program failed to "initialize interface" and no matter what I tried it failed to connect.
I managed to get it installed by using the ODIN to flash different clockwork mod (but that errored out on the when I went to flash cyanogenmod 10 )
So I used that to root it then installed cyanogenmod via rom manager by having that install the right clockwork mod then cyanogen 10.
It would be nice if they provided a ODIN Image for cyanogenmod
VoiceMail:
voicemail was missing its number after I installed cyanogen mod.
It took me forever to get this correct. Found out that you just forward to your mobile number. In the phone settings. or dial **004*PhoneNumber#
Also Google voice failed to setup correctly as well and had to use the **004 path.
Skype:
downloading via google play kept returning "package file invalid" (I cleared /cache and dalvik cache still failed) I ended up downloading it via the androiddrawer website and it installed (sideload?).
The problem with this is when using the voice or video chat the other side just hears very load static. Found someone claiming these problems came from cyanogenmod 10 not using the correct mics all the time. This is still an issue.
My questions are these issues fixed in the most recent version of Cyanogen the M releases? And if not are they known and someone working on them?
And does anyone have a fix for the static issue in skype?
Click to expand...
Click to collapse
Unless your wife can troubleshoot issues why install a custom ROM on her phone. My wife would kill me since she has no clue but I digress.
Why not flash 10.1 on the phone and download the gapps from the goo.im site and see if hat helps your issues. Maybe you got a bad flash and/or download. For the short amount of time I tried it I didn't have any of these issues you do. Those don't seem to be any bugs in the known bugs beyond maybe the static. Task's AOKP is another one to try if you want a custom stable rom.
Try another ROM or maybe a fairly stock rooted rom and see if that clears up any issues.
Are you using a Mac or a PC ? You mentioned Odin (for windows PC's) and heimdall (for all others). Honestly the best way is to flash a stock rooted ROM from the no tripping flash counter Rooting thread in Development and then flashing CWM in rom manager. Limiting having to flash in odin is the far better option. I've never ha d a bad flash in a custom recovery but everytime I have to use Odin I get extremely nervous.
Read Beerdroid's guide and you can't go wrong
hednik said:
Unless your wife can troubleshoot issues why install a custom ROM on her phone. My wife would kill me since she has no clue but I digress.
Why not flash 10.1 on the phone and download the gapps from the goo.im site and see if hat helps your issues. Maybe you got a bad flash and/or download. For the short amount of time I tried it I didn't have any of these issues you do. Those don't seem to be any bugs in the known bugs beyond maybe the static. Task's AOKP is another one to try if you want a custom stable rom.
Try another ROM or maybe a fairly stock rooted rom and see if that clears up any issues.
Are you using a Mac or a PC ? You mentioned Odin (for windows PC's) and heimdall (for all others). Honestly the best way is to flash a stock rooted ROM from the no tripping flash counter Rooting thread in Development and then flashing CWM in rom manager. Limiting having to flash in odin is the far better option. I've never ha d abad flahs in a custom recovery but everytime I have to use Odin I get extremely nervous.
Click to expand...
Click to collapse
agreed.
there are a couple good and stable stock/touchwiz custom roms as well as AOSP-based roms on this forum. i would steer clear of nightlies and super-custom roms that are always posting new updates. these are less stable imo.
put something on her phone thats solid and be sure to use the proper wiping and flashing procedures when you do so. wiping/flashing correctly makes ALL the difference on the software's performance while it's running on a device
xBeerdroiDx said:
agreed.
there are a couple good and stable stock/touchwiz custom roms as well as AOSP-based roms on this forum. i would steer clear of nightlies and super-custom roms that are always posting new updates. these are less stable imo.
put something on her phone thats solid and be sure to use the proper wiping and flashing procedures when you do so. wiping/flashing correctly makes ALL the difference on the software's performance while it's running on a device
Click to expand...
Click to collapse
Well I went with Cyanogen because I used it on my old droid incredible and its was great. I also want a stock like rom because I personally use a stock Nexus 4 and want my wifes phone to be similar and wanted to remove all the retarded extra apps atnt and samsung threw on.
So no idea if the 10.1 would fix the static issue then?
JonoPorter said:
Well I went with Cyanogen because I used it on my old droid incredible and its was great. I also want a stock like rom because I personally use a stock Nexus 4 and want my wifes phone to be similar and wanted to remove all the retarded extra apps atnt and samsung threw on.
So no idea if the 10.1 would fix the static issue then?
Click to expand...
Click to collapse
I can't say for sure but download and see if it works out of you. Thing with bugs is that they aren't always reproducible. I don;t see your issue as a known bug on 4.2.2. There are a few other ROM like super nexus in the dev section that are a practically stock nexus feel. Why not give that one a try ? Give AOKP a try as well.
Here's super nexus:
http://forum.xda-developers.com/showthread.php?t=2219944
hednik said:
I can't say for sure but download and see if it works out of you. Thing with bugs is that they aren't always reproducible. I don;t see your issue as a known bug on 4.2.2. There are a few other ROM like super nexus in the dev section that are a practically stock nexus feel. Why not give that one a try ? Give AOKP a try as well.
Here's super nexus:
http://forum.xda-developers.com/showthread.php?t=2219944
Click to expand...
Click to collapse
i'm an advocate of AOKP, but thats just my 2 cents. there is a very solid 4.1.2 milestone out and their 4.2.2 milestone will be released very soon.
although faryaab is a great kid and puts some good stuff together, remember that supernexus is a port and you could experience bugs (as i did). again, just my opinion
As the title says, I am running gedeROM 1.55 for the past year, since I experimented with a couple ROM's and settled on this one. For the most part its been a decent daily driver but have found it a little 'sluggish' lately and it annoys me. The lack of deep sleep keeps me always scrambling to keep it charged and ready to go so I don't find it dead when I want to use it.
Of course in the process I am using an older version of FFF and TWRP, so I know an update of them would be necessary.
A couple questions, looking for opinions:
1. Is it possible to just use KFU and update FFF and TWRP without disturbing everything else? I'd like to get them up to date.
2. After reading for 2 hours or more I am unclear on the limitations of 10.1 JB and wonder if I should be changing to JB at all?
3. Are the 10.1 ROM's a better option than I am running for speed and reliability? If so, any shining star amongst them?
I know asking for opinions will bore most people to death reading this, but I need some guidance from those that have been active and keeping up with ROM dev on this unit while I left mine alone and got behind.
Thanks in advance.
This might help you:
1. Look on the first post of this thread. Theres a flashable zip for FFF1.4 (Just flash in TWRP)
2. Here is Ichigo's flashable zip for TWRP 2.5.0 (Just flash in TWRP) https://www.dropbox.com/s/b4idirzkmgvnm07/TWRP-Blaze-2.5.0.0.zip
Those will not disturb anything else.
And try This ROM first and see if you like 4.2.2. This is the OFFICIAL cyanogenmod 10.1. To me its by far the best in terms of stability and speed. Make sure you wipe everything BUT /sdcard in TWRP before you flash!
Moving to a recent JB ROM will be a good move compared to gede because not only will you have better battery life but you'll have almost another year of improvements made to the Kindle since then.
Thanks for the info.... I'm gonna give this a shot I think. Not much to lose, nothing mission-critical on my tablet anyway
I'll post back once it's done!
Thanks again.
Bozz5384
It seems to have gone well, thanks for all the info. Updated FFF, TWRP, and now on CM 10.1 ... I did the 5/20 nightly, wasn't sure which one to do -- seems pretty bug free at this point.
As of recent, I've been having a ton of stability problems on my S2 across all ROMs. It will often get sluggish and randomly shut down, the WiFi will completely drop and I won't be able to connect unless I restart my entire phone, and various other problems. I've done a full wipe when installing any ROM and problems only came up when I installed cwm 6.0.4.3 and I was wondering if that may have been the issue. Either way, I was wondering if there was a way to completely wipe my phone and bring it all the way back to factory and how it came in the box so I can completely start over to try to fix these problems. Any other suggests would be greatly appreciated, too.
Currently running BeanStalk 4.4+, last "stable" build was with Cyanogenmod 10.1 nightly.
Thank you to everyone in the XDA Developer community, you certainly are amazing and thank you to the developers of the search function, I may not know how to use it to it's greatest potential but it's certainly helped me a TON. This is the first time I've felt I've actually need to make a post for something going wrong, sorry if the problem has happened in the past and I missed a post.
Dude i had a similar problem a while back switching from TWRP to CWM. Somehow I corrupted my Dalvik partition. I couldn't even get back to recovery.
So I went here. Followed the instructions and completely went back to stock.
Quick Note that I don't see mentioned enough, YOU WILL LOSE YOUR APPS AND SETTINGS, (hopefully thy're all backed up with Titanium), BUT YOU WILL NOT LOSE YOUR STUFF ON YOUR INTERNAL OR EXTERNAL SD CARDS. The first time I went back to Stock I was scared s***less because I thought I was losing all my pics.
When I booted up the first time, I got the "repairing" Android Icon, it rebooted and I was back in business.
Then I had previously grabbed the TWRP odin flashable 2.5.0.0. tar file from over here. I got 2.5.0.0 because I planned to flash a 4.2.2 ROM after all is said and done. I flashed that with Odin from Download Mode.
I didn't even bother logging into Google on the stock 4.1.2 ( I just can't go back TouchWiz after Cyanogenmod). I just rebooted right into TWRP 2.5.0.0 manually with Volume up and Power button.
From there I factory wiped everything, then superwiped and cachewiped ( both can be found http://forum.xda-developers.com/showthread.php?t=2235141), just to be on the paranoid side.
And finally I flashed Cl3Kener's latest 4.2.2 version of his BlackLiquid and his latest 4.2.2 stable Uber Kernel. I personally think this is the most stable, and as close to perfect ROM thats going to come out for this phone. Of course that is just my opinion after my own experiences with 4.3, 4.3.1, and 4.4.
This is a completely streamlined version of the complete cluster f** I did researching, trial and error, and starting over, while I was in the middle of actually doing it. One last tip I can give, is to get all the files you think you might possibly need and put then on your external SD if you got it, or internal SD. Its a real pain stopping and starting cause your missing a zip you forgot.
Hope this helps
Huge thanks to the Developers threads I Linked to.
Hi all. I've been running a Sprint L710T and am a bit overwhelmed by the variety of opinions regarding what can and can't be currently done on this particular S3 model.
Disclaimer: I am quite new to rooting and ROMS!
How I rooted my Sprint L710T:
1. Used Odin3 v1.85 to flash Sprint CWM recovery v6.0.4.5.
2. Copied SuperSU v2.00 to internal storage on phone.
3. Rebooted into CWM recovery and installed SuperSU v2.00.
4. Rebooted into OS and ran SuperSU, disabled KNOX. Phone is now rooted.
After looking at a few roms, I decided to try Gummy ROM (M3.0-07-16-14-RELEASE-d2lte), Installed without a hitch along with gapps (pa-gapps-stock-4.4.4-20140629-signed). Bear in mind that up till this point I did not know I had a L710T! I was ignorantly working under the assumption that it was a regular Sprint L710. Regardless, I guess I was lucky since at this point all was working in Gummy ROM except for screen rotation being reversed. I then rebooted back into CWM and made a nandroid backup. THANK GOD I did this! After a few days I decided to try some other roms and in ALL OF THEM I had no baseband. Fortunately I was able to revert to my nandroid backup.
So this brings us to the present. I now am aware that I have a L710T so I have not tried any other roms. I want to try out some of the Touchwiz roms but am now concerned that I will mess something up.
Now for some questions I've been pondering:
1. Is there any "danger" in flashing L710 (Non T) roms?
2. Will reverting to my nandroid backup ALWAYS work? Can flashing a particular rom mess things up to the point my nandroid cant save me?
Hopefully we can keep this thread going and make it a source for all things Sprint L710T.
Cheers!
TujungaGuy said:
Hi all. I've been running a Sprint L710T and am a bit overwhelmed by the variety of opinions regarding what can and can't be currently done on this particular S3 model.
Disclaimer: I am quite new to rooting and ROMS!
How I rooted my Sprint L710T:
1. Used Odin3 v1.85 to flash Sprint CWM recovery v6.0.4.5.
2. Copied SuperSU v2.00 to internal storage on phone.
3. Rebooted into CWM recovery and installed SuperSU v2.00.
4. Rebooted into OS and ran SuperSU, disabled KNOX. Phone is now rooted.
After looking at a few roms, I decided to try Gummy ROM (M3.0-07-16-14-RELEASE-d2lte), Installed without a hitch along with gapps (pa-gapps-stock-4.4.4-20140629-signed). Bear in mind that up till this point I did not know I had a L710T! I was ignorantly working under the assumption that it was a regular Sprint L710. Regardless, I guess I was lucky since at this point all was working in Gummy ROM except for screen rotation being reversed. I then rebooted back into CWM and made a nandroid backup. THANK GOD I did this! After a few days I decided to try some other roms and in ALL OF THEM I had no baseband. Fortunately I was able to revert to my nandroid backup.
So this brings us to the present. I now am aware that I have a L710T so I have not tried any other roms. I want to try out some of the Touchwiz roms but am now concerned that I will mess something up.
Now for some questions I've been pondering:
1. Is there any "danger" in flashing L710 (Non T) roms?
2. Will reverting to my nan-droid backup ALWAYS work? Can flashing a particular rom mess things up to the point my nan-droid cant save me?
Hopefully we can keep this thread going and make it a source for all things Sprint L710T.
Cheers!
Click to expand...
Click to collapse
glad your rooted and the info for this model is spread out this forum and im going to post a video about what i know sometime this week on my YouTube channel you can link to my boost root thread if you want cause there is one more method to root this model and it's your kernel that is in charge of your rotation if you flash a custom TW rom you have to somehow restore your stock kernel for good rotation
New L710T
So I just ordered a GS3 from Virgin as it's on a good sale price and I'm desperate for a new phone, then I start googling about ROMs and get super excited to get either CM11 or an unofficial CM12 running...and then I find out I ordered an L710T.
So couple things. I would be more than willing to try and backup all of the factory set data from the phone--the stock ROM, stock modem, etc., since this stuff seems to be kind of hard to find and is scattered all about.
However, any ethical questions aside, has anyone ever bought a phone, made backup recoveries to put online and returned it? Because unless I can flash CM11 and then flash a backed up copy of the stock modem and use the phone with data, then I'm probably going to want to return the phone I ordered and get an L710 if I can find one. Does that seem reasonable, flashing stock recoveries after CM11? Or is that likely to break things? Half the reason I ordered a new "flagship" model phone was because my old cheapo had no roms available and not even an unlocked bootloader, so the idea of being stuck with TW roms is a huge disappointment.