Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
View Poll Results: Do you like the new LiquidSmooth Theme ?
Yes love it... 155 62.25%
No gimme stock Theme back... 94 37.75%
Voters: 249. You may not vote on this poll

Post Reply

★★★ [ROM][AOSP][4.0.4][26-06-12] M3dD0gs LiquidSmooth V3 "Linaro" ★★★

OP m3dd0g

23rd May 2012, 02:32 AM   |  #1321  
Senior Member
Thanks Meter: 20
 
209 posts
Join Date:Joined: Jan 2011
More
Is all well with M3d D0g ? .... has v2 been scrapped ? .... its already been a very long wait since it was announced! ... envy

Sent from my GT-N7000 using XDA
23rd May 2012, 03:03 AM   |  #1322  
Member
Thanks Meter: 2
 
96 posts
Join Date:Joined: Jun 2009
i installed this rom on asylm..um dint like it so tried to instal back the asylm..but it stucked on installing update..and now i cant turn on my fone,...what happended? any idea :S

---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------

i hope my fone is not bricked! i cant turn it on..cant go in recovry :S
23rd May 2012, 03:39 AM   |  #1323  
Senior Member
Thanks Meter: 209
 
1,067 posts
Join Date:Joined: Oct 2010
Quote:
Originally Posted by umair1234

i installed this rom on asylm..um dint like it so tried to instal back the asylm..but it stucked on installing update..and now i cant turn on my fone,...what happended? any idea :S

---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------

i hope my fone is not bricked! i cant turn it on..cant go in recovry :S

for me it was liquid..try asylum did not like it..back to liquid (and miui too)-g

anyway...u need to get gb abyss 3.9 or 4.2 kernel (both have red redpill recovery) or a complete gb rom installed then do full wipe (in the gb kernel/gb rom recovery)..think even franco kernel will do..then install what you want..do not think you can just overwipe roms especially these do not mix...go to recovery if you can..and install gb 3.9 abyss kernel but you need to have that already on sd card..otherwise follow

http://forum.xda-developers.com/show....php?t=1659768

it is in your asylum op itself
23rd May 2012, 06:11 AM   |  #1324  
Reb0rn's Avatar
Senior Member
Flag Alingss
Thanks Meter: 763
 
1,824 posts
Join Date:Joined: Sep 2007
Donate to Me
More
Quote:
Originally Posted by umair1234

i installed this rom on asylm..um dint like it so tried to instal back the asylm..but it stucked on installing update..and now i cant turn on my fone,...what happended? any idea :S

---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------

i hope my fone is not bricked! i cant turn it on..cant go in recovry :S

There's how safe the kernel is on this rom... when you installed asylum directly from lp5 kernel you corrupted your eMMC. This happens to some ppl but. Consider yourself unlucky. But in this day and age I can't for the life of me understand why you would flash a rom that uses any of the ics touchwiz kernels. Its pasted everywhere. They are not safe! Never ever belive someone that says that!

Sorry friend but your super bricked... you learned this lesson the hard way.

Sent from my GT-N7000 using Tapatalk 2
23rd May 2012, 07:41 AM   |  #1325  
Senior Member
Flag Mackay
Thanks Meter: 122
 
767 posts
Join Date:Joined: May 2011
More
Quote:
Originally Posted by Reb0rn

There's how safe the kernel is on this rom... when you installed asylum directly from lp5 kernel you corrupted your eMMC. This happens to some ppl but. Consider yourself unlucky. But in this day and age I can't for the life of me understand why you would flash a rom that uses any of the ics touchwiz kernels. Its pasted everywhere. They are not safe! Never ever belive someone that says that!

Sorry friend but your super bricked... you learned this lesson the hard way.

Sent from my GT-N7000 using Tapatalk 2

Aren't the Touchwiz kernels only "not safe" when you try to use recovery? There are a lot of phones out there happily using LPY and LPF. If you don't try to use recovery with these kernels can they still be unsafe?
23rd May 2012, 08:39 AM   |  #1326  
matius44's Avatar
Senior Member
Sunderland
Thanks Meter: 1,077
 
1,798 posts
Join Date:Joined: Feb 2011
Quote:
Originally Posted by appro77

Aren't the Touchwiz kernels only "not safe" when you try to use recovery? There are a lot of phones out there happily using LPY and LPF. If you don't try to use recovery with these kernels can they still be unsafe?

No it's NOT safe, Guys listen to the knowledgeable people when you are in doubt. Do you question your doctor when he/she diagnoses you?

Chainfire and Entropy both said it's not safe, and there was at least one report of brick with the stock LPY kernel (not even CF-Root) just by doing factory reset from within the Settings menu!

And people attacked me when I said here adjust the OP, not just "resolve kernel issues" in a post buried in the thread
Last edited by matius44; 23rd May 2012 at 08:42 AM.
23rd May 2012, 08:56 AM   |  #1327  
Kangal's Avatar
Senior Member
Thanks Meter: 179
 
721 posts
Join Date:Joined: Jan 2006
Quote:
Originally Posted by appro77

Aren't the Touchwiz kernels only "not safe" when you try to use recovery? There are a lot of phones out there happily using LPY and LPF. If you don't try to use recovery with these kernels can they still be unsafe?

They can still be unsafe out of the recovery.
Entropy (an experienced and recognized kernel developer) said that the processes occuring in CWM-recovery aren't that different to the processes in Android. He said there's a risk using it normally, and that with high I/O usage it will be just like flashing the rom and the stupid "feature" will activate = wipe your emmc and possibly a "bad" wipe so that it can no longer write (ie Actual HARDWARE DAMAGE)...meaning even with a Jtag/Jig and Odin you cannot revive it because it is hardbricked (aka SuperBricked).

This "feature" (MMC_CAP_ERASE) has a use and is from Google source (the AOSP). But something in the kernel keeps activating it when its used heavily (I/O - like hard number crunching in Android or Recovery) and wiping the eMMC. Its NOT meant to be activated under those situations, at least not automatically and not uncontrolled.

You need to realize this is a REAL issue, and NOT a scare tactic from Entropy, Reinbeau, ChainFire, neobuddy, etc etc. These are real (and recognized) developers/members who confirmed the bug in the kernel of the official ics roms (lpy, lpf, lp9 etc). And its not just the N7000, other Samsung devices have the same bug in the kernel, with confirmed bricks. There's a reason the thread is STICKIED in the board. Remember these developers dont get anything if you flash/dont flash...so for this to be a "scare tactic" is completely baseless and without any sense. And flashing a new bootloader won't solve the issue, but is very dangerous and can lead to headaches later for you.

As much as I appreciate the enthusiasm in this thread, I do respectfully warn you to get some background info before you flash ANYTHING. Some members here like firasusman shows his enthusiasm and is telling people to flash this rom with the new kernels and telling you there is zero risk. His justification is that "He trusts this man [m3dd0g]" and that buying another Note is Not a Problem. I will just tell you upfront those are DANGEROUS propositions.

I don't know you, but I dont want you to BRICK your device; weather SOFT or HARD. Its such a pain if its happened to you, and the financial burden can be too much for some people. I've played around with a JTAG so I'm telling you this from experience, its a very bad state (frustrations/time wasted/effort spent) to be in. There have been many people who've flashed the LPY kernel and haven't bricked their devices, but there now AT RISK when flashing another kernel/rom and even normal usage...and even that is something I wouldn't wish for anyone.

Here's the summary: Wait for it!
The (few) Kernel developers WILL eventually create a custom kernel WITHOUT the bug, and use the new drivers from the kernels. Or Samsung will respond to our emails and update their software/release an ics update without the bug. Or the available "safe" kernels (eg CM9 nightlies) will resolve their issues (loudspeaker etc etc)....and safe development will continue. Just follow the boards for news, trust me the wait will be worth it
The Following 9 Users Say Thank You to Kangal For This Useful Post: [ View ]
23rd May 2012, 10:48 AM   |  #1328  
Senior Member
Flag Mackay
Thanks Meter: 122
 
767 posts
Join Date:Joined: May 2011
More
Quote:
Originally Posted by Kangal

They can still be unsafe out of the recovery.
Entropy (an experienced and recognized kernel developer) said that the processes occuring in CWM-recovery aren't that different to the processes in Android. He said there's a risk using it normally, and that with high I/O usage it will be just like flashing the rom and the stupid "feature" will activate = wipe your emmc and possibly a "bad" wipe so that it can no longer write (ie Actual HARDWARE DAMAGE)...meaning even with a Jtag/Jig and Odin you cannot revive it because it is hardbricked (aka SuperBricked).

This "feature" (MMC_CAP_ERASE) has a use and is from Google source (the AOSP). But something in the kernel keeps activating it when its used heavily (I/O - like hard number crunching in Android or Recovery) and wiping the eMMC. Its NOT meant to be activated under those situations, at least not automatically and not uncontrolled.

You need to realize this is a REAL issue, and NOT a scare tactic from Entropy, Reinbeau, ChainFire, neobuddy, etc etc. These are real (and recognized) developers/members who confirmed the bug in the kernel of the official ics roms (lpy, lpf, lp9 etc). And its not just the N7000, other Samsung devices have the same bug in the kernel, with confirmed bricks. There's a reason the thread is STICKIED in the board. Remember these developers dont get anything if you flash/dont flash...so for this to be a "scare tactic" is completely baseless and without any sense. And flashing a new bootloader won't solve the issue, but is very dangerous and can lead to headaches later for you.

As much as I appreciate the enthusiasm in this thread, I do respectfully warn you to get some background info before you flash ANYTHING. Some members here like firasusman shows his enthusiasm and is telling people to flash this rom with the new kernels and telling you there is zero risk. His justification is that "He trusts this man [m3dd0g]" and that buying another Note is Not a Problem. I will just tell you upfront those are DANGEROUS propositions.

I don't know you, but I dont want you to BRICK your device; weather SOFT or HARD. Its such a pain if its happened to you, and the financial burden can be too much for some people. I've played around with a JTAG so I'm telling you this from experience, its a very bad state (frustrations/time wasted/effort spent) to be in. There have been many people who've flashed the LPY kernel and haven't bricked their devices, but there now AT RISK when flashing another kernel/rom and even normal usage...and even that is something I wouldn't wish for anyone.

Here's the summary: Wait for it!
The (few) Kernel developers WILL eventually create a custom kernel WITHOUT the bug, and use the new drivers from the kernels. Or Samsung will respond to our emails and update their software/release an ics update without the bug. Or the available "safe" kernels (eg CM9 nightlies) will resolve their issues (loudspeaker etc etc)....and safe development will continue. Just follow the boards for news, trust me the wait will be worth it

Thanks for going to the trouble to post this. Very informative and appreciated. Now I'm worried. I'm currently running RocketRom v1 ICS with the LPY kernel. From what you've said there's a chance that it could all go pear shaped.

I have a nandroid backup of Litening Rom v1 which is GB. Maybe I should flash AbyssNote 4.2, then restore the Nandroid backup of Litening rom then sit on that until this superbrick fiasco is resolved.

Of course the question that comes to mind is why are the developers of these current ICS roms that are using the new kernels not giving users the information and warning that you just have?
The Following User Says Thank You to appro77 For This Useful Post: [ View ]
23rd May 2012, 11:01 AM   |  #1329  
AA1973's Avatar
Senior Member
Flag Frankfurt
Thanks Meter: 8,941
 
5,726 posts
Join Date:Joined: Sep 2010
More
Quote:
Originally Posted by appro77

Of course the question that comes to mind is why are the developers of these current ICS roms that are using the new kernels not giving users the information and warning that you just have?

This is just unfair. Have a look at the original post of eybee1970's Rocket Rom ICS, which you are currently using. There are warnings. Just read the post once or twice...

Galaxy Note N7000 - PARANOIDANDROID (CM9)
Last edited by AA1973; 23rd May 2012 at 11:05 AM.
23rd May 2012, 12:24 PM   |  #1330  
Senior Member
Flag Mackay
Thanks Meter: 122
 
767 posts
Join Date:Joined: May 2011
More
Quote:
Originally Posted by AA1973

This is just unfair. Have a look at the original post of eybee1970's Rocket Rom ICS, which you are currently using. There are warnings. Just read the post once or twice...

Galaxy Note N7000 - PARANOIDANDROID (CM9)

The only warnings that I read were regarding using cwm on that kernel. There were no warnings that there is a chance of superbricking the phone just by using the rom as posted above.

Post Reply Subscribe to Thread

Tags
ask firasusman its working on his device try again, butt is itching but i took a shower, i hate stepping in poo
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes