Database Develop

News flash***rom manager***

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.

[Q] Brick

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).

Installing GB ROM

Is it common to take about 25 minutes and still not be able to complete the installation of GB Rom using PC Odin..?
I am trying to install KL3_KL1 GB Rom and the PC Odin is stuck at Factory fs for 25 mins ...
unplugged the cable, removed the battery and restarted the process .. still the same no matter what I do...
I am at the moment following steps form dr.Ketan's threads.. but the process seems to take a little too long and am unable to get into recovery mode.. Its only download mode and never going past the factoryfs.img situation in PC Odin..
I was on Stock ICS ROM Indian version before i started the process with PC Odin.
My goal is to get into Criskelo ROM for now.
Any help of suggestions to get me out of the situation please..

Have you ever did factory reset or wipe on stock ICS?
this is bad sign, and highly suggestive of super brick emmc bug. if you cnfirm wiping on stock ICS then it must be that only.

sob sob ... may be i did ...
should i just handover my phone to Samsung service center now ??

Yes, just check your flash counter is zero
Sent from my GT-N7000 using xda premium

yep.. That one is set to Zero.. Will Samsung just re-install software or replace device in this case ?
I have a nandroid backup taken 2 days back. Can i use that backup on the new phone to get back all my settings ??I primarily need contacts that i do not want to loose.

I believe it's a Motherboard replacement that you will be given, I doubt there will be anything you can pull from the old phone..

I luckily copied the nandroid backup onto my PC along with the md5 checksum... Would that help me ?
what is the process to restore from Nandroid backup
Recovery --> restore --> show the target ? is that it ?

Coolkriss said:
I luckily copied the nandroid backup onto my PC along with the md5 checksum... Would that help me ?
what is the process to restore from Nandroid backup
Recovery --> restore --> show the target ? is that it ?
Click to expand...
Click to collapse
No, never try it. You wont be able to restore anything. Just send to repair center and have a new mobo replacement if still under warranty.
Then after get your devices back and check again how to do nand restore. ( please read or ask before do any nand restore).
Good luck, mate.
Sent from my GT-N7000 using xda premium

As per above post - just wait until they send the device back repaired -
In the meantime read, read, read on how to go about these things otherwise you risk another brick..
To be honest, I'd just start a fresh when the new phone comes back..

Thanks guys .. Thanks for all the prompt responses. I just hope they dont take long time to get me the repaired or new phone.
I will just let my gmail account do the sync.

CJSlim79 said:
As per above post - just wait until they send the device back repaired -
In the meantime read, read, read on how to go about these things otherwise you risk another brick..
To be honest, I'd just start a fresh when the new phone comes back..
Click to expand...
Click to collapse
You are right, actually i do believe for those who get bricked with their devices must be a experienced flasher. Those of them ( included myself) surely only read how to unroot the new devices but never read other thread such as ...how to ugrade rom...general section...problem.....
But i think after these brickbug dilemma, a lot of xda member like me and you sure will read ...read and read the whole forum before do any rooting and flashing no matter jump to which brand of devices......
Sent from my GT-N7000 using xda premium

Usually new user are lazy to read n search, or searching just single targeted topic and follow it without even reading first few comments of op.
Though i remember coolcris is quite senior n if i remember correctly he had communicate with me many times on time of gb rom. But sadly sometime members not taking advise seriously. Or may be selects short cuts.
Have anyone remember single case faced any issue who updates rom theoritically clean or following instruction to d letter?
I believe if you read instruction fully n follow it word.to word, chances of brick is almost zero.
Sent from my GT-N7000 using xda premium

dr.ketan said:
Usually new user are lazy to read n search, or searching just single targeted topic and follow it without even reading first few comments of op.
Though i remember coolcris is quite senior n if i remember correctly he had communicate with me many times on time of gb rom. But sadly sometime members not taking advise seriously. Or may be selects short cuts.
Have anyone remember single case faced any issue who updates rom theoritically clean or following instruction to d letter?
I believe if you read instruction fully n follow it word.to word, chances of brick is almost zero.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
You're right mate, If the instructions are followed then I can't recall a single issue..
I've used your instructions (after extensive reading) and also had a lot of support from azzledazzle (Who was kind enough to walk me through my first downgrade).
I've had Android for a few years now since ditching the iPhone's and on HTC I used to flash anything and everything and just nandroid if anything went wrong. I think the issue here is that there is an issue, a bug with the eMMC, and people don't bother to research their NEW device, they approach with "I've flashed Android before" attitiude and this is where we end up...
It took me a while, and as I say alot of research before i started dabbling with the Note.... And as I am sure AD will confirm, I asked every n00b question under the sun of him about the process.. Yeah, I was a n00b and I am still learning... I asked the questions, nobody laughed and my Note is still purring...
I guess people either don't wanna feel stupid by asking (Old saying: No such thing as a stupid question!) or they are confident they "Know" how to do it because they have done so on other Android devices...
The guys on this forum are a wealth of knowledge and maybe it's just me, But I like to learn...
Hopefully, I maintain my head and don't mess it up in the near future and I am considering testing NoteCore V7 STD... but still not comfortable with the cleaning scripts etc - So i will read more, ask more and learn more... and hopefully continue to use my Note .. more...

dr.ketan said:
Usually new user are lazy to read n search, or searching just single targeted topic and follow it without even reading first few comments of op.
Though i remember coolcris is quite senior n if i remember correctly he had communicate with me many times on time of gb rom. But sadly sometime members not taking advise seriously. Or may be selects short cuts.
Have anyone remember single case faced any issue who updates rom theoritically clean or following instruction to d letter?
I believe if you read instruction fully n follow it word.to word, chances of brick is almost zero.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I know and this was perfectly my mistake ..
I have flashed a lot of times and i actually remember know about the eMMC bug.. the only thing is that i did not check if i had that bug ..
Situation for me today.. I started the process and got an email that i had to respond immediately from my office..
In this process, I forgot if i did a reboot into recovery after flashing the Abyss Kernal .. that is when i just went ahead with the wipe cache/dalvik and data ...
This was my lazy A$$ to blame ..
but for anyone doing a flashing .. please concentrate on what you are doing and just dont rush ahead ...
and ofcourse read, read & read before you proceed with any steps...

Coolkriss said:
I know and this was perfectly my mistake ..
I have flashed a lot of times and i actually remember know about the eMMC bug.. the only thing is that i did not check if i had that bug ..
Situation for me today.. I started the process and got an email that i had to respond immediately from my office..
In this process, I forgot if i did a reboot into recovery after flashing the Abyss Kernal .. that is when i just went ahead with the wipe cache/dalvik and data ...
This was my lazy A$$ to blame ..
but for anyone doing a flashing .. please concentrate on what you are doing and just dont rush ahead ...
and ofcourse read, read & read before you proceed with any steps...
Click to expand...
Click to collapse
I'm on a wing and a prayer at the mo as before i did any modding i was helping my bro (who lives in another country) and was talking him through it - jumped into Stock recovery and hit wipe cache by mistake...
It can and does happen but I am very diligent now and I've flashed a a good few ROM's and a good few stock recoveries since then so I hope i got away with that stupid mistake...maybe it's the wipe data only that brings forth "The Brick"

Yes..
anyway. I gave my Note to the SSC today .. IT was strange that they said .. DO NOT DO OTA .. you have to come to SSC for any software upgrade.
They initially told me that this is out of warrenty as I did OTA and showed them who the BOSS was .. Instantly they changed the tone and now they say we will do it for now, but the next time bring it to SSC for upgrades ..
They asked me to visit them tomorrow to collect the unit, but i doubt if they can change the Motherboard by tomorrow. Hoping they will..
Will keep you all posted on the status
Thanks a lot for all your guidance guys ...I would not have loved my Note so much if I was not on XDA

Now this has gone bad.. the SSC tells me that the software upgrade is not covered under warranty and is asking me to take back my phone .. They are not ready to repair it ..
Help me here guys ... anyone aware of something that i can scare them with ??

Coolkriss said:
Now this has gone bad.. the SSC tells me that the software upgrade is not covered under warranty and is asking me to take back my phone .. They are not ready to repair it ..
Help me here guys ... anyone aware of something that i can scare them with ??
Click to expand...
Click to collapse
You can advise them of many many instances of this brickbug and provide evidences FROM SAMSUNG confirming that exists and acknowledging that this can be triggered by a simple update / large data move or copy.
This is standard practice for Service Centres, unfortunately they always try to get out of it.. Stand your ground, keep your head and you will be given a repaired / replaced device..
Oh - and answer any questions straightforward - Yes / No, Do not offer information.
Did you root / flash / play around - No
How did this happen - Via KIES
etc
Again - This can be triggered via a standard Factory reset / Wipe from within Settings > Factory Reset on ALL stock ICS kernels...
A little research on these forums will give you enough info...
Good luck
---------- Post added at 02:35 PM ---------- Previous post was at 02:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=1633938

Thanks a lot for the advice.. I am searching if I can find any official Samsung statement anywhere to get this resolved.
I called the head of SCC in my city and spoke to him today. He will check with the center and give me a call tomorrow..
Am just hoping this gets resolved... aaargh ...

Coolkriss said:
Thanks a lot for the advice.. I am searching if I can find any official Samsung statement anywhere to get this resolved.
I called the head of SCC in my city and spoke to him today. He will check with the center and give me a call tomorrow..
Am just hoping this gets resolved... aaargh ...
Click to expand...
Click to collapse
Check the thread I posted..
There's a few Dev's here been in touch with SS over this issue since it was realised and I'm pretty sure you've all you need to basically tell them to replace it, No, Demand it...
Even under the Sale of Goods act - the device should be fit for purpose it is sold for.
Given that even on STOCK Firmware you can brick this device without rooting / modding AT ALL.. indicates this statement is not met. The device has a highly publicised and highly know firmware issue and Samsung were stupid enough to release a software modification (Which they encourage you to download via THEIR software) which enables you, without knowledge to destroy your phone..
It's your fault as you know that it happened (As we know from this forum and more the safe way)
But it is THEIR problem that they have the issue.. Do not take no for an answer, And to be honest - I would have refused to wait for the callback.. I would have advised (As I have previously) that I will hold on the line while they contact whoever they need to because you are eager for resolution of this.
You will get a new/repaired device...

Need help to Hard Brick my phone

Yes, you read correct, I want to hard brick my phone not unbrick it but at the same time not leave traces of evidence of tampering. An unusual request it may be, but I have tried everything but just cannot get the damn thing to brick. I wanted to brick it and then experiment on possible ways to unbrick it. And then if all failed, I was going to send it back to Samsung to see if they find any traces of deliberate tampering. Come on geniuses...I know you're out there somewhere

Rom manager flash the wong recovery fr other devce
Sent from my GT-S5830 using xda premium

DeadSp1d3r said:
Rom manager flash the wong recovery fr other devce
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
+10000000 it's so easy

Thanks. Just downloading a Rom for the S5830i to try out. Wouldn't you be able to re-flash the correct rom this way and get it to work again? Also if it does brick this way, would it leave traces when Sammy Techs investigate?

Gizmotech said:
Thanks. Just downloading a Rom for the S5830i to try out. Wouldn't you be able to re-flash the correct rom this way and get it to work again? Also if it does brick this way, would it leave traces when Sammy Techs investigate?
Click to expand...
Click to collapse
if you use rom manager samsung will not find out anything
if you flash other devices rom like acei on ace then it might brick but not for 100% sure but there is lots and lots of change that it will brick since it uses other flash scripts and binarys

Gizmotech said:
Yes, you read correct, I want to hard brick my phone not unbrick it but at the same time not leave traces of evidence of tampering. An unusual request it may be, but I have tried everything but just cannot get the damn thing to brick. I wanted to brick it and then experiment on possible ways to unbrick it. And then if all failed, I was going to send it back to Samsung to see if they find any traces of deliberate tampering. Come on geniuses...I know you're out there somewhere
Click to expand...
Click to collapse
Just download a galaxy s3 ROM and kernel...bricked right there.
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok Just tried to load up the firmware file for a Ace Plus on odin 4.38 but it wont accept it and comes back with "out of memory" error on the PC screen. Will try Rom Manager.

Bingo! Bricked it. I take it there's no way that I can attempt to revive it? Also I hope there is no traces of CWM Rom Manager, Superuser or Busybox

I don't know about the traces. But the only way to revive it is JTAG or replacement motherboard.
Sent from my GT-S5830 using xda premium

Next time, I'd rather make a backup in CWM and then restore it from another Recovery. What this does is delete the boot.img, so now your phone can't do anything and Samsung can't get any logs etc. from the device.
Also REMEMBER! Play dumb when taking it to the Samsung store! Don't mention Roms etc..

PulseDroid said:
Next time, I'd rather make a backup in CWM and then restore it from another Recovery. What this does is delete the boot.img, so now your phone can't do anything and Samsung can't get any logs etc. from the device.
Also REMEMBER! Play dumb when taking it to the Samsung store! Don't mention Roms etc..
Click to expand...
Click to collapse
Or rename a text file to boot.img and flash it as a ROM. This gives a totally faulty ROM.
Sent from my GT-S5830 using xda premium

Thanks guys, gonna give it in to service today and will keep you guys updated. I like the above method as it definitely would not leave traces of CWM, Superuser or Busybox. Duh, why didn't I think of that:silly: but too late now. maybe next time or someone else.

Gizmotech said:
Thanks guys, gonna give it in to service today and will keep you guys updated. I like the above method as it definitely would not leave traces of CWM, Superuser or Busybox. Duh, why didn't I think of that:silly: but too late now. maybe next time or someone else.
Click to expand...
Click to collapse
Do you not ever think there is someone in samsung softwere development reading this...
Sent from my GT-S5830

Best way to hardbrick your phone is to use rom manager
I got transformed into a potato while writing this post

athe_s said:
Do you not ever think there is someone in samsung softwere development reading this...
Sent from my GT-S5830
Click to expand...
Click to collapse
I do. That's the good thing about having a screen-name

Updates!!!
Gizmotech said:
Thanks guys, gonna give it in to service today and will keep you guys updated.
Click to expand...
Click to collapse
Any updates dude?

Wow. No wonder phone manufacturer doesn't honor warranty nowadays.
Seriously if u want to do such scam u should do it quietly without creating thread asking howto do so.

This is nice.... You can brick your phone in the last month of you year warranty and get a new phone/motherboard
Once my friends phone switched off suddenly... Non rooted stock
It happened suddenly and also out of warranty
She had to pay 5k to the Samsung people to get it repaired... And the plus point she got 14GB internal memory with the new motherboard
Her phone was the Samsung galaxy S i9000
it would've been done in free if she had warranty
So maybe you might get the GT S5830i.. The new version mother board or something
Best of luck

Gizmotech said:
Yes, you read correct, I want to hard brick my phone not unbrick it but at the same time not leave traces of evidence of tampering. An unusual request it may be, but I have tried everything but just cannot get the damn thing to brick. I wanted to brick it and then experiment on possible ways to unbrick it. And then if all failed, I was going to send it back to Samsung to see if they find any traces of deliberate tampering. Come on geniuses...I know you're out there somewhere
Click to expand...
Click to collapse
ohh !!!! so easy !!! install rom manager... 100% sure samsung won't find out what went worng with your ace ...

ysrini said:
Any updates dude?
Click to expand...
Click to collapse
Yes, the phone was repaired. They apparently replaced the motherboard.
an0nym0us_ said:
Wow. No wonder phone manufacturer doesn't honor warranty nowadays.
Seriously if u want to do such scam u should do it quietly without creating thread asking howto do so.
Click to expand...
Click to collapse
I would have done it quietly if I didn't need the help. Duh! Besides, I doubt this is the reason why they don't honour warranty. I think it is more to do with that they are greedy corporate companies who would rather save at any cost irrespective of whose fault it is. I mean why should they penalise someone because of something someone else done? After all you are all paying customers. They scam people everyday and no one complains. I guess people only complain when it happens to them. You can buy a new phone and have it go faulty within 2 months. Do you think you can get a new phone under warranty from them? No it will be a refurbished one and doesn't mater how much you scream and shout for a new one, they don't care. A neither do I.
jumbobombo said:
So maybe you might get the GT S5830i.. The new version mother board or something
Best of luck
Click to expand...
Click to collapse
No, I think it is the same motherboard. What I don't understand is, whether it is the same motherboard they repaired or a replacement one, as this phone was initially locked to the Three network. I had it unlocked. So a new motherboard would have meant that the phone would be locked again. But when I received it back, it would still accept any sims.

Ics v28e update without USB question

Can someone advise me on whether it is possible to update to the new Rom without the use of a USB.
My g\f's phone doesn't have usb its bust for some reason.
Is there any other way to load the latest 5.0 cwm, the new bootloader and then install a zip from cwm.
Any help is much appreciated.
Sent from my LG-P990 using xda app-developers app

monkeyass said:
Can someone advise me on whether it is possible to update to the new Rom without the use of a USB.
My g\f's phone doesn't have usb its bust for some reason.
Is there any other way to load the latest 5.0 cwm, the new bootloader and then install a zip from cwm.
Any help is much appreciated.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
1) You should clarify the title. Something like "How to update to v28E without USB". Imagine every thread like "LG P990 question", it's absurd.
2) You should tell us if you want the vlite or the full version of v28E.
3) CWM 5.0 is not the latest.
4) Yes, it is possible, put everything in the sd card =P.
Good luck.

Hello, apologies for that.
Thank you for the fast response.
I would like to install the full version, I am aware that you need to specifically partition the ad, but I can read grains thread for that.
Can I just confirm then, that if there is a zip for the new downloader, cwm and Rom in one zip.
That can be run from cwm?
Thank you
Sent from my LG-P990 using xda app-developers app

monkeyass said:
Hello, apologies for that.
Thank you for the fast response.
I would like to install the full version, I am aware that you need to specifically partition the ad, but I can read grains thread for that.
Can I just confirm then, that if there is a zip for the new downloader, cwm and Rom in one zip.
That can be run from cwm?
Thank you
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
First -- In case you want to go full metal on P990, that means repartitioning, new BB and full flash, you need to flash. There is no other way than using NVFlash, as described in lovely thread in development by Stephan G.
Reasons - reformatting is not easily done from within phone which runs on these partitions, same goes for reflashing recovery from within recovery.
Second -- not sure why without USB?
Third -- there is CWM-possible way by using TonypAndHarsh's vlite V28E rom, yet this goes without new BB and with possibility of no call audio issue.
So, to repeat my answer to your main point, no. There is no way to fully install new system/BB without USB connection and PC. You have to flash it.

Hello. I think you can instal the new ICS without your usb cable.
1. you need to instal rom manager from PlayStore and flash from here the CWM recovery. I recomend you to instal the version 5.2.0
2. Make a nandroid backup before you do something to your actual rom.
3. Use titanium backup to backup all your apps and settings.
4. Put ICS rom from here http://forum.xda-developers.com/showthread.php?t=1959545 in your sd card (i think you have at leat a card reader and on adapter to put your microsd card) and follow the isntruction from the download page.
Good luck!

Cool thank you will try tomorrow.
Ant
Sent from my LG-P990 using xda app-developers app

ergosum said:
1) You should clarify the title. Something like "How to update to v28E without USB". Imagine every thread like "LG P990 question", it's absurd.
2) You should tell us if you want the vlite or the full version of v28E.
3) CWM 5.0 is not the latest.
4) Yes, it is possible, put everything in the sd card =P.
Good luck.
Click to expand...
Click to collapse
I'm sorry but I disagree with you... I think that anyone that thinks about the title for 2 seconds can understand that if the guy is asking if it's possible to flash v28e without USB of course he means the "full" stock ICS leak, the one which requires you to redo your partitions and whatnot... the one that is only possible through nvflash, thus, it is not possible to update to v28e without USB.
Or, you could just reply... hey, it's not possible to flash "the real deal", but you can flash tonyp's "lite" version, which uses the old bootloader and a patched kernel (thus some bugs might come from that) and all you need to do is put the files in the sd card...
I don't know why you had to be so "blunt"...

LarsPT said:
I'm sorry but I disagree with you... I think that anyone that thinks about the title for 2 seconds can understand that if the guy is asking if it's possible to flash v28e without USB of course he means the "full" stock ICS leak, the one which requires you to redo your partitions and whatnot... the one that is only possible through nvflash, thus, it is not possible to update to v28e without USB.
Or, you could just reply... hey, it's not possible to flash "the real deal", but you can flash tonyp's "lite" version, which uses the old bootloader and a patched kernel (thus some bugs might come from that) and all you need to do is put the files in the sd card...
I don't know why you had to be so "blunt"...
Click to expand...
Click to collapse
Thank you for that information, I am currently trying to find out if there is a way to install the right version of CWM, then try to install the new bootloader from within CWM? I am not even sure if that is possible.
I think she is just going to have to get her phone sent back, the only problem is the o2x is discontinued, I doubt they will replace it or fix it. They will probably try and replace it, but only give her something that I wouldn't consider a good replacement. But we'll have to speak to her insurance company first.
I have seen these phones selling on ebay, they are about £100 from what I can gather, it depends what she wants to do. Could buy a new one and sell her one, just a shame really, i found another thread about the USB problem and they had to send it back and get it repaired, must be either a problem with the connection or the board, I would think the board as it charges fine, which is really weird.
Anyway, thank you for you help, i will keep searching to see what i can find.

monkeyass said:
Thank you for that information, I am currently trying to find out if there is a way to install the right version of CWM, then try to install the new bootloader from within CWM? I am not even sure if that is possible.
I think she is just going to have to get her phone sent back, the only problem is the o2x is discontinued, I doubt they will replace it or fix it. They will probably try and replace it, but only give her something that I wouldn't consider a good replacement. But we'll have to speak to her insurance company first.
I have seen these phones selling on ebay, they are about £100 from what I can gather, it depends what she wants to do. Could buy a new one and sell her one, just a shame really, i found another thread about the USB problem and they had to send it back and get it repaired, must be either a problem with the connection or the board, I would think the board as it charges fine, which is really weird.
Anyway, thank you for you help, i will keep searching to see what i can find.
Click to expand...
Click to collapse
Just cause you didnt mention it before, but are you running a hacked version of ICS right now on the phone? If you are, it could be a matter of the ADP drivers on your computer? If it was a stupid idea sry. It was just something that pop'd into my head

headshot21 said:
Just cause you didnt mention it before, but are you running a hacked version of ICS right now on the phone? If you are, it could be a matter of the ADP drivers on your computer? If it was a stupid idea sry. It was just something that pop'd into my head
Click to expand...
Click to collapse
Unfortunately not, it is running a version of gingerbread, can't remember which one.

monkeyass said:
Unfortunately not, it is running a version of gingerbread, can't remember which one.
Click to expand...
Click to collapse
I got a bug on my O2X USB as well, and I managed to solve it temporary, (the bug comes back after some time, but the process has worked for me everytime the bug comes back, I'm currently testing to try to identify the cause of the bug), it is kind of a long process but I could get back my usb sync, if you want I made a tutorial of what I exactly did, after this process you can install any stock or custom rom without any problem just make sure to follow the instructions as they are described
http://forum.xda-developers.com/showthread.php?t=1981359

ocr66 said:
I got a bug on my O2X USB as well, and I managed to solve it temporary, (the bug comes back after some time, but the process has worked for me everytime the bug comes back, I'm currently testing to try to identify the cause of the bug), it is kind of a long process but I could get back my usb sync, if you want I made a tutorial of what I exactly did, after this process you can install any stock or custom rom without any problem just make sure to follow the instructions as they are described
http://forum.xda-developers.com/showthread.php?t=1981359
Click to expand...
Click to collapse
Thank you, tried your fix but unfortunately didn't work, looks like it will have to be sent back.
thank you though

monkeyass said:
Thank you, tried your fix but unfortunately didn't work, looks like it will have to be sent back.
thank you though
Click to expand...
Click to collapse
Too bad to hear it didn't worked, do you mind if I ask, what exactly failed? I mean, it would be great to have some feedback of what you did and where you got stuck, so I might make some updates of the post, or upload another backup, or so
If you have any doubt about my post, I would be pleased to help you with that
thanks for giving it a try
cheers

Hi
I downloaded a stock Rom that had been modded.
So I could be sure that I would have cwm in case anything went wrong.
Rom loaded and was able to get into the secret menu.
I will say that under USB connection type there was misspelling where it said:
LG USB adnroid
Not sure if that would affect it.
I selected that item.
Then went to port.
Selected the different options in ordered and waited about 10 seconds on each turn, then pressed find any changes in device manager unplugged and plugged the USB.
Then tried in different orders but with not luck.
Took the battery out and tried holing the vol up down the plugging in USB but to no avail.
Then pressed power and vol down.
The phone tuned on and showed LG sign then switched off.
I tried pressing check any changes as the LG sign came on but nothing.
Then tried nvflash as the LG sign came on but nvflash showed no connection.
Very weird, definitely dead but still charges, doesn't make sense.
Oh well
Ordered an atrix with work and play kit for 68 quid, has a broken digitizer which will cost 20 pound, on average, off ebay.
Thanks for the help though.
May take the 2x apart when new phone comes and see if there's any physical damage on te board.
Sent from my LG-P990 using xda app-developers app