Curious - Sony Xperia S, Acro S, Ion

What would happen if I flash another phones FTF?
like maybe the X10's or the Arcs etc
would my phone blow up, or get bricked?

Won't flash.
Sent from my LT28at using Tapatalk 2

Even if it did, could hard brick your phone. The coding between phones is not normally compatible unless you are talking something like the Galaxy S series where the I9000 rom can be flashed on to some of it sister phones like the Captivate, but the orientation doesn't work along with a few other things.

Related

flashing's bad effects

got my arc bl unlock,and rooted,begin flashing and flasing all kind of kernels and custom roms(thnks to all devs here,for making our arc better than sgs2),so are there any bad effects to my phone?like hardware or somethings?
Sent from my LT18i
If you haven't noticed any thing wrong with your phone yet then your fine unlike me which has a slight glitch in my firmware after flashing the update but it's nothing serious so I just live with it rather then doing the hole process again.
As long kernel works you are fine
Hardware will not take easily bad effect, unless some overclocking does some harm.
Generally speaking yes. NAND wears out eventually when you always flash/write to it.
Good news is... You would probably not need/changed your phone by then before you wear that out.
Or should I say probably would take you 100,000+ times of flashing before you wear it out.
ROMs and kernels won't harm the device.
But when you oc top much that might harm.
1.4-1.5GHz are said to be safe for Arc and a bit more for Arc S
Sent from my iPad 2 using Tapatalk
thank for the advice,im just curious about the effect,if all of you said "okay",then ill keep on flashing
Sent from my LT18i

ICS Leaks Causing Bricks?! Updated With More Info.(New Link)

http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
Maybe someone who is a little more savvy in this field could take a look?
Here is a very good article and discussion about the issue:
http://forum.xda-developers.com/showthread.php?t=1644364
Sent from my SGH-T989 using xda premium
this is kinda scary but so far I never had any problem
We don't even have any kernel source. There is a leaked kernel but that didn't cause any brick in our devices. Also note that the article does not mention sgh t989 or sgh 727 and all its sub variants. If this was the case for us you would see many more "[Q] plz halp I haz brick " threads
Sent from my SGH-T989 using XDA
Hey guys. I just came over from the Sprint version of this phone (Epic 4G touch), and while I know that this article dosen't say that it pertains to our device specifically, one of the devs over there got in touch with samsung about the issues. You can see their progress here:
http://forum.xda-developers.com/showthread.php?t=1644364
For those who don't want to read (and I don't blame you if you don't want to, it's heavy stuff and I needed to have it explained to me), long story short: The memory chips (known as the EMMC) in the phone have their own firmware embedded in them, independent of the ROM, kernel, modem, etc. In that firmware, there's a bug that writes a string of zeros to an area of the firmware itself, kind of a self distrusting thing. It's only for certain revisions of the EMMC firmware, and it's only triggered by a specific low-level wipe function that is commonly used in recoveries (I'm not sure which, one of the partition wipes I think), and it for some reason seems to happen more with an ICS based kernel more than in a GB.
Given the nature of EMMC chips and the fact that multiple devices might share these same physical type of EMMC memory chips, it's hard to say how many different kinds of phones and devices might be affected, but it's safer to assume that we might be, rather than to think that we're safe based on this article alone.
There's no official solution as of yet, as far as I know. Samsung has started to patch their 4.x kernels to work around this specific wipe function, thus avoiding triggering the bug, and I think this is because rewriting the EMMC firmware itself is more risky and perhaps harder to do on a wide scale, but again, I'm not sure of their reasons. But, we do know that they're working to find some way around the bugs, and those who built custom kernels also removed/modified that wipe command to work around this bug with success.
Again, I know this doesn't say that it applies to our phones, but because of what was discovered on the Epic 4G touch, I believe that it *may* apply to many, many Samsung phones and devices, and just to be safe, I figure I should share this with you all.
The solution that we were using for time being was: never, ever do any recovery functions from a ICS based kernel/recovery. Always ODIN a GB based kernel/recovery to do what you need to do, then flash the proper ICS back. Kind of tedious, but it worked and prevented me from ever bricking when a LOT of other people were. Food for thought, everyone
TL;DR: You should probably avoid doing anything in an ICS based recovery/kernel on any Samsung device until we hear from them that they've worked out this bug.
kahm said:
Hey guys. I just came over from the Sprint version of this phone (Epic 4G touch), and while I know that this article dosen't say that it pertains to our device specifically, one of the devs over there got in touch with samsung about the issues. You can see their progress here:
http://forum.xda-developers.com/showthread.php?t=1644364
For those who don't want to read (and I don't blame you if you don't want to, it's heavy stuff and I needed to have it explained to me), long story short: The memory chips (known as the EMMC) in the phone have their own firmware embedded in them, independent of the ROM, kernel, modem, etc. In that firmware, there's a bug that writes a string of zeros to an area of the firmware itself, kind of a self distrusting thing. It's only for certain revisions of the EMMC firmware, and it's only triggered by a specific low-level wipe function that is commonly used in recoveries (I'm not sure which, one of the partition wipes I think), and it for some reason seems to happen more with an ICS based kernel more than in a GB.
Given the nature of EMMC chips and the fact that multiple devices might share these same physical type of EMMC memory chips, it's hard to say how many different kinds of phones and devices might be affected, but it's safer to assume that we might be, rather than to think that we're safe based on this article alone.
There's no official solution as of yet, as far as I know. Samsung has started to patch their 4.x kernels to work around this specific wipe function, thus avoiding triggering the bug, and I think this is because rewriting the EMMC firmware itself is more risky and perhaps harder to do on a wide scale, but again, I'm not sure of their reasons. But, we do know that they're working to find some way around the bugs, and those who built custom kernels also removed/modified that wipe command to work around this bug with success.
Again, I know this doesn't say that it applies to our phones, but because of what was discovered on the Epic 4G touch, I believe that it *may* apply to many, many Samsung phones and devices, and just to be safe, I figure I should share this with you all.
The solution that we were using for time being was: never, ever do any recovery functions from a ICS based kernel/recovery. Always ODIN a GB based kernel/recovery to do what you need to do, then flash the proper ICS back. Kind of tedious, but it worked and prevented me from ever bricking when a LOT of other people were. Food for thought, everyone
TL;DR: You should probably avoid doing anything in an ICS based recovery/kernel on any Samsung device until we hear from them that they've worked out this bug.
Click to expand...
Click to collapse
Finally someone with a brain! Thanks for the post
Sent from my SGH-T989 using xda premium
Scary stuff indeed, has anyone confirmed that our devices (T989) is affected by this bug?
Back on the original Epic we used Odin to get the next version. I think it was 2.1 to 2.2 roms. I've always wondered how safe it was to revert to GB by flashing after installing ICS
Sent from my SGH-T989 using xda premium
[Q] plz halp I haz brick
Disregard. Funny how you figure out your issue just seconds after you post and open yourself up to ridicule.
DOH!
mharmon said:
I seem to have hard-bricked my SGH-T989 phone after flashing task650-aokp-Build-36. I don't know if it's a superbrick, but nothing I can do seems to make any difference. The phone does not seem to respond and does not seem to power off, power on or go into download mode. I have swapped with a known good battery and I know that's not the issue. I've tried using a USB jig and that doesn't help. I've contacted Samsung and I should be shipping it to them Monday.
If anyone has any advice, I'm willing to try anything otherwise I'm going to take my lumps and ship my phone off.
Click to expand...
Click to collapse
Pull your battery sd card and sim card out. leave phone sitting with everything pulled for about an hour. put it back together and try again. make sure your battery is charged for sure. it would suck if it was nothing but a dead battery
Sent from my SAMSUNG-SGH-T989 using xda premium
Micronads said:
Pull your battery sd card and sim card out. leave phone sitting with everything pulled for about an hour. put it back together and try again. make sure your battery is charged for sure. it would suck if it was nothing but a dead battery
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for the quick response. I've tried pulling the battery, USB jig, etc. and can't get it to power on, off or go into download mode. I know what I did wrong. I made a rookie mistake and flashed a ROM meant for my AT&T I777. I feel stupid for bricking my phone.
mharmon said:
Thanks for the quick response. I've tried pulling the battery, USB jig, etc. and can't get it to power on, off or go into download mode. I know what I did wrong. I made a rookie mistake and flashed a ROM meant for my AT&T I777. I feel stupid for bricking my phone.
Click to expand...
Click to collapse
Sounds like you are fizzucked then. Sorry to hear that. That is what sucks about having different phones and flashing stuff. Got to keep track of what is what.
Sent from my Galaxy SII T-mobile using xda premium
Micronads said:
Sounds like you are fizzucked then. Sorry to hear that. That is what sucks about having different phones and flashing stuff. Got to keep track of what is what.
Sent from my Galaxy SII T-mobile using xda premium
Click to expand...
Click to collapse
Yeah sounds dead to me. Send in for warranty. Oh well, stuff happens. Good luck to you!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Id rather risk bricking than rock without 4.04
Sent from my SGH-T989 using xda premium
Nobody has said it is necessary applicable to this device.
jim93 said:
Nobody has said it is necessary applicable to this device.
Click to expand...
Click to collapse
You're right, it doesn't say it's applicable to our device. But it also doesn't say our device is one of the safe GS2 variants. As you can see in my signature, I'm also using 4.0.4. And if you read my post history, I recommend it to everyone. I'm just saying that it hasn't been proven safe yet, but there's also no proof its dangerous either.
Sent from my SGH-T989 using xda premium
ICS has been flashed to these phones probably a half million times by now. If it was causing bricks we would have heard about it.
Sent from the iPhone graveyard.
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
kahm said:
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
Click to expand...
Click to collapse
Also, people should know that the listed phones in the OP are Exynos based and T989, i727/r and i717 are Qualcomm based. This has been discussed in the skyrocket forums and some devs have explained that.
Just my 2 cents.
kahm said:
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
Click to expand...
Click to collapse
The brick in this thread was due to flashing an i777 rom to a t989. Flashing an i777 rom to t989 regardless of OS will brick your phone.
It seems to be all exynos based, but thanks for the heads up, man.

[Q] Anyone ever flashed a Verizon S3 ROM?

LiquidSmooth 4.2.2 ROM is available for both the ATT and Verizon S3's. I have the ATT and I regularly flash my Cousin and his wife's phones for them. But they're four hours away and I won't see them again for a couple months.
What I've done in the past with my ATT Skyrocket was to flash a TMobile Hercules ROM on it and customize it the way it needs to be, then just sent it to them to restore from CWM.
But, the Skyrocket & Hercules were essentially the same phone. So now that we all have the S3, and they are on Verizon now, I'm not sure how well I'll get away with this.
Basically I flash the ROM on my phone. Install all their apps. Set up all little tweaks & customizations. Then do a Nandroid for them to restore on their phone. Makes it a nice and TIGHT phone. They love it, and I get killer BBQ & Beer & Pool fun when I go visit every few months.
The Wife's phone has been having issues, so it's time for a new flash. And they're still on 4.1.1 ROM's.
I know the TMO & ATT S3's can share the same ROM. But I don't want to brick my ATT S3 with a Verizon S3 ROM flash, even if it's just for a couple hours while I set it up. Wondering if it's absolute trouble waiting to happen?
Its different. I had to root my friends vzw s3 and the whole process is different, and I'm sure the partitions are different.
Sent from my SGH-I747 using xda app-developers app
They are already rooted (TWRP). But that's a good point about the partitioning.
Definitely not going to do something unless someone else has already leapt from this bridge before me....
Nope. I wouldn't try it either.
Sent from my SGH-T999 using xda premium
Don't do it. You will brick their phones. The system files are very different. with different hardware as well. The antenna mainly. As well as a special dialer app and files to work on the out dated cdma network
Wayne Tech S-III
It might work, you wouldnt have signal.... I wouldnt try it though.
Sent from my SAMSUNG-SGH-I747 using xda premium
Bootloader is different. Kernel is different. The partitions may be even set up differently. Different radio bands, RILs and other items will cause it to brick.
Maybe it's the allergy meds I'm on, or maybe I just felt like testing the boundries.
Just flashed AOKP's Verizon 4.2.2 3/5/13 release on my D2ATT.
Phone still boots & works.
Well, data doesn't work (as you guys said it wouldn't). But WiFi does work.
Rebooted and installed gapps. Set up a bunch of settings. So far, so good. Though Play Store does crash. Can't get past that so far.
EDIT:
I just flashed the Verizon version of Slim Bean 4.2.2.
It had an option for me to not only add an APN, but also to select GSM. The AOKP did not.
After setting up these two things, data is working fine. Made a phone call too.
Playstore working also.

Sleep of Death

I'm root and unlocked bootloader and I want to know if xperia ZL suffers from "Sleep of Death" issue like the Z...and does the fix applied to ZL as well..
Cause my zl kinda suffer from it...after a reboot the phone shut itself..it will stay longer if I connected to a charger but after a long period it will shut it self again...I think it's a software issue cause when in cwm, it doesn't shut down...but I have formatted to factory state and everything stock but the problem still persist...
I'm on latest 2.67 firmware and stock kernel but will relocking the bootloader will save my phone...if not, I'm gonna try to claim warranty and hopping they don't detect I'm already void the warranty even I'm relock again...
Hope someone can help....tq
Sent from my iPhone using Tapatalk Pro
martin132014 said:
I'm root and unlocked bootloader and I want to know if xperia ZL suffers from "Sleep of Death" issue like the Z...and does the fix applied to ZL as well..
Cause my zl kinda suffer from it...after a reboot the phone shut itself..it will stay longer if I connected to a charger but after a long period it will shut it self again...I think it's a software issue cause when in cwm, it doesn't shut down...but I have formatted to factory state and everything stock but the problem still persist...
I'm on latest 2.67 firmware and stock kernel but will relocking the bootloader will save my phone...if not, I'm gonna try to claim warranty and hopping they don't detect I'm already void the warranty even I'm relock again...
Hope someone can help....tq
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
Well, im 100% sure that problems on phone comes put when people root, change firmware, custom. etc all kind of (pirate stuff) not officilly from sony to the phone, i have always been stok official on every phone i had ( S2, S3, NOTE2, ZL) and nothing has happened to me with sudden death or sleep of death.
I just want to know WHY PEOPLE KNOWING ALL THIS ISSUES ON CUSTOM, LIKE BUGS ETC THEY STILL LIKE CUSTOM.... lol thats like to be MASOCHIST..
STICK to the stock.
danieldp1990 said:
Well, im 100% sure that problems on phone comes put when people root, change firmware, custom. etc all kind of (pirate stuff) not officilly from sony to the phone, i have always been stok official on every phone i had ( S2, S3, NOTE2, ZL) and nothing has happened to me with sudden death or sleep of death.
I just want to know WHY PEOPLE KNOWING ALL THIS ISSUES ON CUSTOM, LIKE BUGS ETC THEY STILL LIKE CUSTOM.... lol thats like to be MASOCHIST..
STICK to the stock.
Click to expand...
Click to collapse
I agreed with you, I always been stock, no root or unlocked bootloader. I rather be with a phone that have warranty just in case something happen, than been with a modified phone, death and not warranty if Sony found out.
Sent from my C6506 using xda app-developers app
Every phone I had I've modded the **** out of it. Yet I never had the problem that I've broken the phone. I don't know how people get their phone destroyed, the only reason I can think of is the fact that people don't read carefully and miss important details in a description or tutorial.
Sent from my C6503 using xda app-developers app
maclancer said:
I agreed with you, I always been stock, no root or unlocked bootloader. I rather be with a phone that have warranty just in case something happen, than been with a modified phone, death and not warranty if Sony found out.
Sent from my C6506 using xda app-developers app
Click to expand...
Click to collapse
Well that's good for ordinary people with ordinary stuff on their hand...other people doesn't like that and I'm one of it...well this is personal liking anyway...
I have used many android phone in range of model including iphone and all root and jailbreak...and some people love the change and love to put their phone to the limit...
Only recent phone I have problem with and old model don't have any problem...
Sent from my iPhone using Tapatalk Pro
einfachgaer said:
Every phone I had I've modded the **** out of it. Yet I never had the problem that I've broken the phone. I don't know how people get their phone destroyed, the only reason I can think of is the fact that people don't read carefully and miss important details in a description or tutorial.
Sent from my C6503 using xda app-developers app
Click to expand...
Click to collapse
I'm considered myself an experience on rooted phone...always double check when trying to flash or modded something....and always successful on it...if I brick it I always recover it again...only the current flagship I got problem with...I think this is a problem with some Sony phone that have problem on some of it...that something they miss...I work in Japanese factory and I know how they work....
Sent from my iPhone using Tapatalk Pro
martin132014 said:
I'm considered myself an experience on rooted phone...always double check when trying to flash or modded something....and always successful on it...if I brick it I always recover it again...only the current flagship I got problem with...I think this is a problem with some Sony phone that have problem on some of it...that something they miss...I work in Japanese factory and I know how they work....
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
bad luck you got a defective phone, cause mine is working like new with 0 issues.
I had rooted many other phones and also moding, but the truth is that nothing is much better than STOCK = 0 BUGS, and troubles.
danieldp1990 said:
bad luck you got a defective phone, cause mine is working like new with 0 issues.
I had rooted many other phones and also moding, but the truth is that nothing is much better than STOCK = 0 BUGS, and troubles.
Click to expand...
Click to collapse
Well that's true...I'm root and modded my phone always use stock rom...I am not a fan of custom rom but always modding to the limit...always trying to put something on to maximize it...
Bad luck or not, today I'm trying my luck again to go to Sony center to claim warranty on my defective phone...I have made a factory reset and relock my bootloader...so hoping Sony wont find out...if they did...moneys going down the drain...
Sent from my iPhone using Tapatalk Pro
I think we are to premature to say about issues with root, modified or custom roms because the Zl, Z ,Z1 they are babys come out few mounts ago and all the developers are trying hard to make it fly. I remember my HD2, I get that phone after 2 years of his release and I was flashing tons of roms everyday and I find many powerful and stable roms. So be patient.
eclyptos said:
I think we are to premature to say about issues with root, modified or custom roms because the Zl, Z ,Z1 they are babys come out few mounts ago and all the developers are trying hard to make it fly. I remember my HD2, I get that phone after 2 years of his release and I was flashing tons of roms everyday and I find many powerful and stable roms. So be patient.
Click to expand...
Click to collapse
Well, maybe but i think the problem is not in root or any roms...the phone is just defective..i got mine back from repair and work ok again...
And thats true about old phone...i used some HTC, and Sony's old phone, always flash something, and no problem occur...only todays phone, i always encounter many defects on it...great technology, but also fragile...
Sent from my C6502 using XDA Premium 4 mobile app
as far as i understand, its not because u rooted or unlocked but bcuz of a problem with the battery management syste(BMS).
there appears to be sum fault with battery or the bms, which causes the phone to shutdown.
unfortunately, the only solution is to change the battery. u will have to return ur phone to sony. but to claim warranty, u must unroot and relock the bootloader.
mind you, there is only a small number of phones with this problem.
this same issue happend with my ZL too. i returned and within one week, they returned a brand new phone to me.
mine was fully stock, locked bootloader and unrooted(the previous and the newer too)
new is working awesome.
hope this helps, if it does, u know where the thanks button is!
control freak said:
as far as i understand, its not because u rooted or unlocked but bcuz of a problem with the battery management syste(BMS).
there appears to be sum fault with battery or the bms, which causes the phone to shutdown.
unfortunately, the only solution is to change the battery. u will have to return ur phone to sony. but to claim warranty, u must unroot and relock the bootloader.
mind you, there is only a small number of phones with this problem.
this same issue happend with my ZL too. i returned and within one week, they returned a brand new phone to me.
mine was fully stock, locked bootloader and unrooted(the previous and the newer too)
new is working awesome.
hope this helps, if it does, u know where the thanks button is!
Click to expand...
Click to collapse
Was going to say I haven't experienced this issue... and my phone is rooted and unlocked...

Is it possible to install Ubuntu Phone OS?

Hello,
Is it possible to install Ubuntu Phone OS (not Ubuntu Touch) on a Sprint (technically Virgin Mobile) Galaxy S3?
Thank you.
Maxwell175 said:
Hello,
Is it possible to install Ubuntu Phone OS (not Ubuntu Touch) on a Sprint (technically Virgin Mobile) Galaxy S3?
Thank you.
Click to expand...
Click to collapse
I have never tried anything of the sort, but considering you can flash and of the generic d2lte roms to this phone (which is technically d2spr, whether you have sprint/boost/virgin, all three are the same device), I would say that if there's any talk of doing it on any other S3, then it would seem to be totally possible. If you have any luck with this let me know, I'd like try it. Also I have a spare mainboard for my l710, so id be more than willing to take the leap of faith and flash it first
Sent from my SPH-L710 using Tapatalk
fjbredt88 said:
I have never tried anything of the sort, but considering you can flash and of the generic d2lte roms to this phone (which is technically d2spr, whether you have sprint/boost/virgin, all three are the same device), I would say that if there's any talk of doing it on any other S3, then it would seem to be totally possible. If you have any luck with this let me know, I'd like try it. Also I have a spare mainboard for my l710, so id be more than willing to take the leap of faith and flash it first
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
They seem to have ported it to Verizon Galaxy S3 here: http://forum.xda-developers.com/galaxy-s3/help/ubuntu-phone-os-ported-to-galaxy-s3-t2178134
Maybe it could be ported to sprint?
Judging by looking at it, the only issue would be it to recognize our Sprint modem, as it slightly differs (driver-wise) from the Verizon model. But I'm going to play around and see if I can install it on my spare Sprint s3 mainboard. I'll let you know if I have any luck.
Sent from my SPH-L710 using Tapatalk
Hello fellows,
I have been running the CyanogenMod, Nightlies. (5.1.1) on Virgin/Sprint network, for well over a month now! Can say, they do seem to run rather well, right out of the box (Have played with Buid Prop a bit, running even better)
Any who, I have been looking and a working on something like this... UBUNTU PHONE OS, on our Galaxy S3's.....
Never really knew why/what/who ruined the Ubuntu Phone a few years ago.... Was really into that, but it never came out.... (bet someone lost thier job on that deal.... Who wants a phone to work like a reguler PC??? lmao)
PLEASE keep this going. I willing to test just about anything. Dont have an extra board, but do have an extra phone, (screen is jacked, but can boot and run)
....fingers crossed here!!!!
So far everything I tried soft-bricked the phone. Not even a dang boot-loop. Lol.. I'm gonna keep at it though.. I'll update if I have any luck.

Categories

Resources