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.
Related
Hey fellows.
So I wanted to try a custom ROM for my SNS, so I rooted it with this guide: http://www.youtube.com/watch?v=xwe4sWH67dk
And since I'm completly green in all this root thing, I didnt manage to get a custom ROM on my device. So I just stayed with stock android and a launcher, and to be fair, I dont need any more than that.
Then the 2.3.6 OTA update came and I wanted to install that, so I hit "Install" and my phone rebooted. Come to the Google logo with the padlock on the button... and frooze (have to remove battery to restart my phone). Nothing I have done can help it, I tryed factory reset, nothing (get stuck on the same screen again)!
So I looked around the SNS topics in here, and frankly, I can't fix it! I read that locking the bootloader would probably help it. So I installed drivers for my device on my computer, and tryed to use this guide http://forum.xda-developers.com/showthread.php?t=875630 since it seemed fairly easy. But I cant make it work.
My phone version number is GRJ22 and my phone lock state is unlocked.
WHAT DO I DO? Remember, I'm completly green, so cut it into small pieces would be nice!
Hope that there is some helpfull sole out there that can help
arNooold said:
Hey fellows.
So I wanted to try a custom ROM for my SNS, so I rooted it with this guide: http://www.youtube.com/watch?v=xwe4sWH67dk
And since I'm completly green in all this root thing, I didnt manage to get a custom ROM on my device. So I just stayed with stock android and a launcher, and to be fair, I dont need any more than that.
Then the 2.3.6 OTA update came and I wanted to install that, so I hit "Install" and my phone rebooted. Come to the Google logo with the padlock on the button... and frooze (have to remove battery to restart my phone). Nothing I have done can help it, I tryed factory reset, nothing (get stuck on the same screen again)!
So I looked around the SNS topics in here, and frankly, I can't fix it! I read that locking the bootloader would probably help it. So I installed drivers for my device on my computer, and tryed to use this guide http://forum.xda-developers.com/showthread.php?t=875630 since it seemed fairly easy. But I cant make it work.
My phone version number is GRJ22 and my phone lock state is unlocked.
WHAT DO I DO? Remember, I'm completly green, so cut it into small pieces would be nice!
Hope that there is some helpfull sole out there that can help
Click to expand...
Click to collapse
I had a similar issue some time ago and I think I can help you. In my case, I had removed some system apps. I removed books and talk, and it couldn't update because the recovery didn't find these apps to update them. Also, if you don't have the stock recovery, but clockwork instead I think it will not work. You can find in the General section of this Nexus S forum links with the official updates zips. Download one of these and then flash it in recovery(stock or clockwork). Copy the zip to the USB storage and in recovery select 'flash update from usb storage' and select the downloaded zip. Personally, I downloaded the GRJ22 and flashed it, so I can have a clean and upgradeable GRJ22. Then I updated using the incorporated update tool from google OTA to GRK39F. It is better to do a factory reset before you flash the zip with the rom. Sorry for the messy explanation hope this helps. GL
Hmm, I downloaded the GRJ22 fitting me device from http://forum.xda-developers.com/showthread.php?t=1063664, placed it on the SDcard and tryed to go to recovery in fastboot, then the same thing happend again :/ (If that was what you meant)
I installed ClockworkMod Recovery through ROM Manager, then I installed the downloaded file on my device. Now I'm running 2.3.6 :O Thanks for the help dude!
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.
Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.
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?
Okay I've got this weird problem since updated to awesome recovery/kernel. Whenever there is CM/Omni involved, my phone starts acting weird. Okay, listen to this.
First of all, everything seems normal after clean install. Then I install some of urgent apps (total commander, whatsapp - that's all). After a day or two my phone starts to act weird - it's rebooting itself and bootloops. I turn it off and on again - boots to os, then after a few minutes another reboot into bootloop. Okay... I thought it was because I didn't have the ext4 partition. Formatted into ext4 from recovery, installed Omniroom from 2 sept. and suprisingly it went good for two days! I installed some more apps and used it regularly - but it happend again. Reboot, bootloop, manualy reboot, worked fine for a minute, another reboot into bootloop. I thought that my SD card was damaged. h2testw claimed that it was perfectly fine. Now I wanted to install some stock 2.3.5 into it... I couldn't even pass the HTC screen because it keept rebooting itself...
Tell me what can I do to make this piece of... functional again? I ordered new phone, but it will arrive within next 14 days at best, and I still need the functioning android phone. Any advice, help is appreciate: links to a flashable stock roms, links to a fucntioning omni/cm rooms, any help on how to install them... thanks in advance
mclpl said:
Okay I've got this weird problem since updated to awesome recovery/kernel. Whenever there is CM/Omni involved, my phone starts acting weird. Okay, listen to this.
First of all, everything seems normal after clean install. Then I install some of urgent apps (total commander, whatsapp - that's all). After a day or two my phone starts to act weird - it's rebooting itself and bootloops. I turn it off and on again - boots to os, then after a few minutes another reboot into bootloop. Okay... I thought it was because I didn't have the ext4 partition. Formatted into ext4 from recovery, installed Omniroom from 2 sept. and suprisingly it went good for two days! I installed some more apps and used it regularly - but it happend again. Reboot, bootloop, manualy reboot, worked fine for a minute, another reboot into bootloop. I thought that my SD card was damaged. h2testw claimed that it was perfectly fine. Now I wanted to install some stock 2.3.5 into it... I couldn't even pass the HTC screen because it keept rebooting itself...
Tell me what can I do to make this piece of... functional again? I ordered new phone, but it will arrive within next 14 days at best, and I still need the functioning android phone. Any advice, help is appreciate: links to a flashable stock roms, links to a fucntioning omni/cm rooms, any help on how to install them... thanks in advance
Click to expand...
Click to collapse
if you want to install older roms or stock you`ll need to fastboot an older recovery check this out http://forum.xda-developers.com/showthread.php?t=1415223 you only need to do PART 3 : Add a Recovery section
now you should be able to flash non-aw3som3 roms cm10 RC2 and below/ICS/Jellybean/Stock jaggyjags roms either way will get a functioning phone back for you, remember to wipe everything apart from sdcard once in recovery then install whichever rom