Related
I have been running Bonsai 3.0.1 on my wife's Epic for a while now and TRIED to update to 4.0.x a while back, but got a TON of FCs and lock-ups. So, the other day, I saw the official 4.1.1 ROM was out and tried that...even did the suggested "factory reset" within Android. Well, Bonsai overwrote CWM with that new custom recovery they have and I'm still getting FCs and lock-ups. Went back to 3.0.1, but was looking to get a new/updated ROM put on...what is generally considered the best ROM out there for the Epic? Also, what is the best way to get ClockWork recovery back?
I run Cyanogen 7 on my EVO and love it, but noticed that CM7 for the Epic is still in beta with a lot of key features (camera) not working yet.
I know that no one wants to read another "what is the best ROM" thread, but I'd really appreciate some help here...thanks!
Sturmie
Syndicate is THE best imo
PS: make sure to enable journaling right after flashing it.
Best ROM
As I'm sure you've read before, every phone acts differently. Most people seem to gravitate towards ACS or Bonsai. For me, ACS was buggy and Bonsai was, while extremely fast, the worst on battery life.
I personally have had the most luck with the current MidNight ROM and more recently Simply AOSP. Even though there seem to be hundreds of threads on tweaks and hacks, most don't seem to take well to my phone. The big ones (No CIQ, for example) seem to be included in about everything now.
Give 'em a go, see what works. I can safely recommend the two above.
Yup id go with Srf 1.1.1 (1.11?) Best imo
Sent from my SPH-D700
Sturmie said:
I have been running Bonsai 3.0.1 on my wife's Epic for a while now and TRIED to update to 4.0.x a while back, but got a TON of FCs and lock-ups. So, the other day, I saw the official 4.1.1 ROM was out and tried that...even did the suggested "factory reset" within Android. Well, Bonsai overwrote CWM with that new custom recovery they have and I'm still getting FCs and lock-ups. Went back to 3.0.1, but was looking to get a new/updated ROM put on...what is generally considered the best ROM out there for the Epic? Also, what is the best way to get ClockWork recovery back?
I run Cyanogen 7 on my EVO and love it, but noticed that CM7 for the Epic is still in beta with a lot of key features (camera) not working yet.
I know that no one wants to read another "what is the best ROM" thread, but I'd really appreciate some help here...thanks!
Sturmie
Click to expand...
Click to collapse
Bonsai 4.1.1
SRF 1.1.1
Midnight series
Frankenstein
Urban Fury
ACE 2.0
Supernova 3
All are great ROMs
Not sure how to get the other CWM back. I like Bonsai's recovery But, if you use Quickboot and boot into recovery it takes you to CWM and not the Bonsai recovery.
Maybe you got a bad download of the Bonsai 4.1.1? Did you try to reflash it after all the FCs? Did you post in the Bonsai forum or Bonsai thread here?
You could always Odin back to stock and just start fresh that way also. Then just root with One click and get your CWM that way.
2 rules I follow about ROMs
1. No ETAs lol
2. YMMV
Everything with our phones...is phone dependent, they are completely different from the next Epic
Edit:
Sorry to the Devs that I didnt list ROMs from! These were the ones that were just on my sd card right now!
Sturmie said:
I have been running Bonsai 3.0.1 on my wife's Epic for a while now and TRIED to update to 4.0.x a while back, but got a TON of FCs and lock-ups. So, the other day, I saw the official 4.1.1 ROM was out and tried that...even did the suggested "factory reset" within Android. Well, Bonsai overwrote CWM with that new custom recovery they have and I'm still getting FCs and lock-ups. Went back to 3.0.1, but was looking to get a new/updated ROM put on...what is generally considered the best ROM out there for the Epic? Also, what is the best way to get ClockWork recovery back?
I run Cyanogen 7 on my EVO and love it, but noticed that CM7 for the Epic is still in beta with a lot of key features (camera) not working yet.
I know that no one wants to read another "what is the best ROM" thread, but I'd really appreciate some help here...thanks!
Sturmie
Click to expand...
Click to collapse
Use Odin Flash back to stock ECO5 rom.
You can then Flash back to clockwork using odin following the thread instructions for the specific rom you want to work with.
I like ACS Swiss Cheese it works great as long as when you are in a stock rom you get a lock for the gps before installing swiss cheese. There are several threads that explain load order for it to install correctly. I have had it running for near month now with no problems.
Thanks for the replies...I've been looking at Syndicate's ROM...seems to have a lot of people liking it at the moment.
As for Bonsai, I MAY give 4.1.1 another shot since I've been using MyBackup Pro to restore all of her APK+APP DATA, which may have caused some problems. I did have 4.1.1 working when I flashed it OVER top of 3.0.1, but the battery life was horrible...I'm talking 1/2 of what it was with 3.0.1. So, I tried a clean wipe/reset and gave 4.1.1 another shot...that's when I had all the FCs and freezes.
Sturmie said:
Thanks for the replies...I've been looking at Syndicate's ROM...seems to have a lot of people liking it at the moment.
As for Bonsai, I MAY give 4.1.1 another shot since I've been using MyBackup Pro to restore all of her APK+APP DATA, which may have caused some problems. I did have 4.1.1 working when I flashed it OVER top of 3.0.1, but the battery life was horrible...I'm talking 1/2 of what it was with 3.0.1. So, I tried a clean wipe/reset and gave 4.1.1 another shot...that's when I had all the FCs and freezes.
Click to expand...
Click to collapse
You should use Titanium Back and backup your information using nanroid to avoid FC errors. If just remember there newest Rom is only compatible with there own kernel. If you try another Kernel with it your won't get the stellar battery life. I am using a combination of Bonsai and anonymous gingerbread and it is working out well with me. I ran Bonsai and back up all my information on Bonsai then I flashed gingerbread and recovered the Bonsai Rom on top of it.
Sturmie said:
Thanks for the replies...I've been looking at Syndicate's ROM...seems to have a lot of people liking it at the moment.
As for Bonsai, I MAY give 4.1.1 another shot since I've been using MyBackup Pro to restore all of her APK+APP DATA, which may have caused some problems. I did have 4.1.1 working when I flashed it OVER top of 3.0.1, but the battery life was horrible...I'm talking 1/2 of what it was with 3.0.1. So, I tried a clean wipe/reset and gave 4.1.1 another shot...that's when I had all the FCs and freezes.
Click to expand...
Click to collapse
I would definitely go e it another shot. Try using the enable_journal zip in the Bonsai Downloads section first, then flash the ROM. That should help you avoid the FC issues until you get the installation errors ironed out.
Sent from my SPH-D700 using Tapatalk
I had the same issues with my first Bonsai install, but then I ODINd back to STOCK EB13, used Bonsai One click root, wiped 3x, and installed. It is now totally flawless. Give that a shot, it only takes about 30 minutes total.
lattiboy said:
I had the same issues with my first Bonsai install, but then I ODINd back to STOCK EB13, used Bonsai One click root, wiped 3x, and installed. It is now totally flawless. Give that a shot, it only takes about 30 minutes total.
Click to expand...
Click to collapse
From what I've read, coming from EB13 is the best way to go. Even if you Odin EC05, it still seems to have problems. Their dev, Randy, knows the ins and outs of why, so I would suggest Odining EB13, rooting with with their unlocker, then flashing their newest ROM.
I personally use SRF 1.1.1 w/ the Genocide 1.0 kernel, and don't have any major complaints outside bluetooth being wonky after each restart. For me, SRF is stable enough where I don't need to reboot but once a week, if that, unless I'm changing things around.
This. Path of least resistance for Bonsai is definitely ODIN'ing EB13. And 4.1.1 has great battery life in my experience.
Atm, the biggest deciding factor on ROM's to use has to be whether you want to stay on Froyo or do you want to be on Gingerbread.
hayzooos said:
From what I've read, coming from EB13 is the best way to go. Even if you Odin EC05, it still seems to have problems. Their dev, Randy, knows the ins and outs of why, so I would suggest Odining EB13, rooting with with their unlocker, then flashing their newest ROM.
I personally use SRF 1.1.1 w/ the Genocide 1.0 kernel, and don't have any major complaints outside bluetooth being wonky after each restart. For me, SRF is stable enough where I don't need to reboot but once a week, if that, unless I'm changing things around.
Click to expand...
Click to collapse
I would also suggest using Titanium Backup and MyBackUp root sparingly. Not that they don't work but it seems many users troubles always start with restoring old data from Titanium/MBR. I have also found SMS Backup & Restore to be a good option for those wanting to save and restore your txts over using TB/MBR which seems to foul things up when restoring txts.
Don't install any data from previous roms unless it was done by Bonsai during the install. Totally avoid any system data. Old saying: garbage in garbage out...
Sent from Bonsai 7.1.1.1
Looks like I'm not the only one that continues to have issues with Bonsai... everytime I flash Bonsai updates my phone goes wonky and I have to start over again with a factory reset.
After factory resetting to fix my microphone while in a call...now my Slacker will not advance to the next song by itself.
Really looking hard at SRF at this point!
digiblur said:
Looks like I'm not the only one that continues to have issues with Bonsai... everytime I flash Bonsai updates my phone goes wonky and I have to start over again with a factory reset.
After factory resetting to fix my microphone while in a call...now my Slacker will not advance to the next song by itself.
Really looking hard at SRF at this point!
Click to expand...
Click to collapse
You didn't need to reflash to fix the mic, it's a setting in VooDoo.
try EC05 Plus out, quick stable, and good on battery life...
I use Bonsai /w journaling. It is the only ROM that has stayed stable for weeks. Others go bonkers at some point especially w/o jounaling. No offense to ACS but I have yet to have one of their ROMs start and stay stable. Baked stuff is 2nd closest.
Acs srf 1.1.1
Sent from my SPH-D700 using XDA Premium App
I have been on Urban Fury since launch day (March 29 I think) You get 1 FC on the wallpaper app on install and that's it. I have been beta testing themes and kernels and have NEVER had data corruption or force closes other than the one on boot. It comes with Genocide kernel and Wifi Tether 3 pre 14 works great. That being said, all of the ROMs are good. Its just a matter of what you and your phone like the best
Sent from my SPH-D700 using XDA Premium App
For those of you who are having FC's or reboot problems, I recommend trying this (on all roms):
clear cache / DC 3x
flash the rom form the sd card
immediately flash the rom again
Do all of this without rebooting. What ive noticed a LOT is that I often get curious issues with roms, and then I flash them again and dont get those issues anymore (--or, I get a different set of curious issues). Since i do everything else the same, it seems that it must have been the flash that was problematic. just as we have grown accustomed to wipe data multiple times to ensure a successful clear, we should also become accustomed to flashing (especially for larger files more prone to exhibiting problems) multiple times to ensure a clean and successful write.
I know there was a GB ram leakage problem with EG22/EH06 which was causing reboots, but even with these roms you shouldnt be experiencing FC's right out of the box. A lot of people have claimed to run EH17 without any reboots (or FCs) so you too should be able to experience it. Good luck all.
PS - If you have Journaling OFF, make sure your phone doesn't die due to lack of power! Keep it charged. Four times so far I've been thrown into the chaos of "The application Google services Framework has stopped unexpectedly," due to letting un-journaled phones die. Now, I just keep it on for data safety / integrity.
First. Good tip.
you'll probably get flamed for posting this in development though.
Sent from Kevo's Epic w/ Hurricane 2.0
ksmullins88 said:
First. Good tip.
you'll probably get flamed for posting this in development though.
Sent from Kevo's Epic w/ Hurricane 2.0
Click to expand...
Click to collapse
We are a kinder, gentler community lately..lol
Sent from my SPH-D700 using xda premium
JohnCorleone said:
We are a kinder, gentler community lately..lol
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
thank god lol
I brought the lighters, let's getm,,,,, oh, well damn, good tip man.
You know I have never had to flash anything twice and things go pretty well with my flashes for the most part but I do one thing that isn't usually mentioned. After I do all the wipes 3x (data cache dalvik) I go into mounts and storage and I format data cache and system. The data and cache obviously have already been formatted but none of the wipes ever touch system. The ROM script must do that I guess, but I figure why not play it safe and personally clean all the file systems... Works for me.
Sent from my SPH-D700 using Tapatalk
I have been doing thing for a long time. Because of the same weird kinda thing you found.
Good post
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
thanx for the tip man.....will try next time I flash a new ROM
this is what i did after seeingit in a post and mines is runnign goood so far ...question how do u know if journaling is on or off
great tip.. im about to try it RIGHT NOW.. I have wiped and reinstalled roms for the past 2 days now.. because I keep getting reboots and force closes.. even before I try to install any new apps.. im now on a rooted stock deodexed EG22.. that I just flashed about 2 hours ago.. I will now try a custom rom and fash twice and see how it works out for me..
This sounded interesting so I broke my vow not to flash gingerbread again until it was released. I decided to do everything differently than I had in all the previous installs and follow the OPs directions. I'm running EC05 rooted with CWM, so I downloaded the stock odex EH17 zip, followed the clearing suggestions in this post, and flashed EH17 in CWM. Flashed it twice as suggested. Flashed SU, and rebooted.
Long story short, after about 90 minutes it rebooted on its own.
Glad I made a nandroid backup before I started this, because I'm back on stock EC05 rooted again.
all gb roms will have fc's; this is just a procedure to make sure that the fc's you Do experience are caused by errors in the rom's programming as opposed to flashing errors =]
i too am on rking's ec05
Uthman said:
all gb roms will have fc's; this is just a procedure to make sure that the fc's you Do experience are caused by errors in the rom's programming as opposed to flashing errors =]
i too am on rking's ec05
Click to expand...
Click to collapse
I don't get any FCs on Hurricane 1.6. AND no reboots whatsoever with the Tegrak/SetCPU fix in the other thread.
Sent from my SPH-D700 using XDA App
Can someone link to the fix?
Sent from my SPH-D700 using XDA App
I can also assure everyone, turning your head to the right, while flashing, improves the data connection speeds with any GB modem.
kennyglass123 said:
I don't get any FCs on Hurricane 1.6. AND no reboots whatsoever with the Tegrak/SetCPU fix in the other thread.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I had great success with EH17 using the Tegrak config along with the EH17Plus Kernel. Also, I found that the only time I did get a reboot was when I was using the hotspot or wireless tether. But it only happened when the phone got hot and was NOT on the charger. No reboots at all when tethering if I had the phone plugged into the charger, or during any other usage. I recently went back to EC05 to use the SRF1.2 ROM. EH17's modem was a lot faster too, imo. Going back when more ROMs become available.
Also, I tried Hurricane but got fc's. I'll try it again with the doube flash. I liked it otherwise. Now that I think about it, I was flashing modems and started getting fc's on SRF1.2. But none after I flashed it again (double). So this may be the trick if you're having fc's.
Sent from my SPH-D700 using XDA App
ROM: SRF 1.2
Kernel: Revolted
Modem: EC05
brewdude said:
Can someone link to the fix?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I can get you a link later. On my phone right now. But what I can do is go post in it and move it up to the top. It is in this forum marked possible fix for random reboots on GB leaks.
Sent from my SPH-D700 using XDA App
Okay folks, if somebody could bring my issue to the attention of anybody who knows what to do about it I would appreciate it.
My issue is twofold:
1)I'm still getting random reboots with RandomROM Thunderhawk 3.3 despite the posting on the thread that says (NO MORE REBOOTS) Is there anything that can be done about this?
2)I checked my baseband version and the modem is still EC05, is there a way to flash or ODIN an EI22 modem for this ROM without getting a black screen when the icons should come up? Could this also be what's causing the reboots?
Thanks for anybody's help that is willing to give it.
Are you using a custom theme? And you have to flash the stickied modem delta. If you are using a theme, I would blame that.
Sent from my ICS NookColor using Tapatalk
I was using thunderhawk too and I had some reboots but onlyyyyy on the lockmod version. When I flashed the regular one I had no problems at all
And for basband I would probably try this
Nandroid backup
Flash "ec05 to ei22" its somewhere in the development section I believe
Reboot
If that doesn't work then a fresh new start is what I would Recommend
Odin back to stock
Root
Install cwm
Flash "eco5 to ei22" modem
Flash thunderhawk 3.3 (without lockmod if you could live without it)
Sent from my SPH-D700 using XDA App
I got the EI22 modem here and flashed it in CWM and it worked well. Only problem I had with thunderhawk is the lockscreen mod, and I'm having data issues on wifi after the phone's been on a while.
I was ec05 but when I flashed the Thunderhawk and it changed to ei22. never had a problem. Got a wild hair up my butt to flash the shadow kernal 1.0.6. Never been happier. no reboots, wifi works perfect, and very responsive. running a live wall paper and still get awesome battery life. give it a try
I saw several posts from folks having some wifi-4g interaction problems...switching back and forth causing one or the other to fail...is that a common problem to all 3.3 users, or are most people not seeing it? I want to give this a try, but I use 4g (at work) and wifi (home) everyday, so I'd like to see how common that issue is. I'm currently on Mostly-stock with Nubernel's latest released kernel...
Sent from my SPH-D700 using XDA App
So...bummer. I guess I answered my own question...I installed Thunderhead 3.4.3 and sure enough... I have wifi and 4g problems. Seems like going back and forth between the two causes issues...had it fail going both ways today. On a positive...man, that ROM seems pretty nice and his new install process rocks...was seamless going from Mostly Stock...
Sent from my SPH-D700 using XDA App
You could always try a clean install with doing a factory data reset in CWM and wiping Dalvik, flash ROM, check to see if stuff works, then do an advanced data restore from your last nandroid. If you stll have problems then the best bet is to set everything up fresh after the clean install.
Cluefree said:
So...bummer. I guess I answered my own question...I installed Thunderhead 3.4.3 and sure enough... I have wifi and 4g problems. Seems like going back and forth between the two causes issues...had it fail going both ways today. On a positive...man, that ROM seems pretty nice and his new install process rocks...was seamless going from Mostly Stock...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
The deal with the wifi/4g issue is that 4g will show 0.0.0.0 for ip, baseband, and dns if used after wifi in most cases. This is on official releases of 3.3 and newer. If you turn off wifi, reboot, then turn on 4g it should work. This is oviously annoying. Random provided me with alpha builds of 3.4 and 4.0, and the issue was squashed for me. However, the issue still persists in 3.4.3 official release according to some reports. I have limited access to 4g and can only test on certain days.
Thunderhawk is in a transitional period right now, and 3.4.5 should be released today. Random is hopeful this might solve some issues, including the dialer issues some are reporting with the 3.4 official builds. After that his focus will be on 4.0, which is EL30 based. Consider anything from 3.4 on a beta, and only run it if you want to help find bugs. Obviously you don't mind reporting or I wouldn't be replying lol. Just follow the threads and wait untill it looks stable enough for your usage needs.
Sent from my SPH-D700 using xda premium
Thanks! I certainly wasn't busting on Random's work...and I know he has limited access to 4g for testing, so that makes it harder for him to verify these things. So
I absolutely saw what you describe going from wifi to 4g. Going from
4g to wifi, I had wifi that wouldn't turn on at all (error when trying to enable), and, like you and others have mentioned, a reboot resolved both cases. I will hang out and see if he pushes out a fix soon, and just eagerly await 4.0. If it gets too annoying, I'll restore to my
Mostly Stock... Hmmm... Is there an issue restoring an rfs backup if I am now on ext4? Heh...
Sent from my SPH-D700 using XDA App
Just installed the latest 3.4 revision...I think...Heh. The update was so fast its hard to tell!
Sent from my SPH-D700 using XDA App
And...confirming...the wifi/4g issue persists. 4g ip address is messed up on the first connect after being on wifi...reboot resolves.
Sent from my SPH-D700 using XDA App
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.
I posted this over at rootz earlier today and didn't get any bites so I figured I'd give it a shot over here.
I may be the only one in the world experiencing this problem. Looked around quite a bit and don't see any sign of others having this issue... Anyway, my N7 doesn't seem to like it when I flash a new kernel. I've tried several different kernels and when ever I flash one my display will not wake up once it times out or if I turn the display off manually. Once the screen goes dark i have to hold the power button down and reboot. I have zero issues with custom kernels as long as they are baked into the rom. I typically wipe cache and dalvic after flashing kernels...
Sent from my Galaxy Nexus using xda app-developers app
Little bump here... 130 views and not a peep... :-/
scram99 said:
Little bump here... 130 views and not a peep... :-/
Click to expand...
Click to collapse
youre experiencing "sod", which is a fairly common problem with android 4.2.1 source code(not as common on the n7 as the gnex, but common enough). do you flash the kernel with the rom or do you flash the kernel separately?
This happens after switching out the kernel on any ROM I've used. Have not flashed a different kernel at the same time I flashed a ROM. I don't think that will make a difference. I can however flash kernels over my stock rooted backup... I don't know. Just weird and bums me out being limited like this...
scram99 said:
This happens after switching out the kernel on any ROM I've used. Have not flashed a different kernel at the same time I flashed a ROM. I don't think that will make a difference. I can however flash kernels over my stock rooted backup... I don't know. Just weird and bums me out being limited like this...
Click to expand...
Click to collapse
I would just factory reset and start from scratch. Do you have any settings set like UV??
Sent from my Nexus 7 using xda premium
I have tried flashing back to stock, relocking and starting from scratch. I do not undervolt...
A few good folks in the android community had experienced similar happenings and suggested lean kernel... Flashed it earlier this evening and working like a charm.