Related
I switched over to cognition and noticed I didn't have any of my contacts. So then I flashed back to my old rom and the phone wouldn't boot. It stayed at the world phone screen. I can get to download mode and when I try to use odin it says check image path. I tried the reset and still no luck. Any ideas?
Ok, I reinstalled cognition and my phone is working so never mind I forgot that i had a vcard with my contacts so i just used that. But I do want to know the safe way to flash back to a rom. If you could explain the steps I would appreciate it. Thanks in advance.
Odin OneClick and Clockwork Mod Recovery are the norm.
Since this is the cognition help thread, I will post here....
I tried to install cognition 3.0 using CWM. But I keep getting error at Line 15. Do I need to install a new kernel. I don't even know what Kernel I am using so I would assume stock. If I do need a new kernel could I be directed to the proper thread.
Re-download Cognition 3.0 from Designgear's site. Something sounds fishy with your install. You should NOT have to install a new kernel. The Cognition zip package contains everything you need to flash your phone, and have it fully operational.
inc0gn3gr0 said:
Since this is the cognition help thread, I will post here....
I tried to install cognition 3.0 using CWM. But I keep getting error at Line 15. Do I need to install a new kernel. I don't even know what Kernel I am using so I would assume stock. If I do need a new kernel could I be directed to the proper thread.
Click to expand...
Click to collapse
yea worked perfect 4 me i followed there youtube vids worked like a champ only trouble i had was u need 2 dismount sd card 2 push root phone. and it doesnt cover that.
Out of sheer curiosity and wonder, I noticed after the OTA was installed, su was not working, duh, I knew that would happen, so I re rooted the device, I made a back up of the rom every single time it was updated, so I noticed when clicking "reboot into recovery" option in rom manager (keep in mind I am on 2.3.2) it boots me into stock android <3e> recovery and not CWM 3.0.x.x. Which is weird because after that I do a battery pull to jump into the bootloader to access recovery there, nope, still takes me to the damn stock recovery, so back to the bootloader and fastboot my way back. After that, I noticed once back booted in android I go into RM and "flash recovery" (3.0.x.x) and voila! I get back into CWM, but I have to flash it every single time.
Has anyone noticed this?
Feel free to hit me up on twitter since I try to stay outta forums, thank you.
I <3 Trolls.
b16a2smith said:
Out of sheer curiosity and wonder, I noticed after the OTA was installed, su was not working, duh, I knew that would happen, so I re rooted the device, I made a back up of the rom every single time it was updated, so I noticed when clicking "reboot into recovery" option in rom manager (keep in mind I am on 2.3.2) it boots me into stock android <3e> recovery and not CWM 3.0.x.x. Which is weird because after that I do a battery pull to jump into the bootloader to access recovery there, nope, still takes me to the damn stock recovery, so back to the bootloader and fastboot my way back. After that, I noticed once back booted in android I go into RM and "flash recovery" (3.0.x.x) and voila! I get back into CWM, but I have to flash it every single time.
Has anyone noticed this?
Feel free to hit me up on twitter since I try to stay outta forums, thank you.
I <3 Trolls.
Click to expand...
Click to collapse
Wow, I'm sorry to be cranky, but this is unreal.
Your question has been asked and answered a hundred times in this forum if you'd bothered to search, and you're not even willing to a monitor the forum for an answer, you want us to come search you out on Twitter?!?!?
Here's a hint to find the answer to your question, use the forum search button and search for the phrase /etc/install-recovery.sh.
You'll find dozens of posts telling you to rename that file, which Google added with the updates to overwrite any custom recoveries with the stock one on each boot of the phone... Rename the file and you won't have to flash cwm every time any more.
Okay, that last post was a bit more harsh than I meant it to be, perhaps, but I'm leaving it intact. Since you "try to stay outta forums" you probably don't know proper etiquette:
1) search before asking; your issue has most likely been asked before. It's annoying to forum regulars when people show up and ask the same thing over and over that's already been answered.
2) read the FAQ thread before asking; your issue has most likely been addressed in it. It's annoying to forum regulars when people show up and ask the same thing over and over that's already been answered in the FAQ.
3) if you're going to come to the forums and ask a question, then come back periodically and see if it's been answered. We're doing you a favor answering your question, at least show some effort by coming back and reading it instead of asking someone else to come find you in another forum and spoon feed it to you. If you're really just too important or time-challenged to do that, then subscribe to the thread you created and get an email notice when posts are made to it.[/I]
You'll need to rename install-recovery.sh to install-recovery.sh.old.
Its located in the /etc system folder. You can use root explorer or any another alternative. Refer to the rooting guides available as they include a more thorough explanation of how to do this. And please, no twitter.
Sent from my Nexus S using XDA App
it's actually enough just to fastboot push the renamed recovery.img
then it will stick without having to rename the install-recovery.sh
Hey huge thanks to @AllGamer.
The other guy, no idea what crawled up your ass and died, but didn't know that one simple question could hurt so badly. Have a nice day.
P.S. I am sure most of the people here know this, the search engine sucks on this site so yes I did use it and its garbage. I was just concerned about it so I could start my builds without any worry. Happy trolling.
Moderator delete this thread,
Thanks.
AllGamer said:
it's actually enough just to fastboot push the renamed recovery.img
then it will stick without having to rename the install-recovery.sh
Click to expand...
Click to collapse
I don't recall that working for me. I'm not even sure why that would work. Every boot up that script is ran unless you delete or rename it, isn't it? I guess I'll have to play with it when I get a chance.
EDIT: Do you mean renaming clockwork-3.0.0.5-crespo.img to just recovery.img when pushing it via fastboot? Never tried that here.
b16a2smith said:
Hey huge thanks to @AllGamer.
The other guy, no idea what crawled up your ass and died, but didn't know that one simple question could hurt so badly. Have a nice day.
Click to expand...
Click to collapse
I think it was the bit about I try to stay out of forums, so come find me on twitter coupled with the <3 trolls.
I was cranky this morning and I apologize, but it was all true, and don't forget that I did tell you how to find the answer (which search term to use) and even how to fix it (rename the file), so I think thanks are in order....You're welcome for that, and have a nice day as well..
Peace
distortedloop said:
EDIT: Do you mean renaming clockwork-3.0.0.5-crespo.img to just recovery.img when pushing it via fastboot? Never tried that here.
Click to expand...
Click to collapse
yes, it is in my guide
yet people always misses to read it
most people reading it either assumes things, or doesn't follow it properly
that's how i do it every time and it works without fail
AllGamer said:
yes, it is in my guide
yet people always misses to read it
most people reading it either assumes things, or doesn't follow it properly
that's how i do it every time and it works without fail
Click to expand...
Click to collapse
Just to be clear, we're talking about having clockwork NOT overwritten by the stock each bootup. I'm a little confused because you say "that's how i do it every time..." If it sticks, why do you need to do it more than once?
Assuming you mean clockwork sticking without renaming the install-recovery.sh file, please read on. If that's not what you meant, skip the rest below...
I don't think people necessarily miss it, they assume things like you say
I didn't follow your guide to root mine (it wasn't out yet, and isn't Mac), but obviously I've read it. I did notice that you rename it, but assumed it's not necessary, since Koush's instructions don't have you do that and you get a successful flash without renaming.
Anyways, I just tested this out on my NS.
I was on stock recovery, and I have not renamed my /etc/install-recovery.sh file.
I booted the phone to fastboot mode, renamed my clockwork recovery to recovery.img.
I then "fastboot flash recovery recovery.img" and after a successful flash message, selected recovery from the fastboot menu.
The phone booted to clockwork recovery, which confirms a successful installation of it.
I then rebooted the phone, and after it was fully booted, rebooted it to fastboot mode. When I selected recovery, I then get the box with an arrow pointing into the android, so I hit the proper keys and I ended up in stock recovery (blue text).
The install-recovery.sh script still reflashed the stock recovery even though I flashed it per your instructions.
If I rename that script and then install clockwork, any attempt to boot recovery goes straight to clockwork recovery (orange text, extra features, etc).
Did I do something different than you're suggesting? Based on my test, I don't think you have any option other than to rename that script (or delete the backup image it uses to flash stock) if you want to remain on Clockwork.
Thoughts?
you should still have the CW recovery, if you pushed it into the phone as recovery.img
after i reboot the phone, i can go back into CW just by selecting Recovery
i just use those reboot software, or manually hold volume up + power
then i get into the fastboot mode
in fastboot mode i select Recovery
and that takes me back to CW recovery
i did not rename the install-recovery.sh, just in case i ever want to restore the phone back to stock
i do know that if i do not rename the recovery-clockwork-3.0.0.5-crespo.img to recovery.img, then i will lose CW right after the reboot
AllGamer said:
you should still have the CW recovery, if you pushed it into the phone as recovery.img
after i reboot the phone, i can go back into CW just by selecting Recovery
i just use those reboot software, or manually hold volume up + power
then i get into the fastboot mode
in fastboot mode i select Recovery
and that takes me back to CW recovery
i did not rename the install-recovery.sh, just in case i ever want to restore the phone back to stock
i do know that if i do not rename the recovery-clockwork-3.0.0.5-crespo.img to recovery.img, then i will lose CW right after the reboot
Click to expand...
Click to collapse
Well, that's a weird one. You didn't say I tested it wrong, but I am getting different results than you.
If I were ambitious I would make a youtube video of it to show my results, not as a challenge, just to see if I'm doing something wrong.
Are you stock ROM? If not, maybe that's a difference that would explain it.
i'm on Bionix 1.3 beta
perhaps that's the difference?
AllGamer said:
i'm on Bionix 1.3 beta
perhaps that's the difference?
Click to expand...
Click to collapse
Almost certainly the difference.
I'll wager that if you go to the /system/etc folder that Bionix has removed that script for you. That would explain why it's not running and restoring the stock.
Check that out and let me know; we may have solved the mystery here.
FYI, I just downloaded the bionix 1.3 files and checked inside, no install-recovery.sh in it...
Hi.
I own a 3.1 rooted wifi only Xoom running BRD's 1.4.3 Tiamat kernel.
I finished completing these steps from this thread to try and enable marketenabler. Unfortunately, I'm stuck in this constant reboot now after the Moto logo.
I tried pressed volume up as soon as the Moto logo appeared, and the 'starting fastboot......' shows up but just hangs there. Has it anything to do with changing my build.prop?
This is the thread and the steps followed....
http://forum.xda-developers.com/showthread.php?t=1065698
**Ok, first of all, xoom must be rooted
Download verizon 3G build.prop from here http://dl.dropbox.com/u/6763988/build.prop.zip
Make a backup system/build.prop
Use, root explorer or adb to replace build.prop in system/
go to settings/application and clear data for market
Install marketenabler
Restart Xoom
Now open marketenabler, set to t-mobile us, start market end voila**
Would anyone be kind enough to help me?
I tried pushing my original backup file from my pc into the the directory of the new file I installed hoping to fix the problem with adb, when I reboot, my pc won't even recognise my xoom anymore.
It does connect now.
Any Help?
I figured I could still use Clockwork Recovery.
If I stuff up my system folder in my xoom, is there somekind of back up to replace it?
I've re-flashed my boot image and tiamat 1.4.3 to see if that would work. Did everything as it should, except, I'm still stuck in a boot loop.
???
sounds like youve messed something up bad, I would search the forums for the instructions on how to set it back to stock, read them carefully of course as doing this wrong could totally brick your device as with any modifications. Once youre back to Stock then you can carefully Root/Patch up to the version you want to..
tonyb15re said:
sounds like youve messed something up bad, I would search the forums for the instructions on how to set it back to stock, read them carefully of course as doing this wrong could totally brick your device as with any modifications. Once youre back to Stock then you can carefully Root/Patch up to the version you want to..
Click to expand...
Click to collapse
I think that's the way to go. Thanks anyway.
I am new to the world of flashing... tried it once and ended up hard bricking phone... totally my fault with wrong rom. sent it out to get fixed. got it back and all is good. but now my phone runs 2.3.3. tried to root with no luck. trying to atleast restore some apps and contacts
phone stats
model no: sgh-t959v
firmware: 2.3.3
baseband: t959vukf1
kernel: 2.6.35.7-t959vuvkf1-cl270364
build no: gingerbread.vuvkf1
any help and assistance appreciated. ive tried to read as much as i could, but most seem to be based off upgrading from 2.2.
thank you in advance
are you able to restore contacts through gmail sync? and as far as apps goes the ones that youve bought/downloaded from the market you will have to redownload...did you backup your apps with titanium backup?
yeah. backed up with Ti. most of my contacts were phone stored
you wont get the contacts back that werent synced to gmail or tmobile.
but try going to /sdcard/titaniumbackup and your apps should be in there, and either push them to /data/app/ or use root explorer and put them there...let me know how it goes.
jdubb1106 said:
you wont get the contacts back that werent synced to gmail or tmobile.
but try going to /sdcard/titaniumbackup and your apps should be in there, and either push them to /data/app/ or use root explorer and put them there...let me know how it goes.
Click to expand...
Click to collapse
i thought i couldnt use a root explorer without first rooting?
since im basically at square 1, can i just odin a rooted rom like icbinb or trigger? just want to make sure that i dont brick again, my wife would kill me..lol
you cant use root explorer to its full potential without rooting.
you should be able to odin back to froyo, but read through the threads to make sure you get to bootloaders right, because if you dont, you will hard brick your phone
you cant odin icbinb or trigger. those are only cwm flashable. once you successfully odin back to kb5 or kc1, look in krylons final cwm thread and move the two files to the right place and then you can flash one of those roms. for more information about the cwm flashable or odin roms, got to the bible thread in the development section
quick question... how do i know what bootloader i have?
if you are on 2.3 and you get the rainbow screen, then you are on froyo bootloaders. if you dont, you are on gb bootloaders. if you are running froyo fine, then you are on froyo bootloaders.
yea...im pretty sure thats right. lol. like 85%.
rainbow screen? tried to search for what that looks like?
is that only during initial boot
im guessing i have gb bootloader.... no crazy rainbow screen???
I'm a noob too, but this worked for me
I think I was in the same boat - rooted 2.2, then upgraded to 2.3.3 but lost root. I had all the Ti backup done, but then couldn't use it without re-rooting. I followed this (twice, the first time I didn't read carefully):
1. download things below:
Download zimage-root.tar to computer: http://forum.xda-developers.com/attachment.php?attachmentid=627433&d=1308258432
2. Download zimage.tar: http://forum.xda-developers.com/attachment.php?attachmentid=628363&d=1308338680
3. Download ODIN to computer and unzip it: http://www.mediafire.com/file/1qqk94teauc64nb/Odin3-v1.85.zip
4. You should have working USB connection between computer and phone. If not, install Samsung USB drivers:
download Samsung Drivers for 32-Bit windows: http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
download Samsung Drivers for 64-Bit windows: http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
5. reboot into download mod.
6. run the ODIN exe.
7. connect phone to computer.
8. click pda, select zimage-root.tar file, click start.
9. when finish, get a bootloop, remove phone from usb.
10. power off, replace the battery, again download mod, connect phone to computer, run the ODIN again.
11. click pda, select the zimage.tar file, click start.
12. reboot.
Wait you just got this phone back and its completely stock and running 2.3.3 out of the box?! Um that means they have already started to roll out the GB update for the SGS4G??? Why is nobody excited about this haha
on second thought: GRAB THAT PHONE THIS INSTANT AND HARVEST THOSE BOOTLOADERS WE NEED THOSE IF THEY ARE OFFICIAL LOL YOU MY FRIEND MAY HAVE THE FIRST OFFICIAL ROLLOUT OF GB WHY ON EARTH WOULD YOU WANT TO FLASH I BACK TO FROYO???
on third thought: i can help you with the contacts, if they were saved to your phone and your phone only then im sorry but you will never get those contacts back. Create a gmail account if you do not have one and go into settings and accounts and sync check the google and tmobile sync settings to have your contacts backed up for future use, this will solve your problem if it happens that you need to do a master reset or get a new phone! As far as restoring apps i cannot say much because you are running gingerbread.
I am way N00b at this but how do I remove this from my Atrix 2? It is eating up my battery and I can't open some of my apps, they force close. Is it possible to flash back to the point prior to this?
It was backed up before I started but know I cant find the back up. I just want to go back to the point when it was rooted. I used "MotoFail" to root and everything was going great and decided to try this, my bad, any ideas besides buying anoter phone?;-(
ozziedog said:
I am way N00b at this but how do I remove this from my Atrix 2? It is eating up my battery and I can't open some of my apps, they force close. Is it possible to flash back to the point prior to this?
It was backed up before I started but know I cant find the back up. I just want to go back to the point when it was rooted. I used "MotoFail" to root and everything was going great and decided to try this, my bad, any ideas besides buying anoter phone?;-(
Click to expand...
Click to collapse
you have one option, flash the fxz and reroot.
start over.
there is a great nOOb thread telling how to do it.
http://forum.xda-developers.com/showthread.php?t=1396650
ozziedog said:
I am way N00b at this but how do I remove this from my Atrix 2? It is eating up my battery and I can't open some of my apps, they force close. Is it possible to flash back to the point prior to this?
It was backed up before I started but know I cant find the back up. I just want to go back to the point when it was rooted. I used "MotoFail" to root and everything was going great and decided to try this, my bad, any ideas besides buying anoter phone?;-(
Click to expand...
Click to collapse
How did you back up?
If you used CWM (from the A2 Bootstrapper) just reboot into CWM, go to backup and restore, select restore, and select the backup that you made.
If you didn't use CWM or you can't find the backup then you will have to flash the fxz as said above. It will completely remove all of your apps and return you to stock 2.3.5. Make sure that you follow the directions about replacing files.
Thank you matt99017d I will check the link and cogeary I did the back up CWM I'll go that route first if that doesnt work, I'll go back to the beginning. Thank you again for the help
I could not find the backup in CWM so I flashed fxz following the instruction on the link you provided and the info. I'm back to 2.3.6 and it is rooted. Thats as far as I'm going for now, thanks for the help you all provided.
I see at /system/etc/init.d 2 files with sd-card optimization. 03sdtweak and 99override. Is there right or needed to delete one of them?
I highly suggest getting Titanium, for the cases where you don't have a back up, because I lost all my free apps and I don't even remember what all I had. I'm getting things back as I need them.
Douchewithaphone said:
I highly suggest getting Titanium, for the cases where you don't have a back up, because I lost all my free apps and I don't even remember what all I had. I'm getting things back as I need them.
Click to expand...
Click to collapse
https://market.android.com/mylibrary
^ shows everything you've installed from the Android Market. You should have records somewhere if you got things from the Amazon Appstore.
I haven't tried it myself but if you've made a backup in CWM you have the option to only restore apps/data.
Well I decided to give SuperCharged V5 with update 1, and when I disconnected form the charger this morning it was stuck in the boot animation. It has been stuck in that position for the last 30 minutes.
I connected it to PC and it doesnt show as being connected. I've done a search and can't find anything on how to fix it.
I did a battery pull, took SD card out to see if I could maybe transfer something from it to desktop, but everything that was on it is gone.
Don't know what happened.
Can someone point me in the right direction?? In the mean time I'll keep looking.
Ozzie Im in a similar situation. I"m in a bootloop as well (Supercharged Logo just keeps rolling on the screen). I can't get into the Android OS, and I also can't even get into Fastboot to flash back to stock. At this time it appears its bricked. I have been trying to fix this the past 12 hours.
Are you in the same situation??!
ej_424 said:
Ozzie Im in a similar situation. I"m in a bootloop as well (Supercharged Logo just keeps rolling on the screen). I can't get into the Android OS, and I also can't even get into Fastboot to flash back to stock. At this time it appears its bricked. I have been trying to fix this the past 12 hours.
Are you in the same situation??!
Click to expand...
Click to collapse
I am sorry to say, but if you can't get into fastboot it's probably bricked
so i installed V5 and update 2 and i am getting the force closes and my phone won't show up when i plug the usb into my computer
and i can't delete or edit files in my files and i can't open any websites or connect to airdroid on wifi, or use data so i can't get any files onto my phone
help...
flashing the stock fxz worked
Man...and I was gonna do this...flash the supercharged ROM. Nevermind.
after i flashed the 2.3.5 fxz like the bootstrapping thread instructed, i installed the ota update and rooted my phone again and then i tried the custom rom again just for fun
but this time i did v5 and then update 1. then instead of doing update 2, i flashed the image of the rom that's linked right under update 2 in the supercharged thread
it works flawlessly for me now
so i would just recommend that