I rooted my samsung fascinate and falshed a CM7 stable, i loved it except for the fact that my GPS wasn't working. So after some reading and research, i learned that i would have to CWM recovery, flash back to stock, get a gps lock, and then restore back to CM7 and i would have a lock.
Few things went wrong, in my original rooting, i somehow managed to wipe data/cache, thus wiping the stock rom from the phone before i could make a recovery of the rooted stock rom. So when i went back to stock with Odin, i had to completely go back to stock (recovery, stock froyo, stock kernel, etc.) Even at completely stock i still couldn't get GPS lock, even though i could get gps lock before initial root, does anyone know why? I thought it was just Cyanogenmod but i flashed MIUI and still couldn't get lock, yet i was able to get a lock with out root.
after not being able to get a lock, i still needed to get back to my recovery that i made of CM7, problem is i'm not sure which version of CWM recovery i used in order to make the recovery, i'm almost certain that it was the recovery that came with the older rom manager version in the CM7 build i used, but i've tried multiple CWM recoveries and none of which is able to read the recovery files correctly and the recovery can't be fully restored. is there anyway to see exactly which version of CWM was used in order to create the dated backup files on my SD card? Or do i just have to keep trying different versions until one works? I've tried the latest CWM from ROM Manager for the fascinate, but unfortunately the latest version is still unable to read the recovery files
any help is appreciated. cheers.
...You dont have to root to flash a custom rom. That being said there is a guide in the general section that explains how to do things properly.
Related
Im sorry if this has been covered, ive spent the last 2 days reading the Vibrant bible thread and also over on Cyanogen site and Android spin and im really frustrated with how often my device soft bricks.
i have 5 roms on my internal SD card and Rom manager running. i was able to use the option to install form SD card no problem for 4 roms and the 5th one was one called Hybrid R4 and when it rebooted into the clockwork recovery and performed the format and update then it rebooted into the Vibrant logo for 5 min. i removed the battery and rebooted so many times and same thing.
this is the 3rd time this has happened and its so annoying even more so because i know i have a good ROM on the internal SD card i can load up again but i cant get to it because i cant get into clockwork because i keep getting the stock samsung recovery screen with limited options resulting in having to use ODIN to flash the stock firmware and start over.
when i had my Mytouch i had a permanent recovery flashed to the device so i neve rhad to do this. are the Vibrants not able to have a alternate recovery console flashed to it?
which rom are you flashing over? It sounds like you are going from a 2.2 froyo rom. Hybrid R4 is from the time before the Devs started including Kernels with their roms. If you want to flash a 2.1 rom thats doesn't include the kernel over a 2.2 rom you need to flash a 2.1 kernel first. Search the bible for kingklicks kernel or Justanothercrowds kernels. Good luck.
Edit: also when you flash clockworkmod recovery in rom manager, it places a special update.zip in your root directory. leave it there. when you soft brick all you need to do in the samsung stock recovery is reinstall packages (sometimes needs to be done twice) and it will load clockworkmod recovery.
and they can have clockwork permanently flashed but it sometimes causes other problems. Eugene373 has a few kernels for 2.2 that have it permanently flashed, but it caused me issues when trying to flash another rom over it where i had no recovery at all, not even samsungs.
i was on comrom 2.1, went into cwm wiped data, cache, factory reset, then restored my stock verizon rom. my reason for doing so, is so that i can sell the phone with it looking as stock as possible without actually getting rid of cwm. so it works fine except for one issue, the custom boot screen (it just says android , except that it is messed up and instead of showing horizontally, it flashes vertically) that was on com rom is somehow stuck flashing over the stock boot screens (samsung galaxy s and the verizon logo), is there an easy fix for this? or should i return everything completely to stock?
Thanks for any help!!
You may have a problem if you were on a voodoo setup and just flashed the stock rom with out removing the lag fix...?
My suggestion is to odin dl09 with the atlas 2.2pit file and repartition checked and reboot when its done,
Then ota update to the one you want.
at this point you can power down and odin the recovery you want but you have to have a non stock kernel ready to go on your sd cause if you don't flash one the first time your in recovery, the stock kernel will overwrite it on boot. In the dev stickies there is a list of roms...you can find a non stock, non voodoo kernel to work with stock rom, flash that on there the first time you boot into recovery to make sure cwm sticks.
Sent from my SCH-I500 using XDA App
I've been running Gingeritis for ages and decided to upgrade. My first choice was CM7, so I download it, throw it on my SD Card, boot into recovery, wipe everything then attempt to flash. I get no error message but when I go to reboot it stays locked on the HTC screen.
I've updated to the newest radio and am now running, or at least I think it flashed correctly, IMOSEYON (AOSP) leanKernel.
I've tried other ROMS and my phone won't take anything, it just stays on the HTC screen after giving me no errors during flashing.
Any help? I'm pulling my hair out over here.
Attempted a factory reset and wiped everything on the phone and nothing. It won't boot at all and there's nothing I can recover to now. Wonderful, am I screwed now?
Do u have a backup you can revert back to?
Not anymore. I cleared everything hoping to go back to stock, I think all I have left is a blank slate.
Update your recovery version.
How would I go about doing that?
What recovery are you using now? Then I will search for your latest version. The recovery can be in a PG05IMG.zip. Installation is the same as when you flashed the updated radios.
I'm on clockwork recovery, could that really be the problem not allowing it to fully flash the ROM?
Also, when I'm in recovery and trying to install these new ROMS they "finish" in less than 20 seconds...I know that's not normal.
OK. Thank you for letting me know your recovery. Latest version of clockwork is 5.0.2.1
ClockworkMod Recovery flashable from bootloader - xda-developers http://bit.ly/w0BGFZ
This is my first time posting.
I am a noob, but I am trying to get beyond that. I have flashed kernels and ROMS to my GT-I9100, with success. The other day, I was going to flash a new ROM, and I tried to make a Clockworkmod backup of my current ROM...while the phone was charging. Is this a major blunder?
The reason that I ask is that CWM crashed in the middle of the backup, and now I can't enter CWM recovery and the phone doesn't boot properly. I just get stuck in a bootloop. I can get into download mode. I used Pistachio's post about how to fix a soft-bricked GS2 to flash back to stock thru Odin. Then I used CF-ROOT to re-root the phone. After that, everything works fine, and I can get to Android recovery mode. Then when I try to flash a ROM, Titanium Backup must be restoring the previous version of ROM Manager, and I get stuck in the same bootloop when trying to get into CWM recovery.
Is Clockworkmod corrupted? Did the recovery partition get corrupted? Should I flash back to stock, delete ROM Manager, then re-install it? Should I bite the bullet and delete my Titanium Backup folder, then re-install everything from scratch? Should I flash back to stock with Pistachio's .PIT file and tick RE-PARTITION?
I looked for an answer specific to this problem, and cannot find the exact same scenario in any other threads. There are similar problems, but I think that I have a CWM app or recovery partition problem, or I may have a NAND rw corruption. I don't think that it is a NAND rw corruption though, because I can flash different kernels and ROMs.
I have been using Resurrection Remix versions 2.2, 2.4.1, and 2.5.3.
I have been using Siyah 3.3.2 kernel.
Please help, and excuse my noobness if I am beating a dead horse with this question.
Sounds like Rom Manager borked CWM/CWRecovery, which it seems to do on SGS2 quite a lot.
Most of the scenario you outlined in para.3 of your post (back to stock, delete ROM Manager) sounds like a good WTG, but do not reinstall it.
If you're going to use a kernel which has CWM/CWRecovery (like Siyah), do not use Rom Manager at all. Uninstall it & keep it that way. CWM/Recovery can do pretty much everything Rom Manager can, and you're playing with fire having both on the phone. Eventually Rom Manager will bork CWM again if you use it.
In the first instance, go back to stock, re-root your phone & reinstall the rom/kernel you're wanting to use. If Rom Manager is installed by default, uninstall it before you do anything else. With a bit of luck, you shouldn't have to do anything else (like messing around with PIT's which you also mentioned in para.3). If you batch restore your apps with TI, make sure you don't restore Rom Manager.
Thanks for the speedy reply.
I will try what you have suggested, but how do I flash the .zip file from my phone without ROM Manager? Do I have to do it through Odin?
Yep, that's right. Get an Odin flashable rom from Intratech's thread (search for it on here). If links in that thread don't work, search here or Samfirmware.
Edit - And once you've got your phone back up & running the way you want, use CWRecovery to do all your flashing.
My apologies, I should have been more specific. I want to flash the RR 2.5.3.zip. Should I still download it to the PC, then flash through Odin, or can I use Android recovery to do it through the phone?
OK. Let's rewind a bit.
What state is your phone in right now ?
I am flashed back to stock, and about to use CF-ROOT.
OK. Root the phone, CWM/Recovery will be installed by default. Once the phone is rooted, reboot into CWRecovery, flash your RR zip & you should be GTG. Just remove Rom Manager if it's installed as part of that process before you do anything else (including backing up). If you're going to restore a backup, again, uninstall Rom Manager immediately after you restore.
OK, after I flash CF-ROOT, I will re-install Titanium Backup, and delete ROM Manager to be safe before proceeding. Then I will flash the ROM.zip and test CW recovery and reboot again. I will reply after doing so.
Thanks
ARRRGH!
After flashing CF-ROOT I cannot get to the splash screen upon reboot. I made sure that I ticked USB debugging before flashing the kernel. I can still get into download mode and CWRecovery, so I flashed back to stock, and tried again to no avail. I tried flashing the RR 2.5.3.zip, in CWRecovery, and it flashed. I get to the splash screen but no further. I feel like a terrible noob now, because yesterday I had the phone flashed to stock and rooted no problem. Is there something that I am missing? I made sure that I used the proper CF-ROOT kernel.
So you're getting bootloop when you flash RR ? Have you tried booting into recovery & doing a wipe/factory reset ?
I believe that I am fixed.
I restored a Nandroid backup of my stock ICS from right after my original rooting, and the phone booted fine. I did a wipe/factory reset and wiped cache. Then I flashed RR 2.5.3. The phone rebooted fine again. I IMMEDIATELY uninstalled ROM Manager and made sure it was out of Titanium Backup as well. I have rebooted several times, normal, download, and CWRecovery, and everything works as it should. I think that I am getting over my noobness.
I WILL NEVER INSTALL ROM MANAGER AGAIN...DOWN WITH ROM MANAGER!!!!!!!!!!!!!! Except for the Little Alex icon, that's still pretty cool.
A thousand thanks for your help. At least I was on the right track when I first asked for help. I was pretty sure it was a problem with ROM Manager, because when it crashed, it started this whole mess. I'll be sure to press the THANKS button for your help, and I'm going to thank Pistachio for his thread as well.
Not n00bness, stuff happens sometimes ;-) You weren't the first person to get tripped up by Rom Manager (I did not long after I got my phone), and you won't be the last.
Yep you had a fair idea of what might have caused it, and your detailed OP certainly made it a lot easier to work out WTF was causing the problems.
No probs. Glad you got it sorted ;-)
I installed TWRP on my phone, and went into Bootloader an hit RECOVERY so I can get to the program (the first time I did this it brought me to the TMRWP program). THIS time, it completely wiped my friggin' phone... after I sat there like 4 hours re-setting up everything PERFECTLY how I wanted it.
What's weird is it kept ALL my apps that I converted to SYSTEM APPS, but all my user stuff is gone.
Lesson learned... Don't click recovery from Bootloader.
That has yet to happen to me with any recovery and 3 devices currently with twrp. Might be a step missed with the install or maybe you left a bootloader update zip and ran it when you rebooted? Or it can be a bug as going to recovery from bootloader via a cold start is how to get there traditionally. I would email teamwin and try to sort it out or redo the recovery install, making sure to check the md5 of the file after you download it.
Sent from my Transformer TF101 using Tapatalk 2
Your supposed to click recovery at bootloader. Thats where you do backup, restore and flash new roms.
HTC Sensation z710e
ICS 4.0.3
Sense version 4.0
Software Sense-o-maniac v1.3
Kernel. 3.0.30 Bricked
Radio 11.68.3504
That's what I thought too. If I'm not mistaking, I flashed the new firmware after I did the TWRP, so maybe that screwed it up somehow. I take it TWRP must be the LAST image you flash? Only flashes I remember doing were:
Customize bootloader screen
TWRP.
firmware update
Do I need to re-flash the new firmware before re-flashing TWRP, or is the firmware going to remain no matter what I do from this point on?
Just adb flash recovery. Put the recovery image in your platform tools folder. Adb reboot bootloader. when you are rebooted adb flash recovery recovery.img.
Or use one of the many tools made to do that on our forums
Sent from my ADR6425LVW using xda premium
Well I went ahead and used the GOO Manager to flash TWRP again, and this time it worked fine. I'm going to re-setup my phone again then before I customize it back like I had it, going to try to get to recovery and see if it works.
With it now being installed, does that mean I can't flash anything directly from SD Card or modify the bootloader anymore without it causing problems?
What I mean, moreso, is... if I ever put factory reset. will it reload the factory rom + keep the newest firmware I installed (etc.) or do I nee to back up the phone with TWRP and recover from that when I want to load it back?
Factory reset just puts things back to the way they were without the stuff in the data partition or any user apps or settings. This means that say you flash a custom rom, it will reset to as if that custom rom was freshly installed since the custom rom has replaced the factory rom in the /system/ parition and anything else related to it.
With that said it is usually a good practice after rooting a fresh device to do the nandroid and then transfer it to a computer before you do anything else. Note that while you probably won't be switching recoveries a lot, that nandroid backups generally work only with the recovery that generated them so don't get them mixed up.