Hi Guys, I'm italian...I'm sorry for my english
I have loaded on my galaxy S this ufficial firmware "I9000XXJVO (Gingerbread 2.3.3)" and now I want to load a ROM. I prefer a Rom which is fast and stable. Which ROM do you suggest to me? Which ROM leaves more available memory?
Thanks!!
Go for custom roms, far more available memory plus there are lot of tweaks enabled developers to make sure your phone is smooth.. trust me try simply honey 3.6.1, u'll love it.!
Please feel free to browse through the dev and q&a sections. You will find that there are plenty of different roms and kernels available, along with other spicy details/guides. Many of them will tremendously increase the battery span, but will present you with different options with regards to the user interface.
Depending on the android version you're running there are different paths to choose in terms of minimum difficulty.
But, for someone totally new to roms&kernels, who is running 2.3.x already, I'd just reccommend starting with Darky's rom, as it has a great userbase with amazingly detailed guides, you really can't go wrong with their tuts should you feel insecure about flashing etc.
And then when you discover that you're still not happy with the speed, feel free to dive into the dev forum as I said
EDIT:
----------------
And another thing you'll find is that there is no such thing as a BEST rom.
After all, all of this is coming from people limited in their numbers, time and funding....
I have tried "Simple Honey 3.6" but the available memory was from 120 MB to 140 MB (I think it is bad because with the ufficial firmware I9000XXJVO the available memory was 160 MB!!) and the battery doesn't last long...
2012-09-11: update. So far 12 xda users reported a bricked gt8.9. Don't join them...
2012-09-08: update. I will be out of town this weekend. I will keep the top post summarized once per day (if there is news)
Current knowledge is: (note: knowledge on this issue is still evolving and may become more accurate in future)
there is a serious bug in a hardware EMMC chip (or its driver) used in many Samsung devices
in GingerBread / HC this bug was not triggered
in its ICS kernels Samsung has used a feature to wipe EMMC in a way that triggers the bug in the chip
when xda developers used Samsung ICS kernel sources to continue work with (e.g. as kernel for the recovery - which has separate kernel from the ROM itself), they pulled the issue into their work
this has caused many bricks on many many different Samsung devices.
gt8.9 tab's CWM 6.0.1.2 includes this ICS kernel, and is dangerous if used to wipe /system or any other wipe (theoretically, that includes nandroid restore)
gt8.9 earlier CWM are believed to be safe (5.1.2.6, 5.5.0.4, 6.0.0.8, 6.0.0.8_alternate)
potentially, even update-binary inside a flashable .zip can be dangerous: IF it includes a specific (ext4) module from faulty ICS kernel, and IF the updater-script does a format(). So far there are no reports of such so far on the gt8.9
potentially, the same issue can be triggered from the kernel in the ICS ROM (although less risky, as that kernel is normally never used to wipe the boot or system partition). Nobody has reported issues after doing a "factory reset" from within Samsung p7310 stock ICS (USA region). We don't know if the ICS kernel inside that ROM is dangerous. Still, you are (till further notice) adviced not to use that feature inside any ICS rom. If you do, report here!
2012-09-07: v1 (modified)
Still more people are reporting bricking their device, after using CWM 6.0.1.2, even though it's already known 24-48 hours that this recovery can lead to this error.
I will link some threads in a follow up where the issue is discussed. Still, I recommend to try focus the discussion to just 1 thread... It will be easier on us all.
Proposal
- I propose to bump this thread hourly or so, for a few days at least, so that everybody has a chance to see it.
- There are many threads that discuss this issue. Try to keep the discussion a little focussed, don't continue posting in 6-7 different threads. Use this one
- If you see this disappearing from page 1 in General Forum, just reply with either:
* good idea, keep bumping
* stupid, stop it already
- If you heard of this issue here first, hit thanks
Thanks
Links
CWM 6.0.1.2 was made available in the CM9 thread (dev forum) around Sep 4.
By Sep 5 the first reports of bricked devices were coming in. The CM9 thread, starting from post 1066 (link, quote below) has been all about that for several pages. If you have found something really useful, reply on that dev thread. Do not spam it though.
kallt_kaffe said:
FYI, I might have bricked my P7310 so development is paused for now. Was flashing a CM10 build yesterday that I was experimenting with when it got stuck at "Formatting /cache" and after a while I did a long press on power thinking it would recover from it.
However I'm now stuck with black screen and it identifies itself as APX in Device Manager.
(...)
Click to expand...
Click to collapse
If you want to discuss in general, mention you have the same issue, ask for updates, etc, just reply here
other threads started for same issue. just for reference...
http://forum.xda-developers.com/showthread.php?p=31177035
http://forum.xda-developers.com/showthread.php?p=31158609
http://forum.xda-developers.com/showthread.php?p=31238668
http://forum.xda-developers.com/showthread.php?p=31172928
http://forum.xda-developers.com/showthread.php?t=1875756
Reserved
Sent from my HTC Desire using xda app-developers app
I hope those with the problem get a fix soon, i wouldnt be able to sleep if that happended to me
Sorry and up for this thread to warn others
Sent from my GT-P7300 using xda app-developers app
Im not really sure what makes this bugs happen..
But this issues is not new for me in galaxyNOTE gt n7000 and Sgs2 I9100 we call this as EMMC superbrick..
It happen in ICS kernel stock if you operates some EMMC_CAP_ERASE in kernel such as wiping your data or system.. Format.. Or deleting large file in recovery operation or factory reset in EMMC with firmware revision 0x19(firmware of this chip)..
It cannot recover with regular utility like JTAG coz This superbrick makes EMMC faulty in /data partition or /system partition blocks..
If you go to Samsung Service Centre.. Your device should be on mainboard replacement..
Sorry for my english.. You could use this app for testing your emmc has a bug or not..
If you had the emmc bug.. Dont use any recovery from ICS sources until someone with expert knowledge confirm that everything is fine..
Please read this thread for complete issues and discuss..from recognized developer entropy512
http://forum.xda-developers.com/showthread.php?t=1633938
I think it not about cwm version but the kernel is..
THANKS for makes this
Ups seems the i got the bug :-/
Sent from my GT-P7300 using xda app-developers app
I too got the bug and CWM 6.0.0.8 but my tablet will stay with AOKP for the time being until the dust settles.
Could somebody tell me what is the latest safest CWM to use for flashing KK's CM10 preview ROM.
Bump.
Cwm 5.1.2.6, 5.5.0.4 and 6.0.0.8 have all been around long enough to conclude that they are safe (in terms of this emmc bug)
You guys have a twrp?
Sent from my SGH-I727 using xda premium
Well, crap on a cracker...
Okay, so after reading the dumbed down facts about the issue at hand, it would seem that the latest CWM is not completely at fault for bricking devices. This most likely happened to users who were already on ICS and who already had a kernel that will allow the EMMC_CAP_ERASE to execute over a chip incapable of handling it.
The reports of using the latest CWM and successfully updating to ICS experimental builds without bricking most likely came from people going from stock Honeycomb to ICS?
Any of this true?
de3pkeeper said:
Well, crap on a cracker...
Okay, so after reading the dumbed down facts about the issue at hand, it would seem that the latest CWM is not completely at fault for bricking devices. This most likely happened to users who were already on ICS and who already had a kernel that will allow the EMMC_CAP_ERASE to execute over a chip incapable of handling it.
The reports of using the latest CWM and successfully updating to ICS experimental builds without bricking most likely came from people going from stock Honeycomb to ICS?
Any of this true?
Click to expand...
Click to collapse
Yes... You got the point..
strange.
What I understood (not necessarily correct) - simplified and without pointing fingers
the fault is likely in the kernel that is in that recovery 6.0.1.2.
there is another kernel, for the "Android OS", and it could hypothetically contain the same bug, but noone has found any ROM kernel to have the bug.
some developer tried to integrate a (Samsung?) ICS kernel (as released in the opensource for the ROM) in the CWM kernel -
some other developer copied that first developer's work and compiled it for the 8.9 tab
lots of bricked tabs.
So that's not correct? I've been reading about this all day, but I could have missed something in the last few hours.
de3pkeeper said:
The reports of using the latest CWM and successfully updating to ICS experimental builds without bricking most likely came from people going from stock Honeycomb to ICS?
Click to expand...
Click to collapse
I think kallt_kaffe said he flashed at least 10 ROMs using 6.0.1.2 before it failed on him...
Let me look if I can find that back.
orlandoxpolice said:
You guys have a twrp?
Click to expand...
Click to collapse
I've read about that recovery on the 10.1 forums, and on the sub-forum for Galaxy Tab 8.9 SGH-i957 (LTE, 4g version).
But never seen it for the P7300 and P7310.
fred_be9300 said:
I think kallt_kaffe said he flashed at least 10 ROMs using 6.0.1.2 before it failed on him...
Let me look if I can find that back.
Click to expand...
Click to collapse
First.. This bug it doesnt depends how many times you use.. Its random.. Maybe just once or twice or ten times when you wipe..
Second..hardbrick and superbrick is different..superbrick cannot recover with jtag because The chip is broken..
I hope this issue not happen to our tab..we need some testing and investigation..but who can do that?
I guess all samsung device with that kind of type EMMC chipsg is risky when in ICS..
this bug existed for the skyrocket as well as soon as ICS was released, it never existed with gingerbread. seemed completely random as well.
One dumb question: how about if you have already installed ICS kernel. By using CWM 6.0.0.8 or version below and do restore, wipe, etc, will it also brick the tab? Could someone confirm this if it is safe? Or has experience with lower CWM and survive the brick bug? Thanks
nexus_g said:
One dumb question: how about if you have already installed ICS kernel. By using CWM 6.0.0.8 or version below and do restore, wipe, etc, will it also brick the tab? Could someone confirm this if it is safe? Or has experience with lower CWM and survive the brick bug? Thanks
Click to expand...
Click to collapse
All indications are that CWM 6.0.0.8 is 'safe'. The problems appeared to start with 6.0.1.2.
Bump... Just hoping no others get brick from known issue
After fighting for hours trying to get this ROM, I figured I'd share my bandwidth and try to make it easier to get this. Here is a torrent file to download the "BadSoul O3D ICS 4.0.4 v1.0.zip". I'll seed as long as I can.
Thanks to BAD Soul for the ROM, xbsall for the initial port, and all other members who have made it possible to get these ICS ROMs working on the P920/P925 and sister devices. Wish there was more I could do.
I take no credit for this ROM. Check the following thread for ROM info.
http://forum.xda-developers.com/showthread.php?t=2021722
I had to stop seeding this morning, but I put it up on SkyDrive - http://sdrv.ms/Ty7nt0
I can take it down if BadSoul doesn't want it mirrored....looks like he may be doing fixes now?
Though I am a pretty experienced personal developer on Android, I haven't posted enough on XDA to reply in the dev section lol! I just have a few questions regarding this ROM. When I install the script to swap internal and external, I cant look at the system storage at all. It shows it's capacity, space left, etc., though not the files within. Also, there is no camera app installed after flashing V3(?). The thread still says V1, the Batakang FTP shows V3, and only shows first flash zip.. so I am slightly confused on whether it's me not finding things or just a busy, unorganized work space. Thanks in advance! Enjoying the ROM btw! Definite performance and battery boost. :good:
Greetings My Fellow Zenfone Go users!!
Now I'm sure most of you here have already done some research about a Custom Nougat Rom for our device, since it has some very neat features
But sadly, after a few attempts to install the ROM, I get an endless bootloop (approx. 1 hour) then it just hangs at the boot logo.
After some research, my thoughts had dictated me that the most possible causes of this was:
* The ROM was not properly ported
* The kernel for the ROM needed to be built from source
*My device was not properly unlocked
Now I know the third cause sounds quite absurd, but in my case (not sure about others), I had previously used SP flash tool to recover my device from brick in accordance to the method of unlocking the device found on
[ROOT/TWRP] Asus Zenfone Go ZC500TG/Z00VD by keityrobins PAGE 19, POST #185 & #186
(sorry can't post links yet )(I used this method to unlock my device)
But at this time, I am posting this thread just to inform others who don't know that the real problem (based on my research) was THE KERNEL. Something about the accelerometer driver in the kernel being different in the newer releases of Zenfone go (Z00VD) variant of ASUS.
Note that across many sites in the web providing ROMS for our device, they were dependent on that kernel 4PDA devs developed(built from source)
In conclusion, I am happy to say that someone on that forum had the same problem and opened it up, and so the new kernel is developing as we speak.
(Remember I can't post links, you will have to dig into their site yourself)
Please share guys if you found a way to fix the kernel.