lol dont blame samsung if you are doing illegal mods, like flashing root and etc ^^
[07.09.2012][CF-Root 5.6] K**,LA-1346,LB1,LC1,LP-1YF89,LQ-23,LR-GIKQ - su+bb+CWM5
- Thread starter Chainfire
- Start date
Dr Ketan .....on triangle Away Thread , it says that it does not support LPY as of nowtriangle away with ICS stock LPY NO work
any other way without a jig ...
Wait for a week or two: CF had said he was going to produce a new version of TA.
removal of moderated material
In fact, I already have one guy online with me, who seems to brick his device with flashing official ICS build through PC Odin, coming from 2.3.6 with rooted stock kernel. Btw, already not a single example. So...
In fact, I already have one guy online with me, who seems to brick his device with flashing official ICS build through PC Odin, coming from 2.3.6 with rooted stock kernel. Btw, already not a single example. So...
Last edited by a moderator:
Already chasmodo said, you shud w8 Cf likely to create it for stock ICS.
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
To whom whatsever it may concern
To b here in CF root thread to advise keep device stock is ilogical itself.
sorry.
This is for development N advance user only. You are here means you are ready to play with device you like..
Bricking is part of game, when you are victim, it is unfortunate thats it.
At least we shud offer moral support.
I meant ICS, not Android, i do like Android, but not ICS, i simply think GB is way better ant more mature... Maybe i am only subjectif...
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
I meant ICS, not Android, i do like Android, but not ICS, i simply think GB is way better ant more mature... Maybe i am only subjectif...
---------- Post added at 09:44 AM ---------- Previous post was at 09:31 AM ----------
Well, dr.ketan, that is real maturity. Just we (or at least me) can not forget so quickly. I loved this toy man. But in the end i will fix in Samsung service and start over, can not stop, at all. That is one way we keep our synapsis alive, and i like it. Looks like you are close to your hindu kin; beeing born, living, loving, beeing hurt..., and even dying, is part of the univers game. And also crying. And thats it. Is a game, an adventure. Even beeing shot to dead.
I would like to ask you what do you mean with "w8", couse i do not think is about Windows 8....?
would you say this is a solid alternative for LPY.
I only need root to do Battery Percent Mod CRT shut off and transparent top bar.
And I would hate to brick my phone just for those.
Thread cleaned
Gentlemen, stick to actual development discussion and stop the petty bickering. Any more and some infractions will be handed out.
Gentlemen, stick to actual development discussion and stop the petty bickering. Any more and some infractions will be handed out.
Ok so it still isn't really clear if the problem is still present in LPY, or if the issue is "left-over" due to previous ROMs.
It's all possible. Either way, what I wan't to make absolutely clear again:
If the problem is present in CF-Root LPY (and it's not a "leftover" problem from previous ROM - this is possibly the case), then it's also present in stock LPY. This means you *can* randomly brick your phone even if fully booted into Android, under heavy I/O load.
(on the Note there normal and recovery kernels are the same, and CWM is just a userspace program, nothing special(!) - so if the problem can happen in CWM, it can happen in Android)
It's all possible. Either way, what I wan't to make absolutely clear again:
If the problem is present in CF-Root LPY (and it's not a "leftover" problem from previous ROM - this is possibly the case), then it's also present in stock LPY. This means you *can* randomly brick your phone even if fully booted into Android, under heavy I/O load.
(on the Note there normal and recovery kernels are the same, and CWM is just a userspace program, nothing special(!) - so if the problem can happen in CWM, it can happen in Android)
Additional information: I've seen at least one report of someone's device dying after a wipe in stock recovery, and one report of someone's device dying by doing a factory reset in Settings.
Which confirms everything you just said.
Wrong. There's at least one confirmed report of a brick due to wiping in stock recovery on XXLPY, and at least one confirmed report of bricking after doing a wipe from Settings on stock XXLPY.
Guys, could this be true? Is there any hope? I am not so sure but i think you are some the most experienced here, or at least for this topic, an i mean, chasmodo, chainfire, entropy...
Originaly posted by jgaviota: "What I think is happening is that the information about the partitions is being corrupted by the format, in a way that cannot easily be recovered.
As far as I can see ALL the bricks resulted from a format, either via a wipe from recovery or from the install script of Stunner.
Was there any change in the way a format is made from a GB kernel to an ICS one?
If the partition info that gets corrupted is from a partition that does not hold the pbl or sbl then the phone can get into download mode or recovery, but if the partition info that gets corrupted is for any of those two then you have a black screen hard brick.
Has anyone that has a bootloop brick (where you can still go into Download mode) tried repartitioning from latest Heimdall from Linux?
If it is not the partition info it's something like that, maybe some kind of access table...
Anyone has any technical info on the emmc chip used here, and how the partitions are stored? Also any info on the booting process for our exynos? Has AdamOutler made an UnbrickableMod for any of the afflicted devices?
An UnbrickableMod could help us by giving lower level access to the boot process.
BTW I'm an electronics engineer, but I don't have access to the documentation, or to the right tools, and also I don't have the soldering skills to try to develope an UnbrickableMod."
Originaly posted by jgaviota: "What I think is happening is that the information about the partitions is being corrupted by the format, in a way that cannot easily be recovered.
As far as I can see ALL the bricks resulted from a format, either via a wipe from recovery or from the install script of Stunner.
Was there any change in the way a format is made from a GB kernel to an ICS one?
If the partition info that gets corrupted is from a partition that does not hold the pbl or sbl then the phone can get into download mode or recovery, but if the partition info that gets corrupted is for any of those two then you have a black screen hard brick.
Has anyone that has a bootloop brick (where you can still go into Download mode) tried repartitioning from latest Heimdall from Linux?
If it is not the partition info it's something like that, maybe some kind of access table...
Anyone has any technical info on the emmc chip used here, and how the partitions are stored? Also any info on the booting process for our exynos? Has AdamOutler made an UnbrickableMod for any of the afflicted devices?
An UnbrickableMod could help us by giving lower level access to the boot process.
BTW I'm an electronics engineer, but I don't have access to the documentation, or to the right tools, and also I don't have the soldering skills to try to develope an UnbrickableMod."
I don't belong to the knowledge category of CF or Entropy, not even remotely, heh.
However, guys at Epic 4G Touch forum have started a painstaking investigation process to establish what is really causing the bricks. Read about it here:
http://forum.xda-developers.com/showthread.php?t=1644364
However, guys at Epic 4G Touch forum have started a painstaking investigation process to establish what is really causing the bricks. Read about it here:
http://forum.xda-developers.com/showthread.php?t=1644364
@CF, Entropy
After 1 week of questioning and doubts, one simple question comes in mind : Do we stay in ICS-LPY (without wiping, backuping, restoring, large file handling), or do we revert to GB ? You understand that your advice, opinion, feeling is more than crucial to most of us ! And please, an unequivocal one ! Thanks.
(NB : My personal experience = update from LC1+CFroot to LPY through mobileodin, WITH full wipe. Everything ok, for instance 3 CMW nandroid backups I did, though these were 20% slower than the GB backups for approximate same file size (1,5GB). BUT, the day I tried to restore one of these nandroids, my Note stuck badly in Samsungs logo. After 2 hours of 3-finger efforts and battery removals, I was able to start in stockrecovery and flash through pcodin GB KJ1 factoyfs, then flash again LPY through mobileodin, with everroot, without CF kernel. It still works, but I feel so unsafe without reliable backup-recovery!!!).
After 1 week of questioning and doubts, one simple question comes in mind : Do we stay in ICS-LPY (without wiping, backuping, restoring, large file handling), or do we revert to GB ? You understand that your advice, opinion, feeling is more than crucial to most of us ! And please, an unequivocal one ! Thanks.
(NB : My personal experience = update from LC1+CFroot to LPY through mobileodin, WITH full wipe. Everything ok, for instance 3 CMW nandroid backups I did, though these were 20% slower than the GB backups for approximate same file size (1,5GB). BUT, the day I tried to restore one of these nandroids, my Note stuck badly in Samsungs logo. After 2 hours of 3-finger efforts and battery removals, I was able to start in stockrecovery and flash through pcodin GB KJ1 factoyfs, then flash again LPY through mobileodin, with everroot, without CF kernel. It still works, but I feel so unsafe without reliable backup-recovery!!!).
stay on ICS stock and wait updates for resolve this issues....and don't try to do full wipe or format with ICS kernel stock or CF
IMHO
What does it mean:
when I'm connecting Note to PC on window which shown after I put cable to USB - GT I9220
but then when I see in My Computer window - GT N7000 ???
when I'm connecting Note to PC on window which shown after I put cable to USB - GT I9220
but then when I see in My Computer window - GT N7000 ???
See how your phone is identified in your build.prop.
You know what NOT to do, so stay on ICS, don't do it, and you'll be safe.
CWM uses "rm -rf" to "format" a partition before restore, it's not a proper format. So I don't think that's related.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone