Related
Wondering why the bionic has a few roms out already and we dont? Do they have a fully working cwm? Am i missing something? Just curious. Thanks.
So far I've seen a deodexed stock rom and an early pre-alpha of CyanogenMod. What else has been posted for the Bionic?
The deodexed ROM is no different than stock for users and offers zero benefits.
The CM7 ROM was created by the lead CM team member of the Motorola Droid and Motorola Droid X (lots of experience with Motorola phones) and because he was donated a Droid Bionic. It's a completely useless ROM at this point as most of the hardware sensors do not work. It boots. Not much else.
Buy cpvcs a Droid 3, ship it to him and he will have a CM7 ROM booting on it within days of receiving it. It'll be just as useless as the Bionic's version....but it'll be there.
Give it time....it is going to be a while before a good solid/stable ROM is released.
First rule of XDA, don't ask for ETA's. If you want a custom ROM, nothing stopping you from trying to cook one your own.
Edit, hit the thanks instead of quote, they really should move that button
lordgodgeneral said:
First rule of XDA, don't ask for ETA's. If you want a custom ROM, nothing stopping you from trying to cook one your own.
Edit, hit the thanks instead of quote, they really should move that button
Click to expand...
Click to collapse
Where in my post does it ask for an eta???? I was asking why. Its a simple question.
heres the thing...waiting for CM7 will be worth the wait.. mmhmm.
..
They can flash, they're using the same flashing method that the D2, DX are using with 2nd init and hijacking. Hashcode hasn't enabled flashing on the D3 recovery yet because he's trying to do something a little different and a little safer from what I understand. From his explanation over in the clockwork recovery thread in development he's working more on a dualboot flashing system where we would basically leave the stock system intact and run the custom rom off a different partition/folder. This would allow us to boot to the stock rom if something happens during the flash process on the custom rom. Since using the 2nd init and hijack and not having an unlocked bootloader, CWR gets loaded into the preinstall partition along with the hijack files, so there's a chance these can get overwrote while flashing if something goes wrong and potentially soft brick the phone.
Don't worry the D3 is the flag ship phone that won't go to much longer with out some kick ass roms. But it is some BS that the bionic is getting roms right off the bat, while we wait. But I would be happy to send a d3 to those guys... if it would help or will bionic development and hacks work for the d3 as well????
Sent from my DROID3 using XDA App
Since when?
lordgodgeneral said:
First rule of XDA, don't ask for ETA's. If you want a custom ROM, nothing stopping you from trying to cook one your own.
Edit, hit the thanks instead of quote, they really should move that button
Click to expand...
Click to collapse
Since when has their been rules on topics asking ETA's on this forum, or any other forum in general? I know it's taboo to ask questions that have already been answered in several posts, but there are several forums specifically about speculating the ETA of not only just devices or OTA leaks, but about the cooking of roms on freshly rooted phones as well. The question of this post is legit, especially for users without the experience that more knowledgable users like tcrew and you (lordgodgeneral) have contributed to answering a question ALOT of people in the droid 3 community are wanting to know. Glad this topic existed, helped me out..
mmsomekid said:
Because the bootloader is still locked. The Bionic will probably get unlocked slightly faster than the D3 because they have more developers working on it, but theyre so similar that i would expect the D3 to get an unlock the same day as the Bionic. Unless Motorola finally unlocks the bootloaders but who knows when that day will come...
Edit: there is an UNL3ASH3D rom now available for the bionic, i didnt think they could flash yet in CWM?
Sent from my rooted Droid 3
Click to expand...
Click to collapse
It doesn't matter if the Bootloader is locked. It will probably never be unlocked.
Its been a rule since the devs on this particular forum specifically asked us not to ask for eta's. We have people cooking roms, were just waiting for our awesome version of CWM to be stable and safe to use. I'm as anxious as any of you, but don't hassle the devs that are working so hard to make our phones the best out there. Give them time.
sent from my ROOTED DROID3 from the XDA app
ROM Manager Premium Clockwork Recovery
Until now I have been more or less bemused by the complaints that the Droid 3 was being somewhat neglected in the development community in favor of the Bionic, assuming that there was more than a little exaggeration of the progress on the Bionic vs D3. Now, however, I am beginning to wonder if the complaints may not have been somewhat justified. I know no one owes the D3 owners anything on the dev side, but to see the Bionic now able to use ROM Manager while I sit with a previously paid app that does nothing on my phone is admittedly frustrating. I keep reading posts saying that any Bionic developments will be followed rapidly by similar progress on D3, so I hope I can use ROM Manager on my phone in a few days.
pgzerwer said:
Until now I have been more or less bemused by the complaints that the Droid 3 was being somewhat neglected in the development community in favor of the Bionic, assuming that there was more than a little exaggeration of the progress on the Bionic vs D3. Now, however, I am beginning to wonder if the complaints may not have been somewhat justified. I know no one owes the D3 owners anything on the dev side, but to see the Bionic now able to use ROM Manager while I sit with a previously paid app that does nothing on my phone is admittedly frustrating. I keep reading posts saying that any Bionic developments will be followed rapidly by similar progress on D3, so I hope I can use ROM Manager on my phone in a few days.
Click to expand...
Click to collapse
Droid 3 Bootstrap on Market: https://market.android.com/details?id=com.koushikdutta.droid3.bootstrap and direct download: http://download.clockworkmod.com//test/Droid3Bootstrap.apk (ROM Manager support as well)
bam
If you have already purchased Rom Manager, just install it and have it install the custom recovery for you...
Edit: Maybe not.. it shows it installed CWR but I can't boot into it..
A large PayPal donation to the first flashable Rom!
Sent from my DROID3 using Tapatalk
Rocinante said:
If you have already purchased Rom Manager, just install it and have it install the custom recovery for you...
Edit: Maybe not.. it shows it installed CWR but I can't boot into it..
Click to expand...
Click to collapse
You have to use koush's bootstrap...
Sent from my DROID3 using xda premium
Just curious, outside of no custom kernels nothing else has to be used from the stock system, correct? So custom roms with our 512 of ram will be more than enough.
Sent from my DROID3 using Tapatalk
ROM Manager Premium Clockwork Recovery
OK, I am a believer now. No more pathetic whining by me, at least for the next 5 minutes or so.
Androidsims said:
You have to use koush's bootstrap...
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Yeah, I'm guessing there is a special way it boots into recovery with the custom app because I can't get Rom Manager to boot into recovery..
The only determining factor on whether I stick with OEM ROM or flash monster/steeldroid ROM is this: do these custom ROMs have a single bug?
So, users of monster and steeldroid ROMs: are there any bugs?
There are absolutely bugs in both ROMs but there are bugs in OEM too. Both SD and Monster run so much faster than stock. You can still do everything youre used to on the roms. CM7 had the phone broke at one point but even thats fixed now.
Thanks.
I've got one more question if anyone can answer it. Do either of these ROMs I mentioned work on the Verizon Wireless Droid 3 or the GSM Droid 3?
I own the Verizon Wireless one (gotta make sure I don't flash an incompatible ROM by accident).
What, DarkDroid not good enough for you? :'(
Anyways, all roms out right now have been made for the Verizon XT862.
dpwhitty11 said:
What, DarkDroid not good enough for you? :'(
Anyways, all roms out right now have been made for the Verizon XT862.
Click to expand...
Click to collapse
Being someone who doesn't enjoy flashing ROMs, I find it hard to tell which ROM does what but I thought I heard that Steel Droid and Monster were the oldest ones which made me assume they are more consistently stable.
poetryrocksalot said:
Being someone who doesn't enjoy flashing ROMs, I find it hard to tell which ROM does what but I thought I heard that Steel Droid and Monster were the oldest ones which made me assume they are more consistently stable.
Click to expand...
Click to collapse
Right now they're all equally consistent and reliable. Mine just hasn't been out as long, so less people are running it, but hopefully that'll change soon.
Sent from my DROID3 using XDA App
Lol I meant no disrespect. Although I know they have a decent user base, I have not tried dark droid, narcotics, or the other chinese rom (or whatever it is
Sent from my DROID3 using XDA App
Anyone else have problems with contacts forceclosing?
Sent from my DROID3 using XDA App
Ever since I flashed SteelDroid 3.0, the market app won't let me make purchases. I tried flashing Market 3.2, 3.0.26, and 3.1.something, and I tried the Root Explorer replace Vending and uninstall update method and nothing seems to work.
Not sure if its the ROM or something else, but very frustrating.
I'm having the same market problem with Monster, I brought it up in the Roms thread, hopefully it will be fixed in the next update
sent from my MONSTERDroid3 from the XDA app
i think you just need to wipe data/cache to get your market to work.
Yes wiping data and cache will fix the market purchases
Sent from my DROID3 using Tapatalk
Flashing with bootstrap Droid 3
I went in to the recovery mode of bootstrap and then went to safe mode to install zip from sd card and i got it to install. Although when I reboot in safe mode nothing starts and when i boot in regular mode it seems exactly the same? I was trying to get the monster rom on 1.2 need help am i missing a step>? I followed the instruction and i did not notice that i had done anything different.........
No issues with darkdroid or steeldroid 3 from what i've found with my own slight notification mods for both, not had any market buying issues with either, flush the cash of the app or reinstall the market, failing that reinstall your roms from scratch.
-smc
I am new to LG Revolution (trying to install custom ROM on sister's phone). I am coming from 2 different Samsung devices.
I have VZ6, 2.2.2, rooted. Windows 7 64
Here are my questions:
1) Thread http://forum.xda-developers.com/showthread.php?t=1121952
CWM download link gave me a "recovery-cwm-pr1.tar.gz", so I extracted it with 7-zip and get a "recovery-cwm-pr1.tar". How do I get the .img file??
2) What exactly is ADB shell? Where do I find instruction on that?
I assumed installation of Revolt 1.5 is straight forward after I get CWM on the phone. I am just having a hard time to follow those instructions on CWM tho.
Heya,
I'm no professional at all of this, but I'd recommend downloading the revotoolkit. i;ve not used it on vz6, but that is how most of us went about getting cwm. believe there is a thread about it in development (http://forum.xda-developers.com/showthread.php?t=1144951).
hope that helps you
I would get the GB update. Then root with using the post in development by mtmichealson. Then flash Gingervolt.
is the Gingervolt mature?? this is my sister's phone, so I am not going to flash it every week when there is a patch or update... I highly doubt my sister (technologically challenged) will appreciate Gingerbread anyways.
Gingervolt was just released so there will be more releases soon.
If she wouldn't appreciate it just get stock gingerbread on and leave it at that
Edit: not to take anything away from any the developers here don't take it that way please.
Sent from my VS910 4G using Tapatalk
pendragon11 said:
Heya,
I'm no professional at all of this, but I'd recommend downloading the revotoolkit. i;ve not used it on vz6, but that is how most of us went about getting cwm. believe there is a thread about it in development (http://forum.xda-developers.com/showthread.php?t=1144951).
hope that helps you
Click to expand...
Click to collapse
Thanks for the tip. Installed without sweat.
Nice to see people are still working on new ROM on this phone. All devs on Droid Charge have moved to Bionic and left us in the cold.
droidfever said:
Nice to see people are still working on new ROM on this phone. All devs on Droid Charge have moved to Bionic and left us in the cold.
Click to expand...
Click to collapse
That's gay
Haro912 said:
That's gay
Click to expand...
Click to collapse
Thankfully we have dedicated people here, who get excited about the little breakthroughs on this phone. The phone is great, the hardware is fast and responsive, the programming (from what I hear) is a disaster. All the Roms I have tested have been stableish on this phone, a couple force closes here and there, but nothing too intrusive. Gingerbread is perfect, and the Gingervolt from Mtmichaelson is stellar, no hangups, no force closes yet. I would expect themes to roll out soon, and some more stable Roms. I would assume the dream of CM7 is on the horizon now.
In agreement with Haro's comment, you will find that we will not simply give up on this phone, we have been through too much.
No worries, glad I could help. Props to thecubed for that one of course
Sent from my VS910 4G (pimp it) using XDA App
As I make progress towards making us an overclocked kernel I will keep m380w users informed in this thread. Wish me luck!
June 16, 2012 Had to post an updated torrent file.
May 01, 2012 New Firmware Released (NOT ICS)
Attached is a torrent file for FD19
Dec. 08, 2011 Development Halted
Here's the latest. The source code that Samsung makes available seems to have issues. I have tried and tried again to reproduce a stock kernel that will boot with the initramfs. However, the defconfig provided does not match the .config extracted from config.gz. There are some big differences between the two. The defconfig supplied with the source code defines the board as p4 yet the .config from the kernel defines it as p4wifi. So naturally I have tried both and I have tried many, many other things. All for not.
I contacted FOSS and the response was to the tune of, "We sent your message to the dev. team. If they respond, we'll respond. Until then, just wait."
With that said, I see no reason to muck about with trying to make an overclocked kernel, when there is no indication that I have valid source code.
Nov. 24, 2011
Here is a stock ROM of EK10, released 11/23/2011 for those who need or want it.
SHW-M380W.EK10.7z
Rooting directions and files I have tested and do work with this release can be found here on XDA
Nov. 26, 2011
I made some progress and have extracted the initramfs from the EK10 kernel using koush's AnyKernel. See attachments. One step closer to an overclocked kernel.
Pershoot has graciously offered his time and resources and built a recovery cwm_5.0.2.7_kor for the m380w. Which now displays correctly on this device.
He included the following notes:
UMS is not implemented (so the option will not work).
no radio/extra partitions will be available.
Click to expand...
Click to collapse
koe1974 said:
As there are only a few of us in here and nobody in Korea seems to be developing this model, I took it upon myself to retain this ROM from my most recent bout with Kies.
Here is a stock ROM of EK10, released 11/23/2011 for those who need or want it.
HOME_SHW-M380W.EK10.1207_CL583812_REV00_user_ship.tar.md5
Rooting directions and files I have tested and do work with this release can be found here on XDA
I hope to offer an overclocked kernel in the near future but we'll have to see.
Click to expand...
Click to collapse
Can you give a few more details?
Is it HoneyComb 3.2?
Is it for WiFi or 3G tablets?
BeeGee_Tokyo said:
Can you give a few more details?
Is it HoneyComb 3.2?
Is it for WiFi or 3G tablets?
Click to expand...
Click to collapse
It is Honeycomb 3.2. The shw-m380w is a wifi model.
Sent from my SHW-M380W using xda premium
One of the most noticeable difference is the integrated digital dmb tv and radio receiver and antenna. With no change in the look and dimensions. It comes wifi with or without 3g.
koe1974 said:
Nov. 26, 2011
Pershoot has graciously offered his time and resources and built recovery-cwm_5.0.2.7-sam-tab-10.1_kor_odin.tar.zip
He included the following notes:
Click to expand...
Click to collapse
refreshed:
http://droidbasement.com/db-blog/?p=2439
pershoot said:
refreshed:
http://droidbasement.com/db-blog/?p=2439
Click to expand...
Click to collapse
Excellent! Just completed a backup and all worked as expected.
Thanks
Sent from my SHW-M380W using xda premium
Thank you so much pershoot and Koe1974. Now, CWM can operate normally with my device. Actually, my device model is shw-m380s with 3g and I would like to ask you is it able to upgrade by CWM with the custom roms of P7500 (as overcome rom) and the overclock kernel?
Hi pershoot. I've just made a backup for my kor tab (model shw-m380s). Please help me to check the boot.img attached and let me know my device is able to apply your kernel or not. Thank you in advance.
Your device is not compatible with my kernel.
pershoot said:
Your device is not compatible with my kernel.
Click to expand...
Click to collapse
Thank for your reply Pershoot. Yesterday, I tried to patch your kernel and my tab couldn't boot, so I had to back to its stock kernel. I also upgraded my tab to Overcome Rom with stock kernel and it works fine exclude one issue is the brightness level couldn't adjust anymore. Because I am not good at hex and linux coding, so I appreciate if you or other developers could help me (and people own this device) to fix my stock kernel to make it is suitable with CWM roms and able to be overclocked. Thanks alot in advance.
Just to share some of my experience, I have an M380W model, I installed pershoot's CWM-based recovery, backed up everything, and installed Galaxy Task 6.2 ROM for a try (and 6.3 update). The screen keeps scrolling, but this is solved by restoring boot.img within the recovery.
I then have the same symptom as phuonglev, the screen brightness level can't be adjusted (set to medium and looks so), and I sometimes have orientation problems.
Could all this be resolved with your specific kernel koe1974 ?
I don't imagine it will. All I am planning at this point is to enable overclocking. It will essentially be a stock kernel. It sounds as if it is something in the rom causing the problem. As much as we would like to think the korean models are the same, from past experience with a galaxy s 'shw-m110s vs gt-i9000', the roms are just not interchangable. It always seems that there is 'something' that does not work as it should.
Sent from my SHW-M380W using xda premium
How is your progress Koe? I'm waiting for the good new from you.
Awesome, can't wait to see some progress.
I thought I was the only one with problems trying to use tasks rom.
Just FYI for any other M380W owners out there, you can supercharge your tab. Made a big difference for me.
*Edit
Btw Koe,
There is a small update for the M380W 10mb file from software update. After it downloads and reboots it's telling me that it failed to install. Any advice on how to get past this? (I'm rooted and supercharged).
aigoya said:
Btw Koe,
There is a small update for the M380W 10mb file from software update. After it downloads and reboots it's telling me that it failed to install. Any advice on how to get past this? (I'm rooted and supercharged).
Click to expand...
Click to collapse
If you are on EK10 then it is probably the update for Polaris Office. However, if you are not running the stock rom, your device may be reporting that is an p7500 or p7510 which I think comes with QuickOffice. So it might be confused.
Sent from my SHW-M380W using xda premium
could you upload the rom to other source please?
samoelito said:
could you upload the rom to other source please?
Click to expand...
Click to collapse
This is the best I can do ( http://www.wupload.com/file/2662167342/SHW-M380W.EK10.7z ). If you prefer bit torrent, let me know.
So, just to confirm.
If I want to root my device (I just picked it up yesterday) I need to download the
Samsung_Galaxy_Tab_10.1_root.zip file, then follow the instructions for apply the zip through recovery mode.
So what is the ek10.7z do? I understand it is a stock ROM....is it just for back up or why would it be needed? I guess I am just asking what is special about it
Then, who do you flash a ROM with this one?
I am familiar with the Korean ROMs and kernels. I have the m110s and have received so much help from Koe before Thanks for that.
I have taken over the old thread and have been trying to fill your shoes! hahhaa
[email protected] said:
So, just to confirm.
If I want to root my device (I just picked it up yesterday) I need to download the
Samsung_Galaxy_Tab_10.1_root.zip file, then follow the instructions for apply the zip through recovery mode.
So what is the ek10.7z do? I understand it is a stock ROM....is it just for back up or why would it be needed? I guess I am just asking what is special about it
Then, who do you flash a ROM with this one?
I am familiar with the Korean ROMs and kernels. I have the m110s and have received so much help from Koe before Thanks for that.
I have taken over the old thread and have been trying to fill your shoes! hahhaa
Click to expand...
Click to collapse
To root just follow the instructions and you will be fine.
ek10.7z is just the stock rom for if you choose to revert from back. currently, there doesn't seem to be much development going on for the m380w so I uploaded it for those brave enought to try roms built for other 10.1 models. I always delete tons of stock apps so it's helpful to have a stock rom to get back it i need to.
is flashing ROMS still the same?
Just using Odin and put the file into the PDA slot?
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