Database Users

Anyone bricked from iMilka's AOSP/CM9?

Entropy recently stated that using any leaked build was dangerous.
I have used every single version of AOSP and CM9 from the beginning to current, jumping between and back and forth from GB many times with no issues.
I have also never SEEN a report of anyone bricking (when properly) flashing around with these roms.
Just curious if a case actually exists.

crawlgsx said:
Entropy recently stated that using any leaked build was dangerous.
I have used every single version of AOSP and CM9 from the beginning to current, jumping between and back and forth from GB many times with no issues.
I have also never SEEN a report of anyone bricking (when properly) flashing around with these roms.
Just curious if a case actually exists.
Click to expand...
Click to collapse
No but there is a risk. And the question is : "Do you want to take this risk while CM9 is announce next week with a safe kernel".
I was using Imilka Cm9, and yesterday i flashed back to GB. Maybe you could wait one week and avoid flashing a hazardous repack !

I had no issues with Imikas cm9 roms, I used all 3 of them and have since flashed to a stock gingerbread as the video playback in all the ICS roms is not good enough yet compared to GB roms.
I have tried all the ICS leaks and gone back to GB with no issues, just waiting for a proper stable release of ICS with good video playback performance as I get in GB then I will stick with the Ice Cream

remixtech said:
No but there is a risk. And the question is : "Do you want to take this risk while CM9 is announce next week with a safe kernel".
I was using Imilka Cm9, and yesterday i flashed back to GB. Maybe you could wait one week and avoid flashing a hazardous repack !
Click to expand...
Click to collapse
I wasn't stating that there isn't a risk, or that anyone should chance it. Just simply that I have not heard of a single case of anyone having a problem with iMilka's releases (killing the board). Therefore my none developer point of view is that the risk must be VERY small IF said risk does truly exist with all Kernel Leak builds.
It SEEMS to me that the problem does not lie with the kernel build but the way it is scripted and executed. Hence why no one has ever had the problem with AOSP/CM9, but the problem came up with Angelom's kernel and the last Stunner build. The problems were also immediate in both cases, again where no one has ever had this problem caused by AOSP/CM9. So YES, I am sure AOSP/CM9 could have caused the problem if iMilka made whatever mistake was made by Stunner/Angelom, but I would say to me it is quite obvious he did not, and that the problem IS a mistake in the way the kernel is handled. Speculation and opinion only of course.
I have been running them since the beginning, so I am not saying I personally would have chanced it this close to offical ICS / Official CM9, but i've been running his releases for quite some time.

crawlgsx said:
Entropy recently stated that using any leaked build was dangerous.
I have used every single version of AOSP and CM9 from the beginning to current, jumping between and back and forth from GB many times with no issues.
I have also never SEEN a report of anyone bricking (when properly) flashing around with these roms.
Just curious if a case actually exists.
Click to expand...
Click to collapse
Flashed all imilka Roms from day one, and never had as much as a hiccup on any one of them.

The question is if anyone tried to restore a cwm backup ? The most of the bricks were caused by doing that task..
Sent from my GT-N7000 using xda premium

No issues here either with Midnote or TeamMid ROMS (also tried a couple of Alba versions and Stunner).
I have flashed many times and with LP5 kernel through CWMR or Mobile Odin including full wipes.
I have made nandroid backups but haven't tried to restore any, perhaps this has saved me?

Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium

dimcus said:
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Exactly the same here. Unable to format /system partition after restoring.
Odin managed to fix it tho.

jscurtu said:
The question is if anyone tried to restore a cwm backup ? The most of the bricks were caused by doing that task..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I have multiple times. CWM Backup restore works sometimes for me ICS to ICS, and fine GB to GB. ICS to GB or GB to ICS causes issues but I can easily fix them with a flash/odin/etc and still have complete access to download mode / CWM. ICS to ICS I have run in to problems such as funky root or partition issues, once again still easily fixable and still have plenty of access to the phone/flash abilities, By no means even close to a brick.
That said at this point in the game I wouldn't even consider doing a CWM restore, why even chance it!

dimcus said:
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Just to report, I experienced exactly the same.
Regards!
Sent from my GT-N7000 using xda premium

dimcus said:
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Which kernel were you on?

chill392 said:
Which kernel were you on?
Click to expand...
Click to collapse
The first leaked one - LP1.

jscurtu said:
The question is if anyone tried to restore a cwm backup ? The most of the bricks were caused by doing that task..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I think you are wrong.Bricks caused when trying to format /system
Sent from my GT-N7000 using Tapatalk

Bricks were caused by anything that tried to wipe a partition - and restoring a nandroid will first wipe a partition.
What kernel is imilka's a repack of? Maybe it's an unaffected one. I recall seeing stuff in imilka's thread saying not to use its CWM.
Without source for the leak kernels it's impossible to tell what's changed and declare one kernel "safe" and another "dangerous" - as long as some are proven dangerous they should all be considered dangerous.

afilopou said:
I think you are wrong.Bricks caused when trying to format /system
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
When restoring a backup , you usually format /system ; )...so basically yes that is correct, I only mentioned that it mostly happened while doing that task..
Sent from my GT-N7000 using xda premium

Entropy512 said:
What kernel is imilka's a repack of? Maybe it's an unaffected one. I recall seeing stuff in imilka's thread saying not to use its CWM.
Without source for the leak kernels it's impossible to tell what's changed and declare one kernel "safe" and another "dangerous" - as long as some are proven dangerous they should all be considered dangerous.
Click to expand...
Click to collapse
It was multiple different kernels, up to LP5 and LP6 even.
I understand the logic and respect your words of caution with what is most certainly from someone who has a much better understanding than I, I just feel it is the way the kernel was used/modified/implemented that caused the potential problems (by the devs), not the kernel itself. Based on the logic I provided earlier in the thread. I am not saying the problem still does not exist in the kernel, I have no idea, but it is obviously something that did not come out in many rom implementations, just those 2.

Flashed all roms from maxicet and some repack stock ICS roms. Never got any problems. Tested over 10 ICS roms... And now using maxicet's ROM as daily.

crawlgsx said:
It was multiple different kernels, up to LP5 and LP6 even.
I understand the logic and respect your words of caution with what is most certainly from someone who has a much better understanding than I, I just feel it is the way the kernel was used/modified/implemented that caused the potential problems (by the devs), not the kernel itself. Based on the logic I provided earlier in the thread. I am not saying the problem still does not exist in the kernel, I have no idea, but it is obviously something that did not come out in many rom implementations, just those 2.
Click to expand...
Click to collapse
The thing is, this has happened over multiple devices, with multiple recovery implementations, including recovery implementations that work fine with other kernel bases. The end result is the same - fried eMMC that can't even be recovered with JTAG.

Entropy512 said:
The thing is, this has happened over multiple devices, with multiple recovery implementations, including recovery implementations that work fine with other kernel bases. The end result is the same - fried eMMC that can't even be recovered with JTAG.
Click to expand...
Click to collapse
Agreed, very bad.
All I am saying is that it ONLY happened on those 2 botched kernel implementations. It is obviously SOMETHING the Dev's did with the kernel that caused this, seeing how ALL the other roms/versions clearly have not caused this. Since the result was immediate with both of those and many of us have jumped/cwm'ed/etc from MANY different Leaked kernel builds and NOT had that problem.
I am not trying to put them at blame, running any rom/dev is strictly at your own responsibility and risk, just stating that I don't think it is fair to place every leaked rom build in the same category of danger. Is there a risk, certainly, as the dev's could accidentally make said same mistake (I am not even clear if "we" know what causes it?) in a future version. That said I feel pretty confident that if the "final" versions of iMilka's roms were going to cause that issue, it would've happened by now. That is why I wanted to see if anyone had ever been bricked (fried eMMC) from them, and it seems, no.

Random reboot

I'm still on my stock ROM with just root permissions and I'm getting random reboots every once in a while. Before I was rooted I had one or maybe random reboots that I remember and one of the times it just reboot while it was in my pocket. I rooted my phone two days ago and since then my phone has randomly rebooted itself about 4 times already. I had the two mods added which were the touch screen and video bitrate mod. After I seen it happen more than usual after adding those mods I reverted back to stock. I was wondering if anyone else is having these types of issues maybe perhaps a bug in the stock 4.2.1.
Sent from my Nexus 4 using xda premium

AnthonyAldrete said:
I'm still on my stock ROM with just root permissions and I'm getting random reboots every once in a while. Before I was rooted I had one or maybe random reboots that I remember and one of the times it just reboot while it was in my pocket. I rooted my phone two days ago and since then my phone has randomly rebooted itself about 4 times already. I had the two mods added which were the touch screen and video bitrate mod. After I seen it happen more than usual after adding those mods I reverted back to stock. I was wondering if anyone else is having these types of issues maybe perhaps a bug in the stock 4.2.1.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
might be a widget. a lot of people are having luck with the franko kernel. but his r16 build released earlier today started giving people random reboots. he either has it fixed already or is in the middle of doing so. the r15 build that i am on is great. but i would wait for the 16. the changelog looked pretty good.

phermey said:
might be a widget. a lot of people are having luck with the franko kernel. but his r16 build released earlier today started giving people random reboots. he either has it fixed already or is in the middle of doing so. the r15 build that i am on is great. but i would wait for the 16. the changelog looked pretty good.
Click to expand...
Click to collapse
I saw an article from android authority that said Google is aware of the random. Reboots and working on a fix soon. I just reed that after the post.
Can I flash francos kernel on my stock ROM ? Won't that cause problems. ?
Sent from my Nexus 4 using xda premium

AnthonyAldrete said:
I saw an article from android authority that said Google is aware of the random. Reboots and working on a fix soon. I just reed that after the post.
Can I flash francos kernel on my stock ROM ? Won't that cause problems. ?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
yes if rooted. lots of people are stock and running franco.

phermey said:
yes if rooted. lots of people are stock and running franco.
Click to expand...
Click to collapse
So if I want to flash francos kernel on my stock ROM just wipe delvik right ?
Sent from my Nexus 4 using xda premium

AnthonyAldrete said:
So if I want to flash francos kernel on my stock ROM just wipe delvik right ?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
franco says you dont have to wipe anything. then another guy came in right behind him and said to wipe dalvik. its on one of the last three pages in his thread. id say wipe just in case.

phermey said:
franco says you dont have to wipe anything. then another guy came in right behind him and said to wipe dalvik. its on one of the last three pages in his thread. id say wipe just in case.
Click to expand...
Click to collapse
wouldn't hurt to wipe anyway. ill stop wiping and see if i notice a difference though, so far i dont notice any. so id probably just skip out on wiping as it does seem useless because my phone still feels the same

KtManta messed up root

After updating the latest KtManta kernel my nexus 10 lost its root capabilities, super user won't just work, it is just me or it is a known issue?
I've flashed the December version of the kernel afterwards and the problem prevails (ktoonsez doesn't include every kernel download link, a bad practice in my opinion)
I am on CM now and everything is working fine, I wonder if anyone has been victim to this weird issue
Sent from my Nexus 10 using Tapatalk HD

zombiegenerator said:
After updating the latest KtManta kernel my nexus 10 lost its root capabilities, super user won't just work, it is just me or it is a known issue? ...
Click to expand...
Click to collapse
I am guessing but is this a permissions issue? I've flashed KTManta a number of times including just yesterday with TWRP and never had the issue you describe. Occasionally, right after flashing a ROM or Kernel, I have seen from TWRP a "Fix Permissions" message which I always execute. Some custom ROM/Kernels flash instructions even include a "Fix Permissions" instruction.
Also sometimes after flashing then rebooting I've had to "reinstall" Superuser so it can grant root permissions to various programs. As a habit, right after a new flash, I start Superuser once just to see if it says it needs to be reinstalled. This is not a reinstall from an apk but is a dialogue message displayed when the app is started.
As I wrote this is purely a guess on my part.

I had a laugh at the thread title. (sorry) You either have a corrupt download or something else really weird going on. A kernel wont remove root from your unlocked firmware and ROM files unless the flashing script is actually programmed to remove the files needed. Which its not.

Well this is strange, because I have fixed the permission issue and wiped cache and dalvik, not once but multiple times (I set up the kernel thrice, after it was malfunctioning).
But seeing you two replying, I set up KtManta over CM today and it is not giving me a bit of trouble, strange indeed.
btw, is it true that KTManta fixed the color issue a bit?

Yes it does fix the color a little bit.
What ROM were you on that you had this problem?

EniGmA1987 said:
Yes it does fix the color a little bit.
What ROM were you on that you had this problem?
Click to expand...
Click to collapse
Stock
Sent from my Nexus 10 using Tapatalk HD

zombiegenerator said:
Stock
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
It won't cause you to lose root but it is also not really designed to use with stock either. Most if not all custom kernel users are on CM, AOKP or AOSP ROMS.

brees75 said:
It won't cause you to lose root but it is also not really designed to use with stock either. Most if not all custom kernel users are on CM, AOKP or AOSP ROMS.
Click to expand...
Click to collapse
What's the difference between AOSP and stock roms?
And yes it's now working flawlessly with CM.
Sent from my Nexus 10 using Tapatalk HD

[Q] galaxy S4 random reboots

Anyone else had this / any ideas - my s4 randomly reboots. Can sometimes be when I'm using it or other times when it is sitting idle.
Sent from my GT-I9505 using xda premium

if you can go to download mode flash a new stock rom using odin . before it try with a factory reset too :laugh::laugh:

quibble8 said:
Anyone else had this / any ideas - my s4 randomly reboots. Can sometimes be when I'm using it or other times when it is sitting idle.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
yup, i had this after running a custom rom for a few days. i'm sure it wasn't the rom though, i restored back to stock last night just in case, we'll see.

However, in the future, please also post your ROM, kernel, etc.
For example, having your phone OC might result in such random reboots...

okty2k said:
However, in the future, please also post your ROM, kernel, etc.
For example, having your phone OC might result in such random reboots...
Click to expand...
Click to collapse
I didn't change the kernel and I don't want to name the ROM because I'm sure it's not its fault - it was fine for a few days with plenty of reboots and activity/usage. Sounds like others on stock have the same problem (not necessarily related to the camera issue), so I've gone back to my stock backup and will see what transpires.

ch0use said:
I didn't change the kernel and I don't want to name the ROM because I'm sure it's not its fault - it was fine for a few days with plenty of reboots and activity/usage. Sounds like others on stock have the same problem (not necessarily related to the camera issue), so I've gone back to my stock backup and will see what transpires.
Click to expand...
Click to collapse
I understand you, but it is not like blaming the ROM creator. Is that you might have discovered a bug, and you can help to get it solved.
personally, the first thing I would do is to make a factory reset. This is not the case for you any more... but however.
Good luck and please tell us got things go on...

Fair enough, it was slim bean build 6 on Verizon. I reverted to my stock twrp backup last night (10hrs ago) and been fine so far...

Driving myself crazy phone inconsistency

I always used Xylon and always got good days use. Then ill eventually flash a new build cause its got new features and i can never get the battery life back the same how it was. I always perform multiple factory resets and wipes before clean flashing new builds. I use the same Franco kernels, etc. When i had my phone perfect it would drain like a percent an hour. Now its like 2-3.5% an hour and i dont know why. BetterBatteryStats checks out fine. Nothing is keepin the phone awake, the idle drain is just high for some reason. Is there a better process to start fresh? Should i flash everything? Flash stock rom, and bootloader and radio? Then flash xylon? would that make any difference?

Worked for me! I wouldn't definitely try it, I know it sucks, what's to lose
Sent from my Nexus 4 using xda premium

Ill definately give it a try. Will be like the 5th time flashing different roms trying to figure out why this is acting weird this month. Do you happen to have the thread to the latest radio \ bootloader flash?
I found the latest stock rom i believe http://forum.xda-developers.com/showthread.php?t=2251958&highlight=stock

emerica243 said:
Ill definately give it a try. Will be like the 5th time flashing different roms trying to figure out why this is acting weird this month. Do you happen to have the thread to the latest radio \ bootloader flash?
I found the latest stock rom i believe http://forum.xda-developers.com/showthread.php?t=2251958&highlight=stock
Click to expand...
Click to collapse
If you want better battery life you should probably flash the stock image through fastboot; https://developers.google.com/android/nexus/images
Sent from my Nexus 4

Tom540 said:
If you want better battery life you should probably flash the stock image through fastboot; https://developers.google.com/android/nexus/images
Sent from my Nexus 4
Click to expand...
Click to collapse
Big difference compared to just factory resetting and flashing the stock rom?

emerica243 said:
Big difference compared to just factory resetting and flashing the stock rom?
Click to expand...
Click to collapse
Well simply flashing the stock ROM is unlikely to do anything, its just like flashing Xylon or whatever, anyone who had an improvement had it from flashing the img through fastboot. You only have to do once though, if there is going to be any effect
Sent from my Nexus 4