Related
It does not like our phones. Has great options but.......it sucks. Everytime I flash it on my phone my recovery goes bad in a cpl days. Never had this problem with RA. Do a search rom manager pops up all over the place with bad recoveries. Stop using it ppl. Im sure ill get flamed for this but oh well. Kinda tired of reading of noobs that fall victim to a .apk that seems very easy to use until it craps out and then your stuck at the airport with a bad recovery and ADB no where in sight. Or even if u had ADB you still have no clue how to fix it!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=742007
http://forum.xda-developers.com/showthread.php?t=762325
http://forum.xda-developers.com/showthread.php?p=7443928&highlight=revovery#post7443928
I couldn't agree more.
never used it thank goodness.........
Never happened to me
EDIT: Sorry for my rudeness, anyways, people should know that it's not the greatest idea to use rom manager with cm5/cm6. It has already been established that it may be a bad idea to use the program with the following roms. Sorry I get really cranky in the mornings, not the best idea to come onto the forum with some old news :|
protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
I have never used it and I agree with him just from all the posts I have seen related too it messing up people's recovery images. Does that make me stupid?
I've used it for a few weeks now with no problems on my MyTouch on 1.6, 2.1, and 2.2 ROMs. Not saying others aren't having legitimate issues, but people in general are much more likely to post negative reports than positive ones.
protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
hahahahaha good one. Not to stupid to use it. the ui is very simple and easy to use. Flash clockwork or flash alternate. What im to stupid to do is figure out how to fix it after it kills recovery. but thank you for your input, I'm sure it will help someone out.
protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
Please lead us retartds through your install procedure, current rom, set-up so we can be as learndededed as you. I have had cm5&6 with ra installed upon initial set up. No swap/ noext1234, stock mt3g spl 2.22.23.02 radio. Nothing special. I even did it with the donut mytouch rom w/root.I only use basic apps, nothing that would interfere with recovery. to me it seems that when u flash a cpl different roms a day is when it hangs up. I can usually get the phone to boot back up, which gives me a chance to get back into rom manager and flash ra recovery back to the phone. the last cpl times I had to wipe cache before it would actually flash RA recovery. so basically if u can get the phone to boot past the splash screen go to rom manager and flash the **** out of ra recovery until it works. First we found out that clockwork didnt like flashing zip's and backups on low batteries 30% and lower. then the always fun recoverly log issue(cant recall the exact error right now) and of course the cant get to recovery issue. I know it's not a widesporead problem but it is a problem that renders phones useless until u can find someone nice enough to help u and not treat u like a retard. Not everyone knows as much about phones as you guys do....congratulations you know all there is about phones. go learn some ****ing human decency, if u have nothing helpful to say then shut up.
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
arefin said:
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
hmmmmm. Maybe since its flashing clockwork from inside rom manager is what might be killing it for some of us. tonight I will try just flashing clockwork outside of rom manager and see how that goes. i like clockwork's set up and it is easy to use, just kinda freaks me out when my recovery goes bad.
arefin said:
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
but at the same time thats why it is a part of rom manager. one click recovery flasher. to make it "easy". i highly doubt you can go into rom manager and incorrectly flash clockwork recovery. its a one click thing
it's also spoken out at many threads at xda that flashing the recovery from within the OS causes issues, so trying to install the recovery from PC or even RA1.7 should be a better option.
I'm considering that you already know the commands for that. better luck! remember, clock work will allow you to flash anything without signing - meaning? you can edit any update.zip to your liking and then forget about all the trouble of signing it before flashing. a simple toggle should do the trick while you are in recovery mode happy flashing.
Sent from my T-Mobile G1 using XDA App
It is either a case of your phone, sd card setup/left over files etc..
I use rom manager on every phone I root with no problems since its release. 6 G1's, 3 Fender LE's, 7 Mytouch 1.2 and 4 Evos. Sometimes, it takes couple seconds to show up or go into recovery, but that doesnt mean its gone. Recovery cant just dissapear without something either trying to over write it or it being erased.
crypysmoker said:
It is either a case of your phone, sd card setup/left over files etc..
I use rom manager on every phone I root with no problems since its release. 6 G1's, 3 Fender LE's, 7 Mytouch 1.2 and 4 Evos. Sometimes, it takes couple seconds to show up or go into recovery, but that doesnt mean its gone. Recovery cant just dissapear without something either trying to over write it or it being erased.
Click to expand...
Click to collapse
Im gonna give it one more try. I dont think I have ever.....
flashed clockwork from rom manager
reboot into recovery from rom manager right then (read some where that on some roms when u reboot to recovery using the regular way it might mess up....not sure about this one).
wipe everything (clockwork wipes more that amon ra)
reflash any rom
in my case... above steps then in this order
flash fireats custom mtd part 1.1
super E
Gapps
overclock update
fireats custom mtd part 1.2
anyone see a issue with what I have done so far??
Ok I will post back when clockwork fails again.....and if not f-in sweet
chrisgto4 said:
It does not like our phones. Has great options but.......it sucks. Everytime I flash it on my phone my recovery goes bad in a cpl days. Never had this problem with RA. Do a search rom manager pops up all over the place with bad recoveries. Stop using it ppl. Im sure ill get flamed for this but oh well. Kinda tired of reading of noobs that fall victim to a .apk that seems very easy to use until it craps out and then your stuck at the airport with a bad recovery and ADB no where in sight. Or even if u had ADB you still have no clue how to fix it!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=742007
http://forum.xda-developers.com/showthread.php?t=762325
http://forum.xda-developers.com/showthread.php?p=7443928&highlight=revovery#post7443928
Click to expand...
Click to collapse
chrisgto4 said:
hahahahaha good one. Not to stupid to use it. the ui is very simple and easy to use. Flash clockwork or flash alternate. What im to stupid to do is figure out how to fix it after it kills recovery. but thank you for your input, I'm sure it will help someone out.
Click to expand...
Click to collapse
You found your answer within the first example link that you provided, look at post #3:
http://forum.xda-developers.com/showthread.php?t=742007
rom manager is not for idiots like yourself. rom manager is a great tool for many different phones. sometimes it doesnt flash a recovery correctly maybe it be poor service to download the recovery, or low memory when flashing it. an advanced user (who its made for) can still flash recovery via fastboot, and have all the helpfulness and easy ui of rom manager and easy access to cm nightlies.
dont knock a dev who works on many different phones, and dont rely on noob application reports and bad reviews. anyone who finds rom manager crap is just a poor android user.
tehseano said:
sometimes it doesnt flash a recovery correctly maybe it be poor service to download the recovery, or low memory when flashing it.
dont rely on noob application reports and bad reviews. anyone who finds rom manager crap is just a poor android user.
Click to expand...
Click to collapse
i didn't want to get into this pointless discussion, but you have made a ****ty argument for rom mgr, you have confirmed that it doesn't work properly in certain circumstances, which is a good enough reason to not bother with it.
also, why shouldn't we rely on bad reviews? that's the point of a review, to give some idea about what experience to expect.
(i have never used it myself, amon ra recovery is enough for me.)
I agree it is an 'easy' shortcut that is not the best decision.. Like for example I think it killed my phone. I repaired permissions via rom manager, rebooted as it told me to and now my g1 wont boot past the g1 logo. I could install from a backup but the backup is 1+ month old (my error oops!). I am hoping to find a solution... Really dont wanna wipe everything..
warsng said:
i didn't want to get into this pointless discussion, but you have made a ****ty argument for rom mgr, you have confirmed that it doesn't work properly in certain circumstances, which is a good enough reason to not bother with it.
also, why shouldn't we rely on bad reviews? that's the point of a review, to give some idea about what experience to expect.
(i have never used it myself, amon ra recovery is enough for me.)
Click to expand...
Click to collapse
I made a perfectly good argument. Yes it can "mess up", but thats not at the fault of the app. It's at the fault of the phone. There are things that can go wrong that Koush cannot control. It is for ADVANCED users as a quick helpful UI for recovery-based operations. People that don't know what they're doing, or only half-way do shouldn't be using it. However, too many Android users *think* they are advanced enough, yet 5 minutes after using it, post a "PLEASE HELP, PHONE IS BROKEN", because they DON'T know what they're doing.
I'm not saying that all bad reviews are missguied, but I can assure that 90% of them are from noobs that have no idea what they're doing. They rooted their phone because someone told them it was cool, and they have absolutetly no idea whats in their hands and what they can do with it. Let alone, how to properly work it and fix problems. It's easy as pie to point out noobs from those crowds of users, those 3 links in the OP's post are all perfectly examples. People who came to XDA, signed up, never posted anything, then messed up and came crying to the board asking for help (usually in Android Development because people like them, and the OP too, don't how to to post in the correct section).
So for the last time, if you don't know what you're doing on your phone, don't do it. Just because you have root, and an app says "for root users", doesn't mean its for you, which EVERYONE assumes it is. It's piss-poor users like that, that ruin app reviews and the name of Android everywhere.
tehseano said:
I made a perfectly good argument. Yes it can "mess up", but thats not at the fault of the app. It's at the fault of the phone. There are things that can go wrong that Koush cannot control. It is for ADVANCED users as a quick helpful UI for recovery-based operations. People that don't know what they're doing, or only half-way do shouldn't be using it. However, too many Android users *think* they are advanced enough, yet 5 minutes after using it, post a "PLEASE HELP, PHONE IS BROKEN", because they DON'T know what they're doing.
I'm not saying that all bad reviews are missguied, but I can assure that 90% of them are from noobs that have no idea what they're doing. They rooted their phone because someone told them it was cool, and they have absolutetly no idea whats in their hands and what they can do with it. Let alone, how to properly work it and fix problems. It's easy as pie to point out noobs from those crowds of users, those 3 links in the OP's post are all perfectly examples. People who came to XDA, signed up, never posted anything, then messed up and came crying to the board asking for help (usually in Android Development because people like them, and the OP too, don't how to to post in the correct section).
So for the last time, if you don't know what you're doing on your phone, don't do it. Just because you have root, and an app says "for root users", doesn't mean its for you, which EVERYONE assumes it is. It's piss-poor users like that, that ruin app reviews and the name of Android everywhere.
Click to expand...
Click to collapse
Get a clue , its a program any gimp, including you, can install from the market, it is made in such way ...the fact that it dosent fail to write the recovery in fastboot mode means nothing!
This program shouldnt let the G1 user flesh any rec image. Till that happens it is the DEV's fault. Shouldnt be in the G1 CM's either.
After waiting for the official AT&T froyo release with the captivate, I decided to just go ahead and flash a froyo ROM. I've decided to flash the axura ROM first since i heard good things about it.
So while I'm finishing charging my phone before the flashing, is there anything I need to keep note of before flashing so that I can prevent bricking my phone? I've read up on the forums and watched the video from connexion2005 from the post: http://forum.xda-developers.com/showthread.php?t=867153.
Its pretty scary since I'm not much of a tech savy guy and this is my first android phone. Any help and suggestions will be appreciated.
agegsg said:
After waiting for the official AT&T froyo release with the captivate, I decided to just go ahead and flash a froyo ROM. I've decided to flash the axura ROM first since i heard good things about it.
So while I'm finishing charging my phone before the flashing, is there anything I need to keep note of before flashing so that I can prevent bricking my phone? I've read up on the forums and watched the video from connexion2005 from the post: http://forum.xda-developers.com/showthread.php?t=867153.
Its pretty scary since I'm not much of a tech savy guy and this is my first android phone. Any help and suggestions will be appreciated.
Click to expand...
Click to collapse
Backup all your apps and data with Titanium Backup. Make sure your battery is fully charged, and removing your sim and SD cards are good practice.
Have fun! You won't go back.
- Backup all your files and make a nandroid backup!
- Get Odin3 One-Click and drivers to get your phone back to stock in case you brick it: http://forum.xda-developers.com/showthread.php?t=731989
- There may be additional precautions you can take, so read through related threads on xda.
agegsg said:
After waiting for the official AT&T froyo release with the captivate, I decided to just go ahead and flash a froyo ROM. I've decided to flash the axura ROM first since i heard good things about it.
So while I'm finishing charging my phone before the flashing, is there anything I need to keep note of before flashing so that I can prevent bricking my phone? I've read up on the forums and watched the video from connexion2005 from the post: http://forum.xda-developers.com/showthread.php?t=867153.
Its pretty scary since I'm not much of a tech savy guy and this is my first android phone. Any help and suggestions will be appreciated.
Click to expand...
Click to collapse
If you've read as much as you claim to have read, then you're probably in good shape. It's really not an unsafe process as long as you have some idea of what you're doing. I was very nervous about it myself the first time, but since then I've probably flashed 20 roms without a problem.
A couple of things that I would tell you, if you aren't already aware:
1. MAKE SURE that BEFORE you flash, you can get into download mode from the phone being off using one of the methods. I'm sure you've seen the one-click flash back to JF6 (stock) that was posted - download that if you haven't. For me, removing the battery, sim, and ext sd, replacing the battery, and holding down both volume buttons while plugging in the USB works really well - just make sure Odin is running before you do that. If you do manage to brick it, you will want to be able to get to download mode and flash back to stock.
2. After moving to a custom rom, it is best to always flash back to stock before flashing a different rom; you can avoid a lot of potential problems this way.
3. After rooting your phone, backup the update.zip in /sdcard/ on your computer. Any time you flash back to stock, you can reinstall CWM really easily by just putting that update.zip back in /sdcard/ and choosing "reinstall packages" from the recovery menu again. Sometimes you may have to do it twice before it enters CWM.
4. OCLF in the market is, to me, the easiest and quickest way to root your phone, but the one click root method isn't much worse. Just a matter of preference, I guess.
Good luck! Come back if you have any problems.
EDIT: apparently two people replied while I was typing my response lol! But what they said is very good as well.
Thank you for all your help. One quick question though, do I need the android ID changer?
the biggest mistake people make is not making sure they have the button combinations to enter recovery or download. (download = hold both volume buttons own and plugging usb cable in; recovery = hold volume buttons down, then holding power until AT&T screen pops up, letting go of power but still holding both volume buttons) if either of these don't work, you must, before doing ANYTHING else, flash the stock odin one click with the button fixes; it is posted somewhere in the development forum. and no you shouldn't need the android id changer unless you want to keep the android id that your phone came with. then open the changer and click save id and flash your rom of choice. most custom roms have a script to automatically load a saved id or randomly generate one if there wasn't a saved one. good luck in all your flashing endeavors!
edit: also as bodaciousdrake mentioned previously about cwm recovery, you should always keep the update.zip that contains cwm recovery on your sd card and you'll never need to change that to something else because using cwm recovery you can flash any .zip file that you want and it does not need to be named update.zip.
Take out the external SD card before you accidently delete 10 GB of music you had just perfected the selection of. (not that I accidently did that... lol)
mindbullet said:
Take out the external SD card before you accidently delete 10 GB of music you had just perfected the selection of. (not that I accidently did that... lol)
Click to expand...
Click to collapse
lol oops! Did that happen with a master clear, or when you flashed the rom? I have forgotten to take out the sim/ext sd once or twice but I have never had a problem...yet.
agegsg said:
Thank you for all your help. One quick question though, do I need the android ID changer?
Click to expand...
Click to collapse
Yes, you need it. Download it from the market, while on 2.1, and save your id onto your sd card. After you are on 2.2, choose Load id and it will automatically reboot.
majinzen said:
Yes, you need it. Download it from the market, while on 2.1, and save your id onto your sd card. After you are on 2.2, choose Load id and it will automatically reboot.
Click to expand...
Click to collapse
What exactly is the point in saving the phone id? Sorry I'm kinda a noobie at this and looking up things about phone id, it seems like it just is an identifier for the phone but doesn't really provide anything.
Also, how do I get out of download mode? I've put it in download mode to make sure it works and it seem I can't get out of it... I've done the 2 volume bottons with the usb cord.
there's another thread in this forum that answers that question perfectly. also to exit download mode you need to pull the battery out.
slifer315 said:
there's another thread in this forum that answers that question perfectly. also to exit download mode you need to pull the battery out.
Click to expand...
Click to collapse
Really? just take the battery out?
agegsg said:
What exactly is the point in saving the phone id? Sorry I'm kinda a noobie at this and looking up things about phone id, it seems like it just is an identifier for the phone but doesn't really provide anything.
Click to expand...
Click to collapse
Basically, a lot of 2.2 Roms come with the same android id, 977blah... If you don't want market issues later I would suggest that you put in your original 2.1 android id. You can always search more if that answer isn't sufficient. And yes, do a battery pull to get out of download mode.
I've master cleared but can't seem to root. Every time I try with the one click root, and I go to recovery, it said it can't find the update.zip from the /sdcard/
yep, just pull the battery. also you don't need to root to flash roms. just grab the update.zip containing clockwordmod recovery from the thread in the development forum, put it on your sd card, boot to recovery and select reinstall pacakges. after that, reboot the phone (you might have to reinstall packages again) then you'll be ib clockwordmod recovery and you'll be able to flash any rom you want without having to change the filename.
agegsg said:
I've master cleared but can't seem to root. Every time I try with the one click root, and I go to recovery, it said it can't find the update.zip from the /sdcard/
Click to expand...
Click to collapse
For some reason I got this too the first few times I tried to root. I then noticed that in the cmd prompt, for a split second it said failed to push update.zip or something due to privileges.
How I fixed it was ran the one-click root on windows in admin mode. It worked after that.
Thanks guys for all your help. I got it to flash the ROM and it seems I haven't bricked my phone
Thanks again
I am obviously a NOOB. I am reading previous posts, but this is way more complicated than I expected.
I just want to get any factory firmware on my Captivate so that I can sell it. Right now I can't enter Download mode or Recovery mode via button combinations. I have tried for hours now.
Are there any simple directions that actually give links to what I need to download. ie...What Odin Files, etc.
Please help!
Here's the ODIN 1-click
http://forum.xda-developers.com/showthread.php?t=731989
And please post in the RIGHT section this is for development only.
Thanks
jarken20 said:
I am obviously a NOOB. I am reading previous posts, but this is way more complicated than I expected.
I just want to get any factory firmware on my Captivate so that I can sell it. Right now I can't enter Download mode or Recovery mode via button combinations. I have tried for hours now.
Are there any simple directions that actually give links to what I need to download. ie...What Odin Files, etc.
Please help!
Click to expand...
Click to collapse
And if your Captivate boots, you don't need button combinations to enter download mode. You need to download the SDK, put the Captivate in a USB debug mode, and then do "adb reboot download" to get there.
NOOB.
adb cmd???
jarken20 said:
I am obviously a NOOB. I am reading previous posts, but this is way more complicated than I expected.
I just want to get any factory firmware on my Captivate so that I can sell it. Right now I can't enter Download mode or Recovery mode via button combinations. I have tried for hours now.
Are there any simple directions that actually give links to what I need to download. ie...What Odin Files, etc.
Please help!
Click to expand...
Click to collapse
Why don't you just do a factory reset and delete your files from the phone ?
If your unable to just go in download mode and use the Odin one-click then you clearly need to spend more time reading. This is also a big red flag that you could turn your phone (effortlessly) into a brick.
Your choices are:
A) Read up, learn and invest time in it (not just 30min and a simple how-to then jump the guns with it)
B) Just delete your stuff, do a factory reset and sell it like it is.
A more tech savvy user will mod it to its liking. Why do the job for them if your not confortable doing it in the first place? It's not like your going to use it again, your selling it.
Yup I agree - if you already have a Stock phone - don't screw with it. Just do the factory reset which will wipe the phone back to stock anyways - and if you want to go that extra step you could format the internal SDCard from within the phone menu.
If it aint broke - don't play with it! (Well my real motto is If it ain't broke tweak it! but.. for you it doesn't apply)
I don't necessarily WANT to sell it. I want to give it a fair chance. I am used to an iPhone but I wanted to see what all the talk about the androids is about. I heard that this is all SO simple. Maybe so for some. I am just spoiled by the user friendliness of apple i guess.
Anyway, i haven't given up completely. I am gonna try all this again. I just don't have Hours upon Hours to define all the stuff that I'm reading. I am just surprised how difficult it is to make this thing anywhere near the same level as an iPhone. I'm sure it's easy for most. Maybe I'll figure it out....
Jumping in the conversation since we are on the subject. I rooted with z4root and flashed with rom manager. If I want to go back to stock will odin 1click work?
Sent from my SAMSUNG-SGH-I897 using XDA App
Tchem said:
Jumping in the conversation since we are on the subject. I rooted with z4root and flashed with rom manager. If I want to go back to stock will odin 1click work?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes
(Yes is not a 10 char word)
jarken20 said:
I don't necessarily WANT to sell it. I want to give it a fair chance. I am used to an iPhone but I wanted to see what all the talk about the androids is about. I heard that this is all SO simple. Maybe so for some. I am just spoiled by the user friendliness of apple i guess.
Anyway, i haven't given up completely. I am gonna try all this again. I just don't have Hours upon Hours to define all the stuff that I'm reading. I am just surprised how difficult it is to make this thing anywhere near the same level as an iPhone. I'm sure it's easy for most. Maybe I'll figure it out....
Click to expand...
Click to collapse
It's not that hard but yes your spoiled . It's not like going to a website and bingo it's done like the jailbraiking on iphone. You actually do the commands manually and learn something in the process.
You also need the corresponding tools to do the job (Google SDK for ADB, Odin for flashing, etc..). You don't build a house only by looking at the blue prints you have to put some work into it
Check out my ODIN video it should walk you through this very easily.
http://forum.xda-developers.com/showthread.php?t=877652
I am wondering how easy it is to brick my Captivate. Also, how easy is it to brick the phone, with the only solution being to use a JIG?
Is the only way to brick if you do something stupid? If you follow all instructions (flash to stock, etc.) is it even possible to brick it? I've upgraded my phone to 2.2 using Kies; does the fact that I've upgraded once make it muc less likely to fail and brick later?
I'm wondering this because all the ROM makers must flash constantly, so I'm thinking there must be a way to avoid bricks.
Thank you!
AmandeepG said:
I am wondering how easy it is to brick my Captivate. Also, how easy is it to brick the phone, with the only solution being to use a JIG?
Is the only way to brick if you do something stupid? If you follow all instructions (flash to stock, etc.) is it even possible to brick it? I've upgraded my phone to 2.2 using Kies; does the fact that I've upgraded once make it muc less likely to fail and brick later?
I'm wondering this because all the ROM makers must flash constantly, so I'm thinking there must be a way to avoid bricks.
Thank you!
Click to expand...
Click to collapse
Depends on your Captivate. In general, it's a bad idea to flash back to stock unless absolutely necessary. Bad Odin flashes are one of the biggest causes of bricked Captivates. Bad flashes through other methods (like CWM) usually leave you with boot problems, but working button combos for download mode. You should also check beforehand that your button combos work, since some Captivates are without them out of the box.
Also, wrong forum. This belongs in Q&A.
GGXtreme said:
Bad Odin flashes are one of the biggest causes of bricked Captivates.
Click to expand...
Click to collapse
Isn't the accepted way (as in the stickied thread) to always flash to stock?
GGXtreme said:
You should also check beforehand that your button combos work, since some Captivates are without them out of the box.
Click to expand...
Click to collapse
"Hold down both volume buttons and while holding them down plug the phone in." works for me
I have bricked my phone to the point of needing a jig 3 times now all because of odin. But the jig is 99 cents and is easy to use
sent from my captivate running a kitchen rom and hardcores 256hz k12n
kschumake83 said:
But the jig is 99 cents and is easy to use
Click to expand...
Click to collapse
Can you buy it, or do you have to make it from components?
Flashing back to stock is only needed when you have to, but no you do not have to flash to stock every time you flash a rom, a bad odin flash is usually the main cause in a bricked phone.. But as long as you can get to recovery or download mode, then its not bricked, you can usually get something flashed either way
existz said:
Flashing back to stock is only needed when you have to, but no you do not have to flash to stock every time you flash a rom, a bad odin flash is usually the main cause in a bricked phone.. But as long as you can get to recovery or download mode, then its not bricked, you can usually get something flashed either way
Click to expand...
Click to collapse
But the stickied thread says the exact opposite. I'm a little confused.
nbs11 said:
Here is the rule of thumb: if it does not specifically say anything about being able to not use ODIN in the original thread for the ROM you MUST you ODIN.
Click to expand...
Click to collapse
AmandeepG said:
But the stickied thread says the exact opposite. I'm a little confused.
Click to expand...
Click to collapse
Sometimes personal habit becomes the correct way to do something. For instance one teacher teaching how to count with pictures of apples and the other using oranges.
GGXtreme said:
Bad Odin flashes are one of the biggest causes of bricked Captivates. Bad flashes through other methods (like CWM) usually leave you with boot problems, but working button combos for download mode.
Click to expand...
Click to collapse
Do these "bad" flashes occur do to doing improper things, like pulling the cable mid-update, or forgetting to unlagfix before, or stuff like that? Or are they purely random?
Normally The bad flashes from odin are due to the fact the the phone being flashed did not have the 3 button combo by default. I personally have flashed ALOT and always odin and master clear before a new rom, the only time I bricked and needed a jig was when I had my old phone (got it replaced) that didnt have the 3 button and used the wrong odin.
zelendel said:
Normally The bad flashes from odin are due to the fact the the phone being flashed did not have the 3 button combo by default. I personally have flashed ALOT and always odin and master clear before a new rom, the only time I bricked and needed a jig was when I had my old phone (got it replaced) that didnt have the 3 button and used the wrong odin.
Click to expand...
Click to collapse
Thanks! I'm gonna check if my Captivate has this 3 button recovery mode.
If it does, is the 3 button way just as effective as a JIG? And how effective is the 3 button and JIG at recovering from bricks (like I mean, how possible is it that they will not work)
AmandeepG said:
Can you buy it, or do you have to make it from components?
Click to expand...
Click to collapse
you can buy jigs online people sell for 20$ or so...but it's actually very simple to make and so cheap as well so buying one is slightly pointless. also, i have flashed too many roms i've lost track, my phone shutdown in the middle of an odin, etc etc, and i always manage to get out of it so i wouldn't be concerned. having 3button enabled helps tho
AmandeepG said:
Thanks! I'm gonna check if my Captivate has this 3 button recovery mode.
If it does, is the 3 button way just as effective as a JIG? And how effective is the 3 button and JIG at recovering from bricks (like I mean, how possible is it that they will not work)
Click to expand...
Click to collapse
I am guessing that you are concerned with bricking yours. You must be thinking about flashing a rom for the first time. I needed the jig yesterday for the first time. From what I understand, the jig method is almost a guarantee fir download mode, making the captivate nearly unbrickable. Can it be bricked... I am sure it can, but you are part of a community full of resources to keep you from doing so. You trepidation is not unique... I too was slow to flash my captivate. Now that I have, I have a phone that I love. I have been able to contribute to the community. And... I have a new found addiction.
Hi. My username is NunHugger and I am a flashaholic.
Sent from my SGH-I897 using XDA App
NunHugger said:
I am guessing that you are concerned with bricking yours. You must be thinking about flashing a rom for the first time.
Click to expand...
Click to collapse
You are completely right there!
I think I'll hold off doing my first flash until I can go out and get the parts for the jig, make and test it, so I can be sure nothing bad will happen
zelendel said:
Normally The bad flashes from odin are due to the fact the the phone being flashed did not have the 3 button combo by default. I personally have flashed ALOT and always odin and master clear before a new rom, the only time I bricked and needed a jig was when I had my old phone (got it replaced) that didnt have the 3 button and used the wrong odin.
Click to expand...
Click to collapse
Same here...corrupted data is corrupted data..and will cause problems...no matter how it gets loaded ...I've have been using Odin since I came to the Captivate..and is the only way I have been able to actually enjoy a new rom..A new rom...a fresh install..less problems for me.
Mac
A question about download mode:
I want to test if my captivate can get into download mode by the 3-button combo. However, I don't have any zips to update or anything to download or anything like that.
How do I enter download mode and then exit without making any modifications?
I thought I could just power the phone off, but in big letters it says "Do not power off target" (in videos I've watched).
AmandeepG said:
Isn't the accepted way (as in the stickied thread) to always flash to stock?
Click to expand...
Click to collapse
Accepted, yes.
Stupiud, yes.
You don't need anything to flash to get into DL mode
Just follow the instructions as it says and if it comes up you can just reboot the phone. Although you have to pull the battery. Although I've heard that holding just the Vol Up and Power for 10 secs also works. I've never tried it though
AmandeepG said:
Do these "bad" flashes occur do to doing improper things, like pulling the cable mid-update, or forgetting to unlagfix before, or stuff like that? Or are they purely random?
Click to expand...
Click to collapse
Depends on a lot of factors. It could be that your Captivate doesn't support flashing back to earlier than JH2 (JF6 one-click will brick), that your Captivate is already missing button combos (requires C3P0LOL's fixed Odin or AT&T's OTA JH7 update), a bad USB cable, problems with Windows, using the wrong USB port, etc. (all on top of user error). Lagfix won't affect Odin flashes.
AmandeepG said:
Do these "bad" flashes occur do to doing improper things, like pulling the cable mid-update, or forgetting to unlagfix before, or stuff like that? Or are they purely random?
Click to expand...
Click to collapse
I wouldn't say they are random. They are probably mostly caused by user error or some fault in the USB chain (port, cable, driver interactions). Whatever the root cause, from what I can see almost all bricks/semibricks are the result of using odin (I include cases such as where a cwm flash results in a boot loop and the user can recover because he used one-click and has no button combos).
Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!
Jetboard said:
Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!
Click to expand...
Click to collapse
1. You can safely root your x8 regardless of when it is manufactured, you will not brick it
2. You have 11w48 so it is very risky to unlock your bootloader, i suggest you flash ROMS that is for stock
3. If you get soft bricked you can flash the stock firmware back using flashtool or SEUS, if it is a hard brick, you need to go to the nearest Service center or use a JTAG
Swyped via Tapatalk 2
Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?
Jetboard said:
Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?
Click to expand...
Click to collapse
you can root your phone. but you can't unlock bl.
when you root your phone, you cam install cwm recovery. simply dl a rom for stock kernel and go to recovery and install(flash) the rom. remember to check the instructions first.
Just because i don't doesn't mean i can't.
All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?
F308 said:
All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?
Click to expand...
Click to collapse
this is for x8. not sure how it works on J. but yeah we don't havt fastboot either. but we can install cwm even with a locked bl. again that's for se x8.
edit: my advice is go to your phone's subforum. you'll get your answers there.
Just because i don't doesn't mean i can't.
Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.
F308 said:
Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.
Click to expand...
Click to collapse
there probably are a few unbreakable rules, but not being familiar with your device i can't guarantee that it's safe or it would work.
Just because i don't doesn't mean i can't.
Despite lot of reading I still am missing knowledge.
Question is:
What is fastboot ?
I found more than one definition of it and compiled into my own.
1.
Of course fastboot.exe is Windows binary (part of flashtool pack) which does certain type of work.
This is not what we are interested in.
2.
I concluded that:
- fastboot is one of modes into what android device can wake up. Just like linux can boot in different ways or Windows into single mode.
- this feature is encoded into boot.img, it is not separate android application.
- boot.img will work only with related kernel.img. They are like love and marriage (which is like horse and carriage - Bundy's).
- Sony sometimes disables stock boot.img to boot into this mode then without replacing boot .img it is impossible.
More comments ?
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Just because i don't doesn't mean i can't.
Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is okay.
Um, I tried that one it didn't work. It said some stuff are missing, then it exited randomly etc.. Can someone give me a link or a short/long guide which I can use that's latest? I do have some X8 drivers in a .zip file but no idea how to install them. Thanks in advance.
Jetboard said:
Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is good.
Click to expand...
Click to collapse
I rooted mine with this
Means its safe
Sent from my X8
Having few issues with the SuperOneClick thing... It sometimes randomly exits, tells me that some stuff are missing etc. Any help? =/