OK, it goes without saying that to do rooting and flashing you need to have at least a basic understanding of the English language, a decent IQ and the ability to follow basic instructions.
However, with the CWM mod that's out there for this phone, there are dangers in trying to use for anything other than flashing. IMO, the problem is that those discussions are getting buried in long threads that were originally meant for other Subjects. I feel that CWM needs to have a thread of its on to benefit EVERYONE, especially the newbies. So I am starting it off with this simple instruction:
DO NOT TRY TO USE A ROM MANAGER AT THIS TIME! THE DEVS WILL LET YOU KNOW WHEN YOU CAN USE IT
ALSO; DO NOT USE CWM TO RESTORE AT THIS TIME YOU WILL BE BRICKED
#2 IF YOU WANT TO GET INTO CWM FROM START-UP TO FLASH A ROM - HOLD DOWN THE VOL UP BUTTON + HOME BUTTON + POWER BUTTON, WHEN YOU SEE THE SAMSUNG LOGO, RELEASE THE POWER BUTTON.
TO END THE CONSTANT QUESTIONS ABOUT THE "GO BACK" MENU OPTION: SCROLL COMPLETELY THROUGH ALL MENU OPTIONS TWICE, THE GO BACK OPEN WILL THEN APPEAR
I ask the devs to post info. here even if it has been posted in one of the threads.
Forum Management FTW!
If one of the devs could throw up the file to flash CWM and the instructions, that might be helfpful as well.
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
boostedjti said:
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
Click to expand...
Click to collapse
So nandroids are not working, Sorry I dont have my Charge yet so I am only trying to get cleaification?
kejar31 said:
So nandroids are not working, Sorry I dont have my Charge yet so I am only trying to get cleaification?
Click to expand...
Click to collapse
AfaIk thats correct. No one has reported a successful restore. People who have tried end up in stock recovery loop. Hopefully someone will come up with a solution for these folks soon.
hoppermi said:
AfaIk thats correct. No one has reported a successful restore. People who have tried end up in stock recovery loop. Hopefully someone will come up with a solution for these folks soon.
Click to expand...
Click to collapse
Huh?? So if you try a recovery it bricks your phone???? or are you still able to get into recovery and reinstall a ROM?
If your are unable to get into recovery can you at least restore and Odin?
kejar31 said:
Huh?? So if you try a recovery it bricks your phone???? or are you still able to get into recovery and reinstall a ROM?
If your are unable to get into recovery can you at least restore and Odin?
Click to expand...
Click to collapse
Not sure an odin restore is helping people.
I have a theory on a way to fix a stock recovery bootloop but that would require a bootlooped device which I'm not willing to do...
boostedjti said:
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
Click to expand...
Click to collapse
I have found pressing the vol up and vol down at the same time enables the "go back" option. It will state that it is enabled.
It will pop up when you select another option first.
Sent from my voodoo Droid Charge ED2
On the Fascinate when you flashed CWM, Stock recovery would come up the first boot, then you would flash an update.zip that took you to CWM and you could flash a compatible kernel and you were on your way no more stock recovery. I don't know if something like this could work to get ppl unlooped or not, just throwing it out there.
And ShotgunSam you might as well add don't restore w/ CWM in your big red warning.
boostedjti said:
Not sure an odin restore is helping people.
I have a theory on a way to fix a stock recovery bootloop but that would require a bootlooped device which I'm not willing to do...
Click to expand...
Click to collapse
Well, I'm already stuck there, if your idea isn't too complex, I can try it out
I have one that was bricked for this reason. If anyone has any ideas I will test them out. I am good with adb shell and have been trying to figure out how to change the bootmode=7 which I think is the sdcard to 6 which I think is the nand. Can't find where the file is in the system because I can't boot. Or a signed update zip that boots Android of the sdcard like the hd2 might work.
stranula said:
Well, I'm already stuck there, if your idea isn't too complex, I can try it out
Click to expand...
Click to collapse
Go to the epic 4g forums and in development you'll find a thread that contains an update.zip that will use cwm 3.0.2.x. adb push that update to your sd card or just transfer it. Flash jts cwm compatible kernel through odin then try applying the update.zip.
Just a theory. If cwm boots, you can then flash a rom and that may work.
hoppermi said:
On the Fascinate when you flashed CWM, Stock recovery would come up the first boot, then you would flash an update.zip that took you to CWM and you could flash a compatible kernel and you were on your way no more stock recovery. I don't know if something like this could work to get ppl unlooped or not, just throwing it out there.
Click to expand...
Click to collapse
That was something I mentioned on irc the other day lol great minds think alike.
Has anyone with bricked phones tried to reach out to Koush?
Sent from my ADR6400L using Tapatalk
kejar31 said:
Has anyone with bricked phones tried to reach out to Koush?
Click to expand...
Click to collapse
Koush has been worse than useless for the Galaxy S.
Well he does have the Charge listed as a supported device on his website.. if its bricking he might help.. so if my phone were bricked I would at least try and start with him
Sent from my ADR6400L using Tapatalk
I tweeted at him and said the problem. No response yet. Ill keep posted. Everyone should tell him
Sent from my SCH-I510 using XDA Premium App
Koush is looking into it.
Sent from my SCH-I510 using XDA Premium App
Thanks OP for this tread. I agree 100%.
1) I think some "bootloopers" have had success entering download mode when their SD card was pulled.
2) Have any brickers/bootloopers tried the JIG method to force download mode?
Google JIG:
http://forum.xda-developers.com/showthread.php?t=819551
http://www.youtube.com/watch?v=iSaeaAcJHqw
http://www.youtube.com/watch?v=GjDkShT-65Y
http://samsungjigs.blogspot.com/
http://shop.ebay.com/skisky1/m.html
3) Also, I *think* someone who had bootloops was able to clear his data/cache folder somehow/someway. And I *think* he was either able to stop the bootloops or at least get into download mode. But maybe I am thinking of something else here.
Would empty cache/dbdata/movinand.bin files be helpful for Odin? We could rip them out of one of the Fascinate Odin packages to be included with a "Restore to stock" Odin package. Based on the error I've seen of someone that tried to restore, it looks like /data is getting FUBARd and that's causing the problem, but it's not something I want to personally test since my phone is working.
Anyone having issues after a restore, please see if you have adb shell access. If so, please grab a logcat and post it here.
Sent from my SCH-I500 using XDA App
Related
I have been reading threads here and I can't find an answer to my question.
I have an ATT Captivate running ATT 2.2. I ran the super one click app and have superuser available for the apps. I have rom manager free edition but no matter what I try I cannot get it to flash the Clockworkmod Recovery. When I try to flash it I get the message that it's been succesfully downloaded but never get the succesful flash.
I've spent a big part of the day at this and can't figure out why this isn't working. ANY ideas would be appreciated.
TIA, Jeff
[email protected] said:
I have been reading threads here and I can't find an answer to my question.
I have an ATT Captivate running ATT 2.2. I ran the super one click app and have superuser available for the apps. I have rom manager free edition but no matter what I try I cannot get it to flash the Clockworkmod Recovery. When I try to flash it I get the message that it's been succesfully downloaded but never get the succesful flash.
I've spent a big part of the day at this and can't figure out why this isn't working. ANY ideas would be appreciated.
TIA, Jeff
Click to expand...
Click to collapse
It won't actually be flashed to your device. It creates an update.zip file on your internal sd card. What you have to do to get into clockwork is turn your phone off, hold down vol up+vol down+power until you see the AT&T logo show up on the screen. When you see the logo show up, release power but keep holding the volume keys. This will take you into the regular stock recovery. Once you are there, select the 'reinstall packages' option. The phone should reboot, at which point, hold down the volume keys again to get back into the stock recovery. Once it boots into stock recovery for the second time, select 'reinstall packages' again and it should put you into clockworkmod this time around.
At one time in all my trying I've been thru this as well. When I select reinstall packages I get:
E: Failed to verify whole-file signature
E: signature verification failed
Installation aborted
I really want to get away from this ATT 2.2. I waited for the ATT upgrade but since it still won't support bluetooth voice dial I'm going to go this route if I can get it to work.
Jeff
modest_mandroid said:
It won't actually be flashed to your device. It creates an update.zip file on your internal sd card. What you have to do to get into clockwork is turn your phone off, hold down vol up+vol down+power until you see the AT&T logo show up on the screen. When you see the logo show up, release power but keep holding the volume keys. This will take you into the regular stock recovery. Once you are there, select the 'reinstall packages' option. The phone should reboot, at which point, hold down the volume keys again to get back into the stock recovery. Once it boots into stock recovery for the second time, select 'reinstall packages' again and it should put you into clockworkmod this time around.
Click to expand...
Click to collapse
Beg to differ. He has 2.2. Signature verification error.
Sent from my GT-I9000 using XDA App
Recovery 3E. The fix is in the dev forum
Sent from my HTC Vision
http://forum.xda-developers.com/showthread.php?t=909213
Sent from my GT-I9000 using XDA App
Oh right, totally forgot about that. It's been forever since I've flashed stock 2.2.
You can either follow the guide here:
http://forum.xda-developers.com/showthread.php?t=909213
Or you can simply flash back to 2.1 using this and do what I said in my original post:
http://forum.xda-developers.com/showthread.php?t=751518
Pirateghost said:
Recovery 3E. The fix is in the dev forum
Sent from my HTC Vision
Click to expand...
Click to collapse
+1
I've answered the same question atleast 20 times last week.
Please look around the forum and you'll find your answers!
Thanks Pirate for taking care of this one (with so many more to come )
BWolf56 said:
+1
I've answered the same question atleast 20 times last week.
Please look around the forum and you'll find your answers!
Thanks Pirate for taking care of this one (with so many more to come )
Click to expand...
Click to collapse
bets on number of posts this week regarding this same issue?
Good place for this question would be q&a, next time post there or search first.
Sent from a super smooth captivate running andromeda
Pirateghost said:
bets on number of posts this week regarding this same issue?
Click to expand...
Click to collapse
I got $5 on 7, what kind of odds am I looking at?
studacris said:
I got $5 on 7, what kind of odds am I looking at?
Click to expand...
Click to collapse
I got her under, what's the spread?
Sent from a super smooth captivate running andromeda
studacris said:
I got $5 on 7, what kind of odds am I looking at?
Click to expand...
Click to collapse
lolol
I say 11!
Wouldnt it just be easier to load a kernal tar file in odin? I know that may noy be recommended for noobs but im willing the help out walking someone through steps,if you havent already figured it out
Sent from my GT-I9000 using XDA Premium App
brd912 said:
Wouldnt it just be easier to load a kernal tar file in odin? I know that may noy be recommended for noobs but im willing the help out walking someone through steps,if you havent already figured it out
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
It is a way to do it but Odin can easely brick a phone if not used right.
It's alot easier to just prompt the command (.bat) from our computer with our phone plugged in debugging mode and let it do its magic. Takes a few seconds and it's done
There have been many people wondering whether or not the version of clockworkmod recovery will be compatible with certain roms. Clockworkmod has no affect on the ROM whatsoever so you can be on 5.0.2.7, touch recovery 5.5.0.4, touch recovery 5.8.1.3, etc. and you can install any rom from within those recoveries. It makes absolutely no difference what recovery you are on. Every recovery above CWM 3.0 uses edify scripting (which is what is needed for all roms above android 2.0). So if anyone tells you that you need a certain recovery to flash ICS or GB they are wrong. All Clockworkmods are compatible with ALL ROMS.
I concur. Ive tried all 3 and ive had no issues. I think some folks state to use certain ones because thats what they used and they didnt have any problems, so they keep telling everyone to do what they did.
As with any Rom load, all issues arise or dont arise based on how well you cleaned the slate before applying the ROM.
Dixit
Good to hear this re-affirmed. I am having problems flashing .zip's in CWM and know for sure it's not the version!
randomtask16 said:
Good to hear this re-affirmed. I am having problems flashing .zip's in CWM and know for sure it's not the version!
Click to expand...
Click to collapse
what issues are you having? right away the first thing i would try is downloading the rom again as you may have had a corrupted download.
From personal experience I have had a ton of issues before I ODINd the 5.5.0.4 recovery. Prior to that I was running the 5.8.1.3 and I was having a ton of issues flashing some of the roms. I don't have any proof of errors or anything but I'm certain that Appdroid will be willing to vouch for me right now.
~PsyCl0ne
I've tried them all without any major issues except for one. Flashing ROMS is one thing but the overall functioning of all the tools within seem to differ. Permissions for example work on some and not on others. They do differ overall but I agree flashing a ROM isn't an issue. Everyone has their preference and if a developer says to use a particular version, there is a reason. I'll ask you since your the expert, do the wipes and cache clears work the same way?
Sent from my SAMSUNG-SGH-I727 using xda premium
Maybe someone can tell me what's wrong with my setup, I'm on Superlite 5.0 with ROM Mgr v5.0.0.6. I can only boot into CWM (Touch 5.8.1.3) from ROM mgr and nothing else. It's not a major deal but I can't go directly to backup, restore e.g. like I used to with a GB rom.
bdbx18 said:
Maybe someone can tell me what's wrong with my setup, I'm on Superlite 5.0 with ROM Mgr v5.0.0.6. I can only boot into CWM (Touch 5.8.1.3) from ROM mgr and nothing else. It's not a major deal but I can't go directly to backup, restore e.g. like I used to with a GB rom.
Click to expand...
Click to collapse
I dont use Rom Manager, you wont find alot that use it for those functions either as its essentially passes that request off to CWM when its rebooted. So Id suggest just rebooting to recovery using the toggle panel in Superlite, then in the CWM touch, just backup, restore, do anything.
Dixit
bdbx18 said:
Maybe someone can tell me what's wrong with my setup, I'm on Superlite 5.0 with ROM Mgr v5.0.0.6. I can only boot into CWM (Touch 5.8.1.3) from ROM mgr and nothing else. It's not a major deal but I can't go directly to backup, restore e.g. like I used to with a GB rom.
Click to expand...
Click to collapse
Are you saying that if you power down and use the three-button combo it doesn't work? (ie volume up+volume down+power)
If this is the case you may want to try using Odin to flash recovery again (found in the Fix Soft Brick or in the rooting thread...)
skrambled said:
Are you saying that if you power down and use the three-button combo it doesn't work? (ie volume up+volume down+power)
If this is the case you may want to try using Odin to flash recovery again (found in the Fix Soft Brick or in the rooting thread...)
Click to expand...
Click to collapse
For my phone I don't have to hold power when booting up. I just hold both volume buttons till I see the recovery menu.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA
PsyCl0ne said:
For my phone I don't have to hold power when booting up. I just hold both volume buttons till I see the recovery menu.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
This is exactly how I get into recovery on my AT&T phone. Holding three buttons just causes it to reboot over and over again
skrambled said:
Are you saying that if you power down and use the three-button combo it doesn't work? (ie volume up+volume down+power)
If this is the case you may want to try using Odin to flash recovery again (found in the Fix Soft Brick or in the rooting thread...)
Click to expand...
Click to collapse
What I meant is that I used to do for e.g. 'Backup current rom' from ROM mgr, name it accordingly, and it will reboot into CWM and backup with that name. Now it just reboots to CWM main panel and sits there. Even the timestamp on the backup file is off.
PsyCl0ne said:
For my phone I don't have to hold power when booting up. I just hold both volume buttons till I see the recovery menu.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Oh yes, you're on rogers. I thought rogers users had to hold volume down only+power button to get into recovery (ie no volume up key involved). I've seen many rogers users say that...
---------- Post added at 10:20 PM ---------- Previous post was at 10:15 PM ----------
bdbx18 said:
What I meant is that I used to do for e.g. 'Backup current rom' from ROM mgr, name it accordingly, and it will reboot into CWM and backup with that name. Now it just reboots to CWM main panel and sits there. Even the timestamp on the backup file is off.
Click to expand...
Click to collapse
Oh! Now I get it. I have had weird issues with ROM Manager ever since I had this phone. Backup via ROM Manager worked a couple times on gb roms but then it started doing what you described. Ever since it started doing that I just backup from cwm, and then go back in with Root Explorer to re-name the files so I know what's what...
Can't you just boot straight to recovery from most roms as well as from rom manager if you were on a rom that didn't have that ability? I can't remember the last time I had to press buttons to get into recovery, I'm not saying it's not useful to know, but merely stating that it's highly unnecessary in most cases to ever have to touch the buttons for recovery.
sk8erwitskil said:
There have been many people wondering whether or not the version of clockworkmod recovery will be compatible with certain roms. Clockworkmod has no affect on the ROM whatsoever so you can be on 5.0.2.7, touch recovery 5.5.0.4, touch recovery 5.8.1.3, etc. and you can install any rom from within those recoveries. It makes absolutely no difference what recovery you are on. Every recovery above CWM 3.0 uses edify scripting (which is what is needed for all roms above android 2.0). So if anyone tells you that you need a certain recovery to flash ICS or GB they are wrong. All Clockworkmods are compatible with ALL ROMS.
Click to expand...
Click to collapse
You are absolutely correct. That is why I have not required any specific recovery, but told people what I use. yours . But, there is a caveat, since flashing a full rom requires reliable wipe operations from the recovery, it appears to be a hit or miss. That is why, I have specified the requirement that whatever recovery you use, use the recoveries built-in Format /system, /cache and /data, I am not going to do it within my update script.
BTW, thanks for the recovery, it cuts down a bunch of time trying to test, build..
Funny you say CWR makes no difference. I disagree. The kernel works different in different versions of cwr
With
Clockwork Touch aka recovery-clockwork-touch-5.8.1.3-hercules
I cant adb remount it gets stuck in Read only.
With
v 5.0.2.6 I have no issues
Flashing files in one ver the other may cause issues for some phones.. As we have seen every phone is handling the ICS flash different.
I have had better luck with the older CWR
mhx said:
Funny you say CWR makes no difference. I disagree. The kernel works different in different versions of cwr
With
Clockwork Touch aka recovery-clockwork-touch-5.8.1.3-hercules
I cant adb remount it gets stuck in Read only.
With
v 5.0.2.6 I have no issues
Flashing files in one ver the other may cause issues for some phones.. As we have seen every phone is handling the ICS flash different.
I have had better luck with the older CWR
Click to expand...
Click to collapse
Nope..read the OP again...he is talking about the linkage of ROM and recovery. They are unrelated...
mohan_kr said:
Nope..read the OP again...he is talking about the linkage of ROM and recovery. They are unrelated...
Click to expand...
Click to collapse
i beg to differ, mhx makes a valid point. The op may be true for gb, but for ics i too have noticed better flashes, and things "stuck better" with 5.0.2.6. I can't even get fix permissions to work on anything past 5.0.2.7
icenight89 said:
i beg to differ, mhx makes a valid point. The op may be true for gb, but for ics i too have noticed better flashes, and things "stuck better" with 5.0.2.6. I can't even get fix permissions to work on anything past 5.0.2.7
Click to expand...
Click to collapse
I've flashed multiple ICS roms multiple times on multiple CWM (touch and non) recoveries, and I've never had a single issue.
icenight89 said:
i beg to differ, mhx makes a valid point. The op may be true for gb, but for ics i too have noticed better flashes, and things "stuck better" with 5.0.2.6. I can't even get fix permissions to work on anything past 5.0.2.7
Click to expand...
Click to collapse
If the OP was talking about different features of a particular recovery, then yes there is point to it. He is talking about flashing a ROM with edifying scripting support for the skyrocket, which should work regardless of the version of the base android platform for our device, if of course the ROM creator has put the rights bits in the script for that particular ROM.
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
aperture said:
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
Click to expand...
Click to collapse
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
riverboat2001 said:
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
Click to expand...
Click to collapse
As long as you are using cm, I don't think it will be a problem. I will never go back to official. The problem stems from an issue with the stock recovery from Samsung. So in short, the devs are aware of the issue, but Samsung doesn't seem to care. As long as you are running the current cwm, and the dev isn't an idiot, you shouldn't have a problem. (No offense aorth and locerra, I know you're aware)
Sent from my Galaxy Tab 7 Plus
riverboat2001 said:
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
Click to expand...
Click to collapse
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
wingie6200 said:
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
Click to expand...
Click to collapse
Wow, thanks so much for taking the time to offer your advice.
I only have myself to blame for getting into this pickle! After Flashing so many different ROM's on loads of devices i just got a bit blaiz'e
Last night i did a wipe and factory reset through CWM and it all went well, so my question is, giving that i know i'm at risk, i can see three options,which is the "safest"
1/ Put tab away and don't use it until Samsung release a fix we can use
2/ Keep using the tab, but have that worrying niggle in the back of my mind
3/ Follow the post above and carry out the suggested procedure outlined above? (is it 1000% safe?
Can i assume that if i go as far as recovery mode via the ICS version to see the "recovery 3e" but don't wipe/factory reset i'm safe?
And consequently if i DON'T see that i would be safe to go ahead?
I do feel as if I'm sitting on a time-bomb here
(years ago i would have spent weeks messing around with this sort of thing, but as a middle aged housewife thats always on the go, i don't have the time, I just like to get my stuff working fast and bloatware free and i'm happy!)
Once again thanks for your input.
lol cant guarantee the 1000% safe part (since the offending code is in part coming from samsung) but people are aware of it / working to fix it and all non stock stuff is most probably safe. the CWM 6.0.1.0 definitely is, just used it myself.
and these things are kinda random (if all posts are to be believed) so i would just use the tab normally and worry about it much.. reports also say that samsung does repair these bricked tabs under warranty in case the unthinkable does happen.
and its not a time bomb :laugh:! (although there would probably be an app for that somewhere..)
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
ringnutz said:
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Kuniokun said:
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Click to expand...
Click to collapse
Yeah, I did.. happened the first time
Sent from my myTouch 4g via Tapatalk
Brickbug is caused by ****ty flashing firmware on some of our devices.
No danger with cwm 6.0.1.0 from aorth. We r safe!
Sent from my GT-P6200 using xda app-developers app
I installed paranandroid and gapps but it was the wrong gapps which caused it to error out during install. so now I have the correct gapps on my SD card but do not know how to access it through my phone since I have no recovery. How do I get gapps back on phone so I can get into recovery?
damn....
PHUCK! ok now I'm really freaking out... flashed gapps and says framework as stopped. wont let me past the front screen saying touch android to begin...
1Android said:
PHUCK! ok now I'm really freaking out... flashed gapps and says framework as stopped. wont let me past the front screen saying touch android to begin...
Click to expand...
Click to collapse
OK, don't panic yet! Basic questions first:
Did you flash a recovery like CWM (Clockworkmod) before trying to flash the rom?
Are you able to get into recovery mode via volume up+power+home?
Why dont you reflash the ROM and then do the right Gapps? That way you wont have any screwed up files at all. If you really screwed it up just Odin back to stock and start again.
just flash the rom over the top then flash the right gapps
I went into panic mode and my head went cloudy. I kept olding down volume instead of volume up. Got into recovery and just doing a restore for now till I can make sure I have all the right files...
thanks guys for answering so quickly.
1Android said:
I went into panic mode and my head went cloudy. I kept olding down volume instead of volume up. Got into recovery and just doing a restore for now till I can make sure I have all the right files...
thanks guys for answering so quickly.
Click to expand...
Click to collapse
Good, now when that's done, lets get you up and running with paranoid. It is alot easier, and generally safer to flash through CWM on the phone itself then through odin on your desktop or even the odin app. What method were you using? And more importantly did you do a IMEI backup?
Haven't done the imei backup yet. Need to though asap. I always flash through cwm but once I installed the wrong gapps (didn't even think of grabbing a JB gapps until after I got my phone into recovery and restored) I had no idea how to get into recovery. Once I found the goo manager in system settings I was able to get into recovery. Tried flashing another gapps file (which again was the wrong file) which is where I really freaked out with my framework and setup no working. Was able to clear my head and remember the volume UP not down. I'm restored now and will leave it on synergy till I do my imei backup. Haven't even looked into it to be honest. Is it difficult? Is paranandroid really much better as far as battery life to worry about taking the time to do it?
Sent from my SCH-I535 using xda app-developers app
1Android said:
Haven't done the imei backup yet. Need to though asap. I always flash through cwm but once I installed the wrong gapps (didn't even think of grabbing a JB gapps until after I got my phone into recovery and restored) I had no idea how to get into recovery. Once I found the goo manager in system settings I was able to get into recovery. Tried flashing another gapps file (which again was the wrong file) which is where I really freaked out with my framework and setup no working. Was able to clear my head and remember the volume UP not down. I'm restored now and will leave it on synergy till I do my imei backup. Haven't even looked into it to be honest. Is it difficult? Is paranandroid really much better as far as battery life to worry about taking the time to do it?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The IMEI is very easy to do, especially if your running Synergy. There are 3 methods in the link I'll attach. The first uses any terminal emulator app (free in play store) and simply typing in a code: su (enter) then: reboot nvbackup (enter)...done! Then there is the next way to create a second easier to install if something were to happen way using a Synergy recovery zip. You must do the first method first or the zip way will backup the wrong IMEI. On the link there is another link to the Synergy Key zip file (its right in the directions with HERE in bold as the link). Download zip, run it in recovery ONCE to create the backup, thats it! The synergy backup can then be used on other roms. Overall its super easy, I spent 2hrs researching and 5 min creating the backup. IT really is as simple as that, just do it in order. As far as paranoid goes, I don't have hands on with it, too many bugs for me to bother with it yet, but yes it generally should use less battery due to JB's unmatched efficiency.
Here's the link: (only need to read the first page for making the backups, read further to restore which hopefully won't be needed!)
http://forum.xda-developers.com/showthread.php?t=1852255
I will look into it tomorrow. Thank you so much for your help!! Very much appreciated.
I need/want a fully functional Rom without a bunch of bugs. Might stay with synergy till some bugs can be worked out.
Sent from my SCH-I535 using xda app-developers app
Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!
VyCariously said:
Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!
Click to expand...
Click to collapse
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.
qkster said:
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.
Click to expand...
Click to collapse
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.
VyCariously said:
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.
Click to expand...
Click to collapse
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.
That does remove root access. However, root isn't really necessary, at least for the stock ROM, if you have no intentions of staying stock. The ROM .zips you'll subsequently flash are pre-rooted. After you Heimdall back to stock, and flash it again with "flash bootloaders" selected, then use Heimdall to flash this kernel:
http://d-h.st/6KA
That'll flash both a new kernel and CWM Red recovery. It'll take a few minutes to boot up the first time, as it's installing the lagfix. Once it boots up, just shut it down and boot back up in recovery. From there, you can do whatever you need to do.
VyCariously said:
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.
Click to expand...
Click to collapse
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl
qkster said:
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse
Thanks guys
It's been a crazy busy week and I just didn't have time to deal with the phone. I've been dealing with stock gingerbread. It's getting kind of annoying, though, it seems less stable than the custom ICS that I had on it before. Not sure when I'm going to have time to play with it again and try to get it to where I want it. I think I'm going to try to totally wipe all of the old stuff out of the memory before I do it again, though. There's something that wasn't allowing me to do what you guys are telling me to do successfully. I'm also thinking of finding a GS2 and just selling the Infuse, not because of my confusion, but because the GS2 was what I was originally looking for anyway.
I'll try to get this one set up first, though, as it's just a matter of me being obsessive about it.
qkster, I'll look into the JB, too, lol.
qkster said:
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse
Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app
XperiaNeoVNoob said:
Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome
VyCariously said:
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome
Click to expand...
Click to collapse
No probs...
:thumbup:
Sent from my MT11i using xda app-developers app