Hi all, complete newby. Have an old galaxy 7. running really slow and was getting annoyed i cant run some of the latest apps. SO decided to attempt to put a Rom up to Jellybean.
1. I put the CWMOD on using odin by following a tutorial I found. went ok
2. I followed tutorial to copy the rom to my root.
3. completed Datawipe/reset
4.cleared cache
5.cleared Dalvik cache
6. Installed zip from sd card.
It didnt work. it said it was not supported / error had occurred.
So decided to wipe again and tried again a couple of times. still did'nt work. Plan B load AOKP_p1_build 38.
I Did as above and seemed to be going okay until reboot. it returned me to a modified CWmod screen that is now turquoise in colour instead of orange. when i reboot I get the galaxy screen, then the AOKP screen, but then it jumps to the CWMod boot screen.
I dont know what to do now?? any help greatly appreciated.
UPDATE
I managed to get it running after a few resets and cache wipes. Ive noticed after the fact that I didnt use Nandroid or bootstrap or anything like that. this was because i was not bothered about losing any pictures etc.
However:
I now get the 'cannot use android keyboard' message. I stopped and cleared its cache in settings, but this hasnt helped. searching around I have realised I caused this issue by installing newer Gapps than the android build.
My questions are...
1. Can I download and install a newer AOKP build for my Galaxy 7 GT-P1000, and a newer Gapps?
2. Can someone provide me with links for the AOKP build and Gapps if so?
3. Do I follow the same process as I did to get these on?
Related
i finally broke down and rooted my Tbolt. I installed Rom manager and am trying to install a new rom. I have tried cyanogenmod 7.1.1 and also Liquid smooth 3.2 . the process seemed to go fine, but each time it got stuck at the splash screen,not the white HTC one, but the "intro" screen for the rom i am installing, i let it run for several minutes, finally removed battery and restored my backup.
anything i am doing wrong?
here is some more info on the phone,
Downgraded to 2.3.4 , rooted with revolutionary root, running the most current free version of Rom manager free from market
any help would be appreciated
First thought
Have you wiped the data of the phone before you tried to install the ROM? I am now expert here but I had a similar problem and when I searched forums for the answer that came up quite a bit. I might start there.
Also the ROMs have very specific install instructions and I would follow them closely to avoid any problems.
I searched and read so much before I rooted and installed my first ROM, it does get easier.
Good luck.
Update your CWM version in ROM manager.
It should be the top choice when you open ROM Manager - update Clockwork Recovery.
Make sure you have ample space on a FAT32 formatted SD card, as well a the minimum radio(s) required for CM.
Prior to flash, in recovery, make sure you wipe data/factory reset and clear cache - also go into advanced and format system.
Post back your results and we'll go from there.
Hi folks and especially Chainfire if he is tracking nu-bees,
Nu-bee here. Just installed Resurrection Remix Pro ICS firmware following instructions at Galaxy2Root.com. They had me install 3 files with the Remix package, GoogleApps and GoogleAppsFix. All went well. Then the instructions told me to install 10_CWM.zip so that ClockWorkMod would work. But CWM had been overwritten, so I couldn´t install something from my internal sdcard. I thought I would be clever and install one of Chainfire´s custom CF-root packages. I selected one close to the kernel number I have installed (LPJ). I flashed it over with Odin.
No joy. The phone booted, showed the opening logo and then lay there with a black screen. But CWM recovery still was active, so I wiped the system and reinstalled the files this time including 10_CWM.zip (4 files). This time I have ICS but CWM is gone again. I´d like to back up the ROM.
I´d like suggestions as to how to get CWM installed. I would be most grateful! I read the entire 450 page set of posts on Chainfire´s CF-root upgrades (whew). I´d use one of those if I was confident that I wouldn´t go back to a black screen again.....
still trying
Well, I haven´t gotten much of a response with this. With this 10 post limit for noobies, I can´t get to the developers forum where I would find the folks who grapple with these kinds of issues.
Anyway, I flashed the latest of Chainfires kernels, the LP7 version, and ended up with a black screen again. So I went into restore (and had CWM restore at least) and restored my ROM, etc. But of course, I lost CWM in the process. And had to reconfigure my phone all over again. I had used My Backup Pro and it didn´t save the connections to the Google Market, so I had to reinstall my apps all over again. Is Titanium better in this regard? My Backup Pro claims to make better backups for rooted phones, but this was pretty feeble.
So that will be my question for this forum - should I change to Titanium? Will it get all my apps, settings, and data back into my preferred configuration?
Have a great day......
I am in same boat as you are. I buy i just installed rom with Rom manager and i have Gapps fixer and remix one left and CWM ofcourse. So my problem is i don't have Ex-sd as they suggest to Install "Cwm.zip from external sd card from recovery". How to do so ?
Please help
Thanks in advance
EDIT: Never mind I sort it out Yesterday. I installed from Rom manager & Flash recovery from it and then boot up into recovery from App and then Flash Touch Recovery.
Late last week I tried flashing a new rom onto my CDMA (Verizon) Galaxy Nexus. I've done it before (I am using AOKP), however I tried a few new things and now my phone is stuck in the state it was in before this all started.
What I am on: Galaxy Nexus (CDMA, Verizon), AOKP build 28, franco Kernel
What I wanted: AOKP build 31 OR CM9 alpha nightly (for this device). I tried CM9 first.
What I did NEW: Installed ROM Manager, Flashed Clockword Mod Touch, "fix permissions" in CMW touch, mounted /system after flashing my Titanium update.zip. I may have mounted /system before fixing permissions.
What happened? The startup logo changed from the AOKP one to the CM9 one, but when the system booted up everything was exactly the same as before. This is the state I am talking about. No matter what I do it always reverts to this exact state upon reboot. I can install new apps, take pictures, etc. and it will revert to this upon reboot with all the apps, pics, etc. gone as if it never happened. The phone also reboots randomly. I also can't delete anything off of the sdcard partition. I've gotten messages saying /system is read only, and I think /sdcard has become read-only as well.
What I've tried to fix this so far:
Via the Galaxy Nexus Toolkit for Windows AND adb/fastboot:
Flashing the old CWM (no errors, but doesn't work)
Restoring an old nandroid (no errors, but doesn't work)
Flashing the stock rom for the Verizon Galaxy Nexus, released by google (no errors, but doesn't work)
Fixing permissions via CWM (no errors, but doesn't work)
Via Odin I also tried flashing the 4.0.2 stock rom. I got no errors (it said successful), but it didn't work. I am still stuck with the same exact state when I reboot.
I'm at my wit's end here.
Did you try a full wipe before the new installation?
JonSchimmy said:
Did you try a full wipe before the new installation?
Click to expand...
Click to collapse
I'm not sure. It's been a couple of weeks ago. I want to say I did, but it's entirely possible that I didn't.
Hi Newby here!
Samsung Galaxy 7 GT-P1000
I somehow stumbled my through rooting my stock tab using odin. failed to install a few Roms for Jellybean, but eventually manager to get AOKP build 38 (android 4.04) running. Like an idiot though, the Gapps file was a newer one intended for Jellybean Rom. It went on, however I now get the 'Unfortunately, Andoid Keyboard has stopped' message. I have looked around and tried the force stop and clear cache, but sadly no fix.
what do I do now? can I just install a more recent ROM over the top?
can i install a rom thats not AOKP now I have AOKP on there?
I basically want Jellybean on my tab rather than ICS.
Can you provide me a link to the Rom and relevant Gapps Jellybean, and is it the just the same process as the initial ones I put on?
OR, can I just put an older version of Gapps on and it will resolve my issue. (I want jellybean but can live with ICS if working properly)?
Sorry for the volume of questions... I am just at a loss of what to do as I dont know what I can and cant do.
For the record I dont have Nandroid or bootstrap on here. they were not mentioned in the tutorial and I had already cleared everything off my tab so wasnt worried about losing anything on it.
Thanks in advance for any enlightenment...
As I sit here now I managed to resolve both issues. I just managed to locate and flash the correct Gapps. reset/wipe, del cache, delete dalvik cache, run akop and run replaced Gapps and hey presto.. ICS running smoothly on my GT7 P1000. Runs snapseed, chrome browser just fine. All my social apps are far better in pics than gingerbread. Loving it. Many hours lost on the steep learning curve.
One question remains.. can I flash a from on here by a different mod? Cost I have seen jellybean for the P1000. Don't know whether to quit while I'm ahead, or now I'm getting the gist, mod to paranoid androids jellybean.
I am having a really weird issue I'm hoping someone can help me out with. I was on 4.1.2 Clean ROM which was working great. I wanted to move to 4.3 Clean ROM (8.1 Core Edition). I did the upgrade and then flashed my modem to ML1 both via TWRP.
The ROM setup fine and ran great. However the first time I did a reboot, the phone gets stuck at the Samsung Galaxy S3 logo and never goes anywhere. I left it sit there for 30 minutes and it was hard locked. Only a battery pull would reset it. Through numerous reboots/pulls, the same thing would happen. I tried wiping Dalvik and Cache in TWRP and fixing permissions, to no avail. Reinstalling Clean ROM 8.1 via TWRP without formatting data did not fix the issue either. The only way to get my phone back up and running was a complete wipe and reinstalling from scratch. Then as soon as I reboot the first time, the issue comes back. I've tested this on a clean install - letting the phone go through the initial setup process but not installing or updating any apps - and it still happens.
So I moved on to try AllianceROM build 22, also a 4.3 build and wiped to do a clean install. No matter what options I choose in the setup, the same problem happens. Interestingly in AllianceROM I always get a acore process has failed error on the first boot.
Then I went to download the Knox-free rooted version of stock 4.3 available from Scott's website. I have the same issue with this. Also a wipe with clean install.
It's obvious there is something my phone doesn't like about moving from 4.1.2 to 4.3. In total, I have probably installed three different ROM's about 20 times now after the past couple days.
I've searched about this problem extensively and the only thing I found is a thread for the AT&T S3 that talks about this exact issue, and using Odin to go to stock 4.3 and loading a custom ROM to fix the issue. But I am under the impression that a 100% stock 4.3 will lock my bootloader.
What I plan to do next is use Odin to flash a stock 4.1.2, then go through the process of moving to a custom 4.3 ROM again.
If anyone knows of a tar'd version of 4.3 that won't lock my bootloader, I would be grateful!
If anyone knows of a different way to fix my problem, I would be grateful for that too!
Well I think I can declare victory. My phone is running Clean Rom 8.1 CE and has survived a reboot after every app install for a total of 15 so far.
As it turns out, I think being on TWRP 2.5 and trying to upgrade to Android 4.3 was the issue. Before I went the route of flashing a stock 4.1.2 release, I thought to check if my version of TWRP was the latest, and it was not. I flashed TWRP 2.7, and did a complete wipe and clean install of Clean Rom 8.1 CE, and it's running like a champ.
I know, I know...the install guide on most every ROM says to use the latest version of your recovery - until now I thought that was a "recommendation" or "best practice" and not a hard requirement. Turns out, at least for me, that it is very much a hard requirement. In reading the release notes for TWRP 2.6 and 2.7, they both appear to implement things specifically for Android 4.3 or 4.4.
Hopefully this info helps someone who may be having the same issue.