Related
More info and source credits here, thanks to codeworkx https://plus.google.com/111398485184813224730/posts/21pTYfTsCkB.
ATTENTION:
We've contacted Samsung about the problem where performing a mmc erase could hardbrick your phone (i9100, i9100g, n7000, m250 - MAG4FA, VYL00M, and KYL00M with firmware revision 0x19 // T989 and I727 with fw rev 0x12) if it's having a faulty emmc chip.
Read this thread for more informations about it: http://forum.xda-developers.com/showthread.php?t=1644364
They're working as hard as possible on a clean solution which will be ready soon.
Please be patient and try to not flash any leaked kernels or kernels based on sources where MMC_CAP_ERASE is present.
This app http://forum.xda-developers.com/showpost.php?p=27014974&postcount=1 can be used to identify if your phone is affected or not.
CM9 kernels are safe to flash.
Please share!
Update 14:56 CEST:
Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time.
Click to expand...
Click to collapse
New Clarifications by Entropy : http://forum.xda-developers.com/showpost.php?p=28416723&postcount=403 - Must Read.
To check whether your phone has the brick bug, download the Got Brickbug app from Chainfire: http://forum.xda-developers.com/showthread.php?t=1693704
Also do read the article on xda for more info.: http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
Nice!
That is a really good news after some time.
Sent from my GT-N7000 using Tapatalk 2
Good news!
Looking forward to see how Samsung solve this nightmare
Sent from my GT-N7000 using xda premium
How many time to fix this Samsung BUG? How maby people need ti brick our 600€? If samsung knows why no first before? Grrrrr...
All hard work its from XDA devs!!!! Thank you devs!!
Enviado desde mi GT-N7000 usando Tapatalk 2
Hmmm don't want to get my hopes up
But hmmm ok let's hope saw but how do we know is true ?
Sent from my iPad using Tapatalk
nandihno said:
Hmmm don't want to get my hopes up
But hmmm ok let's hope saw but how do we know is true ?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Teamhacksung dev codeworkx been in touch with Sammy guys so its genuine news...check link in op
Sent from my GT-N7000 using xda premium
at least we now have some hope...hopefully...
So to be clear...
Can someone confirm the following is correct please?
I have a N7000 on official (german) ICS, with the dodgy mmc chip. I must have been lucky since ive flashed a bunch of roms (including CM9, back to gingerbread, then official ICS) without issue. Ive also done a few CWM backup and restores... phew!
1. Flashing anything from the phone itself (eg using mobile odin or CWM recovery) is a no-go (assuming it issues the erase command)
2. Flashing from the PC is OK ??? (via desktop ODIN)?
If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?
thanks
George
ripnetuk said:
Can someone confirm the following is correct please?
I have a N7000 on official (german) ICS, with the dodgy mmc chip. I must have been lucky since ive flashed a bunch of roms (including CM9, back to gingerbread, then official ICS) without issue. Ive also done a few CWM backup and restores... phew!
1. Flashing anything from the phone itself (eg using mobile odin or CWM recovery) is a no-go (assuming it issues the erase command)
2. Flashing from the PC is OK ??? (via desktop ODIN)?
If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?
thanks
George
Click to expand...
Click to collapse
Flashing is not the problem but wiping is
So if they release a new update then simply don't wipe on your ics but wipe only after you install the new update
If however you want to be extra careful like I am
Flash a gb rom via odin then wipe that then flash said ics update via Odin
Sent from my iPad using Tapatalk
While there have been brickage reports using either PC Odin or CWM, there have been none regarding Odin Mobile Pro. So, when I flashed back GB, I used Odin mobile Pro. Everything went smooth.
//troll mode activated
It's just like Microsoft patching windows vista
//troll mode off
This is a true victory for XDA developers!
My deepest respect for all of you guys :thumbup:!!
Are they releasing a fix for brickd phone or a prevention update?
blue_panther9_9 said:
Are they releasing a fix for brickd phone or a prevention update?
Click to expand...
Click to collapse
Prevention.
Sent from my GT-N7000 using xda premium
I really hope this mess will soon be over. Let's hope while they are resolving the brick bug they also take a look at the wakelock thing. Contrary to others I have encountered this problem very rarely (1 time so far). Nonetheless it would be nice to see a solution.
Sent from my Galaxy Note running ICS
Good news but given that we haven't seen ics roll out in all countries, who knows when this will get fixed.
Another thing that bugs me. Is there possibility that Samsung push the solution for this bug and carriers just ignore it and continue with pushing the infected ics?
I guess that all we need is just one good release and everyone can flash it.
Hope to see it soon.
Sent from my Samsung Galaxy Note using XDA app
ripnetuk said:
Can someone confirm the following is correct please?
If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?
Click to expand...
Click to collapse
In all probability it might show a message over kies / OTA message asking to connect to kies on the comp .. and provide an update for kies desktop having 0din in it
ashoksoft said:
In all probability it might show a message over kies / OTA message asking to connect to kies on the comp .. and provide an update for kies desktop having 0din in it
Click to expand...
Click to collapse
Update 14:56 CEST:
Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time.
Just updated op too
This is great news! Many thanks to entropy and chasmodo and all who've worked on this and sacrificed for us!
Also thanls to those who took it seriously.
Sent from my GT-N7000 using xda premium
I was interested, after reading the thread "are you satisfied with your TF300?" to see just the proportion of owners that unlocked their bootloader, as this could have implications with the speed of development. I also noticed how many users said they were not satisfied when their tablet was stock, but became more satisfied when it was running a custom ROM. It seems to me that some people are unsatisfied with the stock ROM, but don't wish to unlock the bootloader and void the warranty meaning they wont be able to send it back should there be a problem, or sell it on for maximum retail value.
Please choose one of the options above, thanks! (It would also be interesting to post your thoughts on how this affected your satisfaction with the tablet)
RolloJarvis said:
I was interested, after reading the thread "are you satisfied with your TF300?" to see just the proportion of owners that unlocked their bootloader, as this could have implications with the speed of development. I also noticed how many users said they were not satisfied when their tablet was stock, but became more satisfied when it was running a custom ROM. It seems to me that some people are unsatisfied with the stock ROM, but don't wish to unlock the bootloader and void the warranty meaning they wont be able to send it back should there be a problem, or sell it on for maximum retail value.
Please choose one of the options above, thanks! (It would also be interesting to post your thoughts on how this affected your satisfaction with the tablet)
Click to expand...
Click to collapse
I cant use a device w/o root... Same day they released the unlock bootloader I unlocked my device! All my android phones are rooted and or unlocked the day I got it.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
I did not unlock. I figured I will leave it stock until jellybean comes out and see how that goes. I did root though. Gotta have that.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I'm rooted atm. Gonna wait until my warranty is done before I consider unlocking.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
I have unlocked and installed the Hydro ROM (see the development section) . It is smoother for sure, no browserlag any more.
First I made sure to have root, so that I could backup my current applications and their settings with Titanium backup. Then I installed TWRM, the modern equivalent of Clock Work Mod, to backup the stock ROM. By taking these precautions the riscs of creating a mess are fairly reduced.
I also used the stock ROM for approximately 6 weeks, to be sure that the hardware was alright and that the chances of needing Asus support in the coming year were small.
Unlocked and rooted the day I got the tablet. Been happily running Hydro since its release.
Still locked bootloader here but rooted off course. I'm waiting for official jellybean
If you are completely satisfied with your device, then don't tinker with it by rooting and unlocking. However, if you unlock the device and install a custom recovery, then it becomes very difficult to brick the tf300. You can almost always come back to a working stock official rom with a custom recovery by simply flashing the software directly downloaded from the ASUS website. I have no regrets about unlocking my bootloader.
Unlocked and rooted
Sent from my Galaxy Nexus using Tapatalk 2
still on latest stock rom. since there will be an update to 4.1.1 i will not root or unlock (the bootloader) of the device. my girlfriend uses the tablet more intensively than me. rooting the device might cause a drop the WAF.
but i am planning to unlock/root as soon as asus stops developing for 300T.
eddyfr said:
Still locked bootloader here but rooted off course. I'm waiting for official jellybean
Click to expand...
Click to collapse
Will rooting change otherstuff such as OTA updates, recovery or etc? Possible to unroot easily?
Sent from my Galaxy Note or from my Transformer TF300T
i didn't unlock , but rooted.
Locked & rooted. Keeping warranty.
Still Charged Up
I am unlocked and have used clean rom, hydro 4.3, cm9, skank for ics, aokp for ics, aokp for jb, cm10 and am currently running skank for jb. For me personally, my tab has run the fastest & smoothest with the custom roms w/ little, if any lag at all. With the new TWRP doing /boot backups as well as external sd support, it is so easy now to try all the roms and find one you like.
I'm not unlocked. Like some, I'm waiting for the 4.1 update to see what I think of it. I find it runs slower than my phone for some functions like updating apps, so I'm leaning to unlocking for a faster rom.
Mine is unlocked & rooted. And yet, I didn't found a rom that would satisfy me - just the stock one But maybe I will try the Clean ROM.
Yes! Is the best that I do
Unlocked, rooted. Btw, rooting doesn't affect otas.
Oh, and I'm waiting for warranty to be almost up, then get it fixed. I have a dead pixel. Lol in know, finicky but still lol
Sent from my SGH-T989 using xda premium
Not unlocked or rooted. Waiting on JB. The stock ROM may have issues but custom ROMs just introduce others.
I have unlocked my TF300G bootloader using ASUS Unlocker V.7 and also root it with CWM as my recovery. I'm still on TW .40 official ROM but I have tweaked the build.prop a little bit.
Figuring that the stock one is so locked down, is it possible to take new features of an ota of the regular s5 and flash it to a dev edition one without messing up root? Things like updated boot, going from 4.4.x to 4.5, etc?
I recall but never fully understood that was the problem with the s4, they never sent out ota update for the dev edition....
Just debating getting an s5 dev edition, but don't want to be stuck with original firmware/software
Sent from my SM-G900V using Tapatalk
808phoneaddict said:
Figuring that the stock one is so locked down, is it possible to take new features of an ota of the regular s5 and flash it to a dev edition one without messing up root? Things like updated boot, going from 4.4.x to 4.5, etc?
I recall but never fully understood that was the problem with the s4, they never sent out ota update for the dev edition....
Just debating getting an s5 dev edition, but don't want to be stuck with original firmware/software
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
I believe you can upgrade from 4.4 to 4.5 but have to flash a unlocked bootloader like one from t-mobile or a international version. From what I gather from the Note 3 thread that's pretty much how they do it.
Well I know the s4 dev edition's problem was that they wouldn't update firmware for it, stuff like the boot (I forget which other things weren't able to get updated since they weren't sending out otas), which left the device with only it's original firmware
Sent from my SM-G900V using Tapatalk
You'll be able to do some stuff. Consider how cm releases updated firmware even though the carrier doesn't make a release. It's tough but possible.
Sent from my SM-N900V using Tapatalk
Hello,
I've been on the forums for awhile but never posted. I tried searching but hadn't found a thread for it yet. Would it be possible to port the Sailfish OS from Jolla to the LG G2? The hardware adaptation development kit has been released by Jolla. I would try it myself but have no programming experience whatsoever. Just curious! Thanks!
Would also like to know this
Sent from my LG-D800 using Tapatalk
I would guess that we would need to have an unlocked bootloader. I may be wrong but I wouldn't be holding my breath.
Sent from my KFTHWI using Tapatalk
corrsea said:
I would guess that we would need to have an unlocked bootloader. I may be wrong but I wouldn't be holding my breath.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
According to the Jolla guide for the build (I'd post links, but I'm unable to yet) all that's needed for an install is a phone that has official CM 10.1.x releases. Like I said, I have no programming experience so I don't know how feasible the build would be for our phone. I have high hopes for it though because the launcher is great and the interface looks fantastic.
If we did it would be unstable atleast on my variant we don't even have sound with a 24a baseband and if were 24a everything it just bootloops
sent from my T-Mobile LG-VS980
Who shall be the first to build ?
The race is on
Buahahhahahhaha
Sent from my LG-D851 using Tapatalk
brolic925t said:
Who shall be the first to build ?
The race is on
Buahahhahahhaha
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Source ?
Sent from my LG-D852 using XDA Free mobile app
shahkam said:
Source ?
Sent from my LG-D852 using XDA Free mobile app
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...roid-5-0-lollipop-source-code-aosp-right-now/
I'm OK now, I'm happy to have waited this long for an AOSP ROM.
I can wait longer if it becomes a L ROM for our G3!!
Great news !
it's hard to say...i'm working on a lollypop port since weeks now and the main problem is a kernel panic related to the modem resetting.. i think that once i will figure out how to solve it i will be able to release a first beta
It is usually very hard to get new android versions ported to a device where there is no official rom of the same version for it - you basically are going in blind trying to get all the hardware to work.
If we are lucky we might see one or two builds before LG release theirs (which is now less than 2 months away!) but I would expect them to be buggy with some hardware not working - so far we don't even have a fully working Kitkat AOSP build for our device.
manups4e said:
it's hard to say...i'm working on a lollypop port since weeks now and the main problem is a kernel panic related to the modem resetting.. i think that once i will figure out how to solve it i will be able to release a first beta
Click to expand...
Click to collapse
good luck bro!!! lets see if you can beat LG to the draw...
please keep us posted!!!
Thanks in advance
Deeemm79 said:
good luck bro!!! lets see if you can beat LG to the draw...
please keep us posted!!!
Thanks in advance
Click to expand...
Click to collapse
if someone would like to help here is last_kmsg at the very end you'll find the kernel panic about modem
bah, who needs the LG Lollipop rom? probably gonna have their own skin again which, in my opinion, is inferior to stock lollipop. plus, if you have not read, Android 5.0 Lollipop gives developers the option to completely lockdown devices and prevent root, specifically in our devices where bootloader is not unlockable. Don't think I'll take the risk though. It's a huge one!
http://www.xda-developers.com/android/android-l-lockdown/
Oooh. I so happy. ????
jayzhoukj said:
bah, who needs the LG Lollipop rom? probably gonna have their own skin again which, in my opinion, is inferior to stock lollipop. plus, if you have not read, Android 5.0 Lollipop gives developers the option to completely lockdown devices and prevent root, specifically in our devices where bootloader is not unlockable. Don't think I'll take the risk though. It's a huge one!
http://www.xda-developers.com/android/android-l-lockdown/
Click to expand...
Click to collapse
this is true although (and i may well be wrong) i would presume this would only apply if you take the update from OEM and not custom rom .... if we take a flashable custom rom i would assume that this lockdown is completely irrelevant and fairly risk free providing the devs can get all the hardware side of things up and running
ah yes, you are right. personally though i would prefer to go straight to stock rom after rooting. not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom
jayzhoukj said:
ah yes, you are right. personally though i would prefer to go straight to stock rom after rooting. not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom
Click to expand...
Click to collapse
that all depends what you want to be able to do on your device ..... without root you cannot use xposed (although until made to run on ART it wont work with lollipop onwards ) ... you need root to delete / modify any / all system apps and other tweaks under the hood ..... there are many things you could need root for
jayzhoukj said:
not really sure what the difference is (if any big changes) between a rooted and non-rooted stock rom
Click to expand...
Click to collapse
Root alone does nothing. It's what you do with the elevated privileges that matters. With root access, you pretty much have complete control over the phone's software, so you can do next to nothing, or completely overhaul everything to the point where it is indistinguishable from a stock, non-modified phone.
By the way... If LG isn't blowing smoke up our backsides, we'll have a working Optimus UI w/ 5.0.. guessing 6 weeks, give or take. And it remains to be seen how quickly they release their sources. Until those sources are released, any 5.0 custom ROMs are going to be Lollipop on top of LG's KK stuff (kernel, radio/modem, graphics drivers, etc). Not sure how stable that will all be. My only experience with a phone running a ROM like that was running early KK builds on my old Galaxy S3, which was Android 4.4 built on top of Samsung's Jelly Bean stuff. And that was buggy as hell, tons of problems. Basic stuff, like every time it switched from Wi-Fi to mobile data, I got a kernel panic and it would reboot.
So I would be wary of any LP ROMs for the G3 that didn't include the native LP stuff from LG.
LeoRex said:
Root alone does nothing. It's what you do with the elevated privileges that matters. With root access, you pretty much have complete control over the phone's software, so you can do next to nothing, or completely overhaul everything to the point where it is indistinguishable from a stock, non-modified phone.
By the way... If LG isn't blowing smoke up our backsides, we'll have a working Optimus UI w/ 5.0.. guessing 6 weeks, give or take. And it remains to be seen how quickly they release their sources. Until those sources are released, any 5.0 custom ROMs are going to be Lollipop on top of LG's KK stuff (kernel, radio/modem, graphics drivers, etc). Not sure how stable that will all be. My only experience with a phone running a ROM like that was running early KK builds on my old Galaxy S3, which was Android 4.4 built on top of Samsung's Jelly Bean stuff. And that was buggy as hell, tons of problems. Basic stuff, like every time it switched from Wi-Fi to mobile data, I got a kernel panic and it would reboot.
So I would be wary of any LP ROMs for the G3 that didn't include the native LP stuff from LG.
Click to expand...
Click to collapse
infact since 1 month i'm trying to port lollypop and i'm blocked by kernel panic at boot due to modem resetting
My concern is for our d850 development .... It will pick up im guessing
2SHAYNEZ
OEM Unlock feature in Lollipop dev options
Lollipop has an OEM Unlock feature in the development options. Chainfire already utilized it to root the N9. See attached.
so excited in looking forward to your effort - friends....
hwong96 said:
Lollipop has an OEM Unlock feature in the development options. Chainfire already utilized it to root the N9. See attached.
Click to expand...
Click to collapse
OEM unlock meaning ?