Related
What sort of ROM would people like to see for the A100?!? Any particular wishes?
Personally I'd like to see a ROM that gives you slightly better battery life and the ability to under and overclock. (Tegra2 is pretty good for overclocking, no?)
That way you could set it for 1200mhz or higher for when you really need some speed, and underclock it to 600 or 800 mhz for a nice long plane trip. You should still be able to watch a couple of movies, but you'll get two hours more batterylife or thereabouts.
What I'd REALLY REALLY like to see in a future ROM, is a port of either HTCs tablet ROM or the Touchwiz ROM from the Galaxy 10.1.
Nothing beats Samsungs Touchwiz for smoothness from what I've seen, and since they use the same Tegra SoC it shouldn't be too hard to port, eh?
The HTC ROM would be pretty cool to have as an option, especially if it would be able to use the HTC Watch app.
What do you guys hope for?
First A500 ROM (Taboonay, Villain...) should be port to A100 easily ! (I hope !)
Then I'm not waiting at all for touchwiz or sense ROM cause Honeycomb is already nice...
The biggest thing on my wish list is native bluetooth PAN like the Xoom has. And tun.ko built into the kernel.
As for what ROM With ICS so close is it worth the effort to build a 3.2 ROM other then to get working drivers?
First we need a recovery. I have tried the A500 CWM with no luck. I have also contacted Koush via his blog http://www.koushikdutta.com/ requesting help with porting CWM to the A100 with no response. Anyone know how to get the ball rolling for a recovery?
painter_ said:
The biggest thing on my wish list is native bluetooth PAN like the Xoom has. And tun.ko built into the kernel.
As for what ROM With ICS so close is it worth the effort to build a 3.2 ROM other then to get working drivers?
First we need a recovery. I have tried the A500 CWM with no luck. I have also contacted Koush via his blog http://www.koushikdutta.com/ requesting help with porting CWM to the A100 with no response. Anyone know how to get the ball rolling for a recovery?
Click to expand...
Click to collapse
Porting CWM is not the problem. In fact, the A500 CWM may work, if you can get it booted. The problem is, when you flash the recovery partition with CWM, you can no longer boot into recovery due to a checksum mismatch that the bootloader performs. The bootloader is encrypted, so can't modify it.
<Sepculation>
I am wondering though.. I believe the A100 and A500 are very similary in hardware (except the screen size). I wonder if it's possible to flash the bootloader from A500 to the A100. Kind of like downgrading the A500 from the new 3.2 back to 3.01. hmm.... i may have to visit best buy.
</speculation>
Euclid's Brother said:
Porting CWM is not the problem. In fact, the A500 CWM may work, if you can get it booted. The problem is, when you flash the recovery partition with CWM, you can no longer boot into recovery due to a checksum mismatch that the bootloader performs. The bootloader is encrypted, so can't modify it.
Click to expand...
Click to collapse
so itsmagic could be helpfull for this ?
sebennett said:
so itsmagic could be helpfull for this ?
Click to expand...
Click to collapse
Nope. Its different.
Sent from my A500 using Tapatalk
JusThinK said:
I would love to have 3G support via Micro USB, if it can be done..
Forum just created, we will get lot's of suff.. My A100 on it's way to India from US , will get it in 1/2 weeks.
Thanks
JusTy
Click to expand...
Click to collapse
Look forward to.Thanks
More USB goodies, and make it run games/apps as well as well as the A500. I want my Stupid Zombies and Dolphin for Pad back. Better battery life would be swell too.
Sent from my A100 using XDA Premium App
So my acer a100 is rooted (since day one), I'm guessing there is no need to do a NAND unlock on these?
Also, what are the honeycomb roms (is there any?)
When i had my DINC i liked CM7 but i really dont want android < 3.2 on my tab (seems like a step backwards).
painter_ said:
The biggest thing on my wish list is native bluetooth PAN like the Xoom has. And tun.ko built into the kernel.
As for what ROM With ICS so close is it worth the effort to build a 3.2 ROM other then to get working drivers?
First we need a recovery. I have tried the A500 CWM with no luck. I have also contacted Koush via his blog http://www.koushikdutta.com/ requesting help with porting CWM to the A100 with no response. Anyone know how to get the ball rolling for a recovery?
Click to expand...
Click to collapse
You have a great point here. With ICS just around the corner for this device (January IIRC) any Devs would be probably rather wait to put their effort in once that arrives.
I think it will take many polite requests for someone (Developer) to grab hold of this one. Or one of them to buy one and want to hack the heck out if it for themselves as well as us. I'm an avid hacker/tester but not a developer sadly. I wish I had more time to learn code and to develop. However, 60 hours a week (6 days) of work with a wife and 3 kids limits my free considerably.
Devs will defenetly wait for the ics to be release
Until ICS arrives I am happy with being able to root the device without unlocking the boot loader. But having a custom recovery like CWM would be great, let's wait and see what the Devs do after ICS arrives.
A solid AOSP ICS and ICS MIUI with CWM just to back up would be AMAZING...
jay_993 said:
A solid AOSP ICS and ICS MIUI with CWM just to back up would be AMAZING...
Click to expand...
Click to collapse
Dude, hear hear. Once I have CWM on my tablet, I'm gonna be such a happy customer. Especially if some dev wants to port 4.0-based MIUI to it...that would be phenomenal.
DaveRichardson said:
Dude, hear hear. Once I have CWM on my tablet, I'm gonna be such a happy customer. Especially if some dev wants to port 4.0-based MIUI to it...that would be phenomenal.
Click to expand...
Click to collapse
I mean. Have you seen the previews of MIUI 4.0?! I thought AOSP ICS looked stunning. MIUI does it nice as well!! haha
I would just love to be able to get a Clockworkmod Recovery running so I can do a Nandroid backup and stuff like that.
best rom
E A G L E B L O O O O O O O D ! ! ! (greatest roms ever made)
---------- Post added at 10:15 AM ---------- Previous post was at 10:10 AM ----------
Mordak said:
I would just love to be able to get a Clockworkmod Recovery running so I can do a Nandroid backup and stuff like that.
Click to expand...
Click to collapse
i like your pic...ironwars??? (Great game)
Clockwork would be great so we can have the confidence to mess up our machines
The encrypted locked bootloader hinders devs from doing dev work on it. With amazing hardware, I'm hoping the devs will work this after Acer rolls out ICS next month, hopefully. I really like to have a custom recovery so I can at least do a nandroid backup in case I eff'd up even the stock ROM.
For ROMs I like, definitely CM or MIUI.
Sent from my A100 using XDA App
like everyone has already said I'd like to make backup and stuff
but I'd like to see cm7 or 9 on this one
and able to over lock that ***** lol
Sent from my A100 using xda premium
I would love to see a sense port from like the HTC Flyer , will probably never happen even when we unlock the bootloader but well, this thread is about what we would like to see
Sent from my Iconia A100 using Tapatalk
Is there anyone who has made any headway in their research on cracking or unlocking the bootloader? My short research confirms that it is using a 256-bit encryption algorithm, but I've not identified the algorithm used, nor do I think it would matter, as I really have no intention of doing a cryptanalysis on something that strong and I doubt anyone else would, either. Out of curiousity, though: anyone know offhand?
I'm curious to know what methods you guys are attempting to employ and what, if any, other research has already been done. I'd like to help, where I can.
**** if i knew more about it id take a crack at it but unfortunately i lack the skills required. Guess its time to learn huh.
grayn0de said:
Is there anyone who has made any headway in their research on cracking or unlocking the bootloader? My short research confirms that it is using a 256-bit encryption algorithm, but I've not identified the algorithm used, nor do I think it would matter, as I really have no intention of doing a cryptanalysis on something that strong and I doubt anyone else would, either. Out of curiousity, though: anyone know offhand?
I'm curious to know what methods you guys are attempting to employ and what, if any, other research has already been done. I'd like to help, where I can.
Click to expand...
Click to collapse
Vache and I worked on it yesterday for about 6 hours. We didn't get it cracked yet but we are making progress. Don't bother with trying to get your SBK (secure boot key) because A: you won't be able to crack the encryption & B: we have a "secret" way to extract it from the tablet (shhhhh!) (and no, we won't share it just yet, sorry )
timbrendelaz said:
Vache and I worked on it yesterday for about 6 hours. We didn't get it cracked yet but we are making progress. Don't bother with trying to get your SBK (secure boot key) because A: you won't be able to crack the encryption & B: we have a "secret" way to extract it from the tablet (shhhhh!) (and no, we won't share it just yet, sorry )
Click to expand...
Click to collapse
Ahh. Yes, it looks like I noticed vache's call for test in the ROOTED thread a bit late, sent him a PM a couple hours ago.
If you guys need another "Linux guy" or a fresh set of eyes, feel free to PM me. I'll keep poking about the system on my own, in the mean time, as well. Good luck on the research!
This is great news!
This is awesome. Keep up the good work.
Sent from my PG86100 using Tapatalk
timbrendelaz said:
Vache and I worked on it yesterday for about 6 hours. We didn't get it cracked yet but we are making progress. Don't bother with trying to get your SBK (secure boot key) because A: you won't be able to crack the encryption & B: we have a "secret" way to extract it from the tablet (shhhhh!) (and no, we won't share it just yet, sorry )
Click to expand...
Click to collapse
reallllyy appreciate the times you guys are putting into this.
I'm curious how the bootloader is different from the acer iconia a500? If it is not, couldn't we use the same technique from there?
will this thing never gonna get unlocked?
i think i should just sell that piece of ****
TheUndertaker21 said:
will this thing never gonna get unlocked?
i think i should just sell that piece of ....
Click to expand...
Click to collapse
Go for it, the Developers of the XDA community don't owe you anything and if this is how you are going to help (by complaining) then you are better off selling this wonderful device. Patience is a key thing with this device, just like the atrix its just a matter of time.
Lightsword1942 said:
I'm curious how the bootloader is different from the acer iconia a500? If it is not, couldn't we use the same technique from there?
Click to expand...
Click to collapse
Yes, different bootloader, due to both having different versions of hc. The A100 is newer, has newer programming, and leaves us with a different place to start. I myself have tried putting every single script of my A100 into an emulator on my PC to attempt to "reverse engineer" the bootloader to try to decrypt it, but that was unsuccessful for many reasons.
ummmmm............ could you repeat that?
Rather new to androids but I would consider myself a Linux guru. I just picked up an A100 on an open box sale and I would like to get involved in cracking the bootloader on this device. I am a professional low level developer and I have contributed to the development of several major open source projects including Gentoo and Fedora.
I also own a new Samsung Nexus S. Whose working on this now? Is there anything you need help with?
vamman said:
I also own a new Samsung Nexus S. Whose working on this now? Is there anything you need help with?
Click to expand...
Click to collapse
Our biggest challenge with this device is the 256bit encrypted bootloader from hell.. if you know a cryptologist, or some one at acer, that would help a ton
Sent from my MB860 using XDA App
Sent from my MB860 using XDA App
I tried not cracking the bootloader but loading a second init. This proved beyond my skills. I am more a infrastructure and SQL guy then developer.
I would love to have this thing cracked open but I must say with a few tweeks this is a fast stable tablet. I do not know what I would want changed other then the native bluetooth PAN menu.
I just received my a100 from best buy, order placed on black friday.
I would love to see the bootloader cracked.
Keep up the good work guys.
Sent from my MB855 using Tapatalk
I for one would love to see some development on the a100! If there is anything I can do to help just let me know. Im not a dev but I have been tinkering since ms-dos in 1982, and I am very eager to see some development on this tablet, especially usb host mode. good luck!!
painter_ said:
I tried not cracking the bootloader but loading a second init. This proved beyond my skills. I am more a infrastructure and SQL guy then developer.
I would love to have this thing cracked open but I must say with a few tweeks this is a fast stable tablet. I do not know what I would want changed other then the native bluetooth PAN menu.
Click to expand...
Click to collapse
That's the route Im going as well, so far I've compiled 2nd-init and it runs, but it crashes right after initalizing the memory and reboots the tablet (I dont think I have the correct memory address of init for the hook to work properly so it reboots the device). I've also tried log's kexec hack and I dont think it works. Asks for a kernel to load, which I dont have but, I dont think our current kernel supports kexec, so a module would have to be compiled for it. Im no kernel developer (I understand how they work, and how to mod an existing one, but building onne from scratch not so much). With kexec, it requires a special kernel the starts up where your current kernel resides in memory, so it would be harder to get working than 2nd-init.
cracking the encryption
I am not sure what type of file this is but I am fairly experienced with cracking and have access to a small render farm with plenty of gpu power and john the ripper installed. I could give it a go at cracking the password. let me know if I can help.
burn.phreak said:
I am not sure what type of file this is but I am fairly experienced with cracking and have access to a small render farm with plenty of gpu power and john the ripper installed. I could give it a go at cracking the password. let me know if I can help.
Click to expand...
Click to collapse
You can't really brute force this kind of thing, we need to use some sort of exploit, would take millions of years or something like that.
Lightsword1942 said:
You can't really brute force this kind of thing, we need to use some sort of exploit, would take millions of years or something like that.
Click to expand...
Click to collapse
I have brute forced a lot before its worth a shot, I wouldn't say its our best shot but it's worth a look and gives me something to occupy my time.
Hello, I have rooted my LG Genesis from US Cellular and would like to flash 2.3.4 onto it. This is a 2.2.2 phone, if that is of any significance. I have looked everywhere and cannot find a solution to this problem. Any help is appreciated. Also, ROM manager does not have this phone in its supported phone list. I need to make a backup before I flash the ROM, obviously. Thank you in advance.
Getting This Phone Soon.
I've been looking into this phone, because it's actually going to be my father's first smartphone. In terms of flashing 2.3.4 on it.... I'll cross my fingers, but I'm not holding my breath. It has a unique form, because of it's dual screens, which in my mind would make it harder to port, and another problem is that as far as I can see, no dev has given any love to creating a custom recovery. I'm just starting out on the whole developing side, instead of just using what others have created. I hope for both our sakes it gets ported. For now, we need a custom recovery and a custom built rom. X.x Joy.
There isn't even any where ive found about rooting the Genesis.... Would love to be able to get ics on it..... Great phone. Love the physical keyboard. Any pointers to any development for this phone?
Sent from my Motorola Electrify using XDA
Rooting Genesis
moparfreak426 said:
There isn't even any where ive found about rooting the Genesis.... Would love to be able to get ics on it..... Great phone. Love the physical keyboard. Any pointers to any development for this phone?
Sent from my Motorola Electrify using XDA
Click to expand...
Click to collapse
Its been talked about before on Android Forums or something. The genesis is STILL running Froyo, so Gingerbreak.apk works like a charm.
Hi,
i was considering buy an A100 but was surprised to see very little or no development for this tablet. Any particular reasons for it?
Sent from my GT-I9001 using XDA App
@sahilkhurana:
The particular reason is that Android 4.0 is supposed to be available on the A100 "early" in the New Year.
jschall said:
@sahilkhurana:
The particular reason is that Android 4.0 is supposed to be available on the A100 "early" in the New Year.
Click to expand...
Click to collapse
I really do hope deving kicks off after ICS. If not i will sell this tab despite being such an amazing specd tab at fantastic price and buy a kindle fire.
jay_993 said:
I really do hope deving kicks off after ICS. If not i will sell this tab despite being such an amazing specd tab at fantastic price and buy a kindle fire.
Click to expand...
Click to collapse
I don't think I could use a kindle fire, it doesn't have a volume rocker, Bluetooth, GPS, or a sdcard slot. I agree this needs more development, but until you we either have a super intelligent person crack the boot-loader, or acer unlocks it for us, we won't get any development going on this. After that gets open, its cake and bacon. (lawl)
It's not ICS preventing dev support... Its the locked and encrypted bootloader. It has been mentioned in several other thread topics that in order for anything "major" to be done to this device that the bootloader has to be unlocked.
With an unlocked bootloader you'll get alot more doors open, such as:
- Rom Manager
- The possibility of porting CM7 and when it comes out CM9
- Custom Kernels
- Over Clocking
- Custom Roms
The dev community can do custom roms (by way of DD'ing a system.img file), but its not the same and can be messy (definitely not something an average person would want to do.)
Some of the more talented "hacker" type devs that have good decryption skills could break the encryption on the bootloader or find a loop hole in it, but so far no one has managed to break it. It's not something every one or dev can do and takes a skilled hacker or someone with the right connections at Acer.
Until this happens this device will be just like the Atrix you won't see much done with it but if it does manage to get unlocked you'll see a flood of roms and things for it.
Thats what i thought as well. Well might sell this tab off soon then cuz i get too many force closes.
Oh and one more thing, you can't use the bootloader hack that was released for the A500. They are two separate devices and while similar the A500 bootloader doesn't have the same 256 bit encryption key.
If you are experiencing too many FC's then you may need to do a hard reset or if you have it rooted try fixing permissions in rom manager (rom manager still works for permissions, but nothing else since it can't load itself into the bootloader). I use this device every day for development work and have no problems, every once in a while the browser will FC, but it's usually because I've done something stupid. Games will FC because of our device's resolution too (all 10" tablets usually run games at 1280x800 our 7" runs at 1028x600)
Like for instance if i log onto xda and click on a link not only will it force close but also delete data as well. Annoying that
I have to agree on slow development but on the other hand i'm so glad I was able to root it quickly as soon as i opened it. Also to add I havent experience FC on normal operation. But I have encountered some when I try to install apps that werent made for the a100. Just as crossix metioned probably cause of resolution conflict.
Thanks a lot for the replies. Its such a shame that Acer has locked bootloader for this device.
Sent from my GT-I9001 using XDA App
why would you buy a crippled WiFi TV
jay_993 said:
I really do hope deving kicks off after ICS. If not i will sell this tab despite being such an amazing specd tab at fantastic price and buy a kindle fire.
Click to expand...
Click to collapse
maby you have not noticed all the things fire dose not have IE: SD card,hdmi,non over custom ROM,and more than i have time to type
I will say this though to be able to charge over USB is nice
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.