First off, let me make this clear very clear(prerequisite) I do not want to hear the word "safestrap", or any variation. I apologize for sounding arrogant , but I am not interesting in wasting my disk space(no offense against the quality work of Hashcode) or dual booting a ROM. I noticed some interesting issues with CWM recovery both the default that comes with Bionic Bootstrapper(4.x.x.x), and ROM Manager(5.x.x.x) in regards to any ICS leaks. So here is the situation, after installing the .232 leak using the "stock recovery option" it went smoothly without any issues, as well as rooting with motofail for ICS. The problems start when I first attempt to install any ROM(AOKP, CM, liquidsmooth etc etc) using 4.x.x.x CWM it appears to install correctly(even booting the ROM up and everything) but when I reboot the phone will continue to boot directly into CWM, and using the reboot option only to boot loop.(I have done the standard Wipe System/Factory reset, Wipe Cache, Wipe Dalvik Cache prior to installing any ROM). Finally, when I attempt to install an updated CWM 5.x.x.x via ROM Manager, it appears to install, but forcing the device to reboot in to recovery does not work, even the two button solute(PWR+VOL UP) as used in the second stage to force CWM to boot into the menu(worked in 4.x.x.x) it is as if it is not corretly installed.. Both CWM installs are clean, and no previous 1st/2nd stage boot loaders are installed, I would like to rule out me being a dumbf*** and it being a case of error on my part. Like I said before please do not mention "SAFESTRAP" as an option, unless it can flash over current baseline install's, having the safe option(noob proof) is not an option. If anyone can assist me with the installation or even a solution to getting CWM recovery to work after installing the ICS leaks it would be greatly appreciated. Thanks again!!! Also I have tested CWM 5.x.x.x install from .905 based roms and it works flawlessly.
Related
First of all I hope this is in the right place: I did do a search but still couldn't find any help.
Here's my problem:
After getting a (delicious) taste for customisation after rooting and lagfixing, I decided to give custom ROMs a go. Hours of indecision passed and ultimately I settled on Doc and Stefunel's magical ROM. Due to currently being on 2.1, I chose to follow the set of instructions provided on the page for doing so.
All was well up until the very final step. When rebooting the phone through ClockworkMod Recovery, instead passing the Samsung boot screen into the Android system, the phone boots into CWM recovery. I've tried doing another factory reset, and reinstalling the ROM to no avail. I've also tried mounting "/mnt/sdcard" in order to place another ROM to flash from, but I keep getting a message telling me to insert a disk (what happens when you don't mount).
That's pretty much all there is to it. I'd be massively grateful for any help!
-anti
If you have made a backup of your apps then flash the JPY with Odin and then make factory reset in recovery mode. Then root with CF Root 1.3 (Or something like that) and flash CWM Recovery. That's what I would do.
Sent from my GT-I9000 using XDA App
from the recovery menu try wipe cache and dalvik, and reboot
Basically the title.
I removed the Tweaked Bootstrap.apk and just downloaded and installed Safe Strap. Rebooted and performed my first backup in Safe Strap. Tried to boot into primary and got black screen.
My current ROM is the latest (11-16) version of CM7.
I don't really need Safe Strap, I kinda just want to be able to boot again. Any help is greatly appreciated.
EDIT: Formatted /system and reflashed CM7 and GApps in SAFE MODE. Can boot now, going to try booting in NON-SAFE MODE.
EDIT2: Still can't boot into non-safe mode. My whole reason for switching was to test out ICS, so I guess I can just flash it and if I need to go back, I'll just reflash CM7.
Regardless, if anyone can tell em what I'm doing wrong, I'd be appreciative.
Did you wipe everything including dalvik? and its best if you start from a stock system. No custom ROMs. then install CWM and install whatever rom you want. uninstall CWM and install safestrap. now boot into safestrap and wipe cache and all taht. Now install ICS/CM9. I found tahts the best way to do it recieve none of the errors many people are having.
Well, since safestrap can't flash nonsafe (yet) its obvious you still can't boot nonsafe if you couldn't before. What you need to do is reflash cm7 using the old bootstrap, install safestrap, make backup, then switch to safe system and flash ics.
Hi guys. I'm quite a noob, but have a good experience on flashing without be bricked (CM9, CM10, Crash, Paranoid...), but I have a problem.
I will explain to you step-by-step what I've done with my Note, so I wish some of you could help me.
1) I was running JB Crash ROM with PhilZ kernel.
2) Some apps got Force Close too often, so I went on Rom Manager and, after a look into the "Fix permissions" description ("It will fix some force closes" or something like that), I decided to give it a try and I tapped on it.
3) After that, my homescreen became unusable, because "TouchWiz Home" got EVERY TIME force closed without reason. Everything else worked fine, so I deciced to boot into CWM recovery to restore a nandroid backup of the same ROM.
4) Instead of tapping "restore", I tapped "backup" (my fault) and it started without possibility of get back. I got something like 200 Mb of free space, so in every case it will never have had success. My Note stucked at this point, so I decided to reboot manually (vol up+home+power) into recovery. Finally I tried to "restore" but I get this message: "ERROR WHILE RESTORING /SYSTEM".
5) I tried to reboot my Note, but it stucks at "Samsung Galaxy Note GT-N7000" screen without going on.
The good news is that it can go without problems into recovery and into download mode. What can I do? Flashing from CWM, for example, CM9 can fix this?
Please help me thanks!
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
friedje said:
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
Click to expand...
Click to collapse
After formatting /system, can I try to restore my nandroid backup? Or I have to necessary reflash my ROM? In that case, it's the same thing make it via CWM or via ODIN PC? I'm still on PhilZ recovery, which is safe I guess!
Anyway, thanks for your help
Via CWM or Odin, depends if you have your rom in the zip or the md5.tar format.
I would reflash to be clean. It's a bit more work in restoring your apps and data
afterwards, but at least you don't restore any messed up files.
if you can still access CMW and Download Mode then you probably are not brick... try fresh install through pc odin.. safe method no need to worry about bricking by fullwiping on unsafe kernel or raising triagle or binary counter whatsoever.. if you wanna play safe then PC ODIN and after that you can root your rom
Thank you guys, now I'm on stock ICS flashed via PC Odin and everything works fine I knew I was 99% not-bricked (still recovery and download mode avaiable), but I was a little scared too.
Thank you again!
glad you solved it.. :good:
I wanted to flash custom rom on my galaxy S. I flashed clean rom, then kernel with CWM, but there is a problem. Everytime I try to flash rom it ends with bootloop. I tried cm7, cm10, rootbox, miui 2.4. Every time is the same. It starts installing (only few secodns), then screen becames brighter, then restart and bootloop. I tried different kernels, roms but still same result.
ps. sorry for my english
Hi, here is a great guide to fix bootloops:
http://forum.xda-developers.com/showthread.php?t=1660596
Usually, doing factory reset, wipe cache and wipe dalvik cache before and after intalling the ROM should fix the issue though.
I'm doing all necessary wipes, I can recover from bootloop easly but I want flash custom rom and I can't. Istalling zip lasts few second, not few minutes, there is a problem.
Sorry if this is too basic, but are you using the right ROM for your phone?
of course...
I don't know if I'll be able to help you, but can you please list the exact model of your phone just in case? You can see the different variants here:
http://en.wikipedia.org/wiki/Samsung_Galaxy_S#Variants
It is just GT-I9000. Now I managed to flash CM7.2 but if I want install CM9 or CM10 im getting bootloop and can't enter recovery mode ;o
Sorry, I can't really give you an answer with that information. If you are following the steps in each ROMs thread, you should have no problems patching as far as I know (someone more knowledgeable than me may say otherwise).
Maybe posting the exact steps you are following would help me or others to find out what the issue is.
I'm following right steps. It's not my first phone. I know how it should be but it isn't. Here are my steps:
Flash stock ROM w/ODIN v1.85 - OK
Flash CF-Root w/ODIN v1.85
Wipe Data/Wipe Cache
Phone now rooted OK
Boot to CWM Recovery
Install zip from sdcard
Select update on SDCard (cm-7.1.0 from CM site)
Flash completes in just a few seconds
Phone reboots automatically
Now stuck in boot loop
Remove battery
Go to CWM again and reflash CM7.1 zip
Now i have CM7
Reboot to recovery, facotry reset, wipe cache, wipe dalvik
Flash CM9/CM10, finishes in few sec, reboots, then black screen, can't go to recovery mode ;(((
Flashing stock with odin again...and every time is the same, sometimes when I choose CM10 i see info: "Incompatible Partition Layout" so it may be the reason (something with partition, idk)
My phone has never rebooted like that, so I'm not sure what the problem is. I do know I use ODIN v3.07. I also have CWM 6.0.2.7
Best of luck finding a solution, sorry I could no be of more help.
I think CWM6 would help but I can't find this version for cm7
IGNORE ALL LINKS BELOW, they are for the wrong phone
I don't think it matters what CM you have on your phone, you should be able to upgrade CWM from recovery: Maybe not in i9000...
http://forum.xda-developers.com/showthread.php?t=1843825
Doesn't work in i9000 as far as I can tell: You can also try installing TWRP, which I like better than CWM and have in a different device:
http://forum.xda-developers.com/showthread.php?t=1694617
Finally, and don't take me on this because is just a guess, maybe your bootloader is not working properly? I don't really remember how to do this myself:
You are showing me links to CMW and TWRP for i9001, I have i9000...
You are right, please ignore those links... I do know I patched CWM 6.0.2.7 through ODIN on my phone, so maybe that's the only way. In any case, I'll let you look for the actual links.
Okay so, I'm not exactly sure if this is the right place but I'll ask here anyway.
I took my old i9000 out of the closet and started playing around with it as I want to use it on my upcoming travel. To make long story short, I used to have a custom ROM on the phone all those years ago, but I am by no means an expert on the subject.
So what I have done so far today:
1. Returned the phone to stock ROM with Odin (XWJW1 or something, most recent anyway)
2. Rooted with Semaphore 2.7.4.
3. Installed Rom Manager and Superuser to check for CWM updates (which caused some sort of a verification error when I tried to boot to CWM through the app).
4. Downloaded the appopriate Slimkat and gapps and moved them into the internal storage.
But after the last step (and after wipe cache, format system etc) when I try to install the ROM, the bar on the screen progresses only slightly and after "Installing update..." it crashes (just goes black without any error messages) and gets stuck with just "Semaphore" on the screen.
I wish to update the phone to Slimkat 4.4.2. But what causes this problem, any ideas? Am I doing something wrong? If anyone can give any help that would be much appreciated!
PS. If I wanted to install for example Philz recovery, how am I supposed to do it when the file is .img?
Anyone?
I guess no one is using this phone anymore?
Yes, you are doing many things bit wrong.... (and many people use this phone still). I hope following will help you:
*recovery and kernel are sharing the same partition on the i9000 what means that you can't flash recovery separately
*make sure to backup your IMEI if still there
*flash first CM10.2 to get updated recovery for KitKat roms and to resize the system and data partitions to those used by all KitKat roms and reboot once into the system. You will need to flash trice to make it work (1. only warning of resizing to come and data lost- and status 7 abort, 2. only recovery update, 3. successful flashing)
*flash SlimKat and latest SlimGapps (addons) for 4.4.4
*PhilZ touch screen isn't yet working well on the i9000 but if you flash Mackay KK kernel, you can get beautiful TWRP touch recovery
tetakpatalked from Nexus 7 flo