i815 ICS install to prevent brick bug? - Galaxy Tab 7.7 Q&A, Help & Troubleshooting

Hey guys, I am about to flash a rom for the first time on my Galaxy Tab 7.7. I have done so on other Samsung devices but this is the first time on a device with known bad eMMC so I am really afraid of the brick bug.
So what I do is this right?:
Flash CWMR 6.0.1.1 in the Development forum (which prevents brick bug right?)
Flash ICS V2 file provided by electron
Wipe everything and then good to go?
I read that you should never wipe on Stock Roms due to the brick bug but does 6.0.1.1 prevent that special brick wipe from happening? So I can wipe with this Stock ICS Rom?
Also does the ICS V2 lock the bootloader? I read that some were finding out that the bootloader is locked but I did not know if it was locked from the beginning or possibly later by flashing either the smaller 29.3MB file from Verizon or the bigger ICS file?

Thread moved to Q & A section.

Related

Remove Bootloader from Stock Rom's

Hey Guys,
I want to flash a original stock ROM to flash on my galaxy 3, i am seeing the the stock ROM's on SamMobile but i am super unsure to flash them
What should I do to remove the bootloader for a safe flashing? What files should I delete and how to?
Yea i also want to know how to do that if somebody can please explain this !
You have the Samsung Galaxy S3 ?
You don't want to "remove" any kind of bootloader. Removing the bootloader would cause your phone to not boot up. Sometimes people need to unlock a bootloader, but you shouldn't have to with your phone.
If someone told you to delete the bootloader, they are probably trolling you and want you to break your phone.
Did you get the phone from someone who had already rooted / installed a custom ROM ? If so, I highly recommend wiping EVERYTHING, including recovery so you can get a fresh start and nothing will be left over.
You don't need to do anything to the bootloader for the Samsung Galaxy S3.
You should factory reset and use the computer program Odin to flash stock ROM + recovery. You can find out how to do that in detail in the forum for the Galaxy S3.
Remove boot loader trololol lol sure if you want to hard brick your phone and you have a Samsung they open no unlocking
Sent from my SCH-I500 using Tapatalk 2
He means removing the new bootloader included in recent OTA's from the OTA itself. The new bootloader will up your flash counter just for having a custom ROM on your phone, rather than flashing one.

[Q] Clarify if possible brick or not

Hi;
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm , will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance
doaft said:
Hi;
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm , will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance
Click to expand...
Click to collapse
Problem emmc bug is kernel , is not wipe data factory reset with recovery , if you brick,this problem a defective eMMC chip/fwrev that is unable to handle eMMC ERASE commands, A kernel that allows attempts to erase a partition to actually happen. (as opposed to reporting "not supported" and doing nothing.) - A common way of rendering a kernel safe is to remove MMC_CAP_ERASE from the capability flags in drivers/mmc/mshci.c ,
A recovery binary that attempts to erase partitions when formatting them. Most ICS recovery binaries fit in this category, most Gingerbread recoveries do not attempt to perform an erase operation so are safe. Note that also, an affected update-binary in a ZIP could be a cause of problems too. (e.g. flashing a firmware that has an ICS update-binary and formats the partition could cause a problem even with a "safe" recovery.) So a kernel can be repacked with a "safe" CWM but it will still only be partially safe.
custom kernel MMC_CAP_ERASE safe is kernel cm10...
devid801 said:
Problem emmc bug is kernel , is not wipe data factory reset with recovery , if you brick,this problem a defective eMMC chip/fwrev that is unable to handle eMMC ERASE commands, A kernel that allows attempts to erase a partition to actually happen. (as opposed to reporting "not supported" and doing nothing.) - A common way of rendering a kernel safe is to remove MMC_CAP_ERASE from the capability flags in drivers/mmc/mshci.c ,
A recovery binary that attempts to erase partitions when formatting them. Most ICS recovery binaries fit in this category, most Gingerbread recoveries do not attempt to perform an erase operation so are safe. Note that also, an affected update-binary in a ZIP could be a cause of problems too. (e.g. flashing a firmware that has an ICS update-binary and formats the partition could cause a problem even with a "safe" recovery.) So a kernel can be repacked with a "safe" CWM but it will still only be partially safe.
custom kernel MMC_CAP_ERASE safe is kernel cm10...
Click to expand...
Click to collapse
I appreciate the reply but am afraid that it is to technical for me to understand, I know just the very basic things like using a launcher
and taking updates mentioned cwm in my earlier reply just to say i dont have it and wont use it,so thanks again for the reply, but if you dumb it down for me, is there a chance of bricking if i just do the update and go launcher
thank you
doaft said:
I appreciate the reply but am afraid that it is to technical for me to understand, I know just the very basic things like using a launcher
and taking updates mentioned cwm in my earlier reply just to say i dont have it and wont use it,so thanks again for the reply, but if you dumb it down for me, is there a chance of bricking if i just do the update and go launcher
thank you
Click to expand...
Click to collapse
Simple answer = YES!
If you update with CWM, there is CHANCE of eMMc bug bricking.
If you just install go laucher or apps from google market..you are fine.
What "devid801" stated is the protocol/procedures for updating safely
acuratlsfan said:
Simple answer = YES!
If you update with CWM, there is CHANCE of eMMc bug bricking.
If you just install go laucher or apps from google market..you are fine.
What "devid801" stated is the protocol/procedures for updating safely
Click to expand...
Click to collapse
thank you so much
http://forum.xda-developers.com/showpost.php?p=29616187&postcount=9
i think this program is very usefull to see if you have such a bad emmc =)

[Q] Summary / Overview - Upgrade to JB

Hi all,
I am farily new to Android and by reading the forum have been able to root and am using ClockWorkMod o my Galaxy Note 10.1 8013. I am pretty happy with all that
So now that JB is out, I went to settings on the Device and did the sofware updated. It download a ~500MB files, then rebooted into CWM which attempted to load the firmware. It then gave me a text error that looked like some code evaluation that was failing (sorry, I did not write it down)
I made backups of my device using CWM, both to the internal card and to the extsdcard. However the external backup failed becuase it could not access /data. I also created an update.zip on the intneral card.
I've read that I *might* be able to upgrade to JB via Kies, but I see a lot of problem posts with this.
So my questions are:
- What is the right/best way to upgrade to JB?
- Do I need to revert to stock firmware first?
- If the Kies process works, will that wipe my data?
- What is the best way to wipe my data and then restore it?
- If I create a full backup using CWM and restore it, does that backup include ICS (hence overwriting JB if I successfully upgrade)?
- I see the term ROM, firmware, OS tossed around alot; I know what these terms mean, but is there any difference, for instance I would think that both CWM and JB are firmware and ROMS and JB is the OS. So when people speak of ROM and firmware what are they really referring to?
- Will I lose all my data and apps and if so what is the best way to back them up and restore them? (I have both the CMW Backup and Titanium backups)
- Is there a cannonical reference for steps like this? It seems like there are alot of questions and suggestions but I cannot find a complete reference.
Thanks in advance. I apologize if this info is readily available in one spot. I've not found it yet.
Jon.Willard said:
Hi all,
So now that JB is out, I went to settings on the Device and did the sofware updated. It download a ~500MB files, then rebooted into CWM which attempted to load the firmware. It then gave me a text error that looked like some code evaluation that was failing (sorry, I did not write it down)
Root phones may fail OTA update .
So my questions are:
- What is the right/best way to upgrade to JB?
Samsung use Kies or OTA
- Do I need to revert to stock firmware first?
No if using Kies .
- If the Kies process works, will that wipe my data?
No
- What is the best way to wipe my data and then restore it?
CWM Recovery format data sd card .
- If I create a full backup using CWM and restore it, does that backup include ICS (hence overwriting JB if I successfully upgrade)?
Backup is whatever you backed up .
- I see the term ROM, firmware, OS tossed around alot; I know what these terms mean, but is there any difference, for instance I would think that both CWM and JB are firmware and ROMS and JB is the OS. So when people speak of ROM and firmware what are they really referring to?
CWM is advanced recovery not firmware .
OS is Android system .
Rom is a firmware of any type .
-
- Is there a cannonical reference for steps like this? It seems like there are alot of questions and suggestions but I cannot find a complete reference.
There are reference posts covering flashing and rooting .
http://forum.xda-developers.com/showthread.php?t=2080366
But as to a full guide no and as 99% refuse to read the basics faqs and guides i would not compile one .
jje
Click to expand...
Click to collapse
Well what you can do is download the JB stock firmware and then install it using Odin.
I would advice against installing OTA using CWM it is not a safe method.
Both the download link and tutorial can be found on the links in my signature
Thanks guys, this helped a lot
I used Kies to get JB installed, that wiped CWM and Root, so I just redid that process (a lot easier this time). So it seems like the 'Recovery mode' is a special boot firmware that can be used to load other firmware. So what I did was, downloaded and installed the new JB OS firmware which put the stock Recovery firmware back in place, upgrade the OS and left all my apps and data alone. Then I used ODIN to load the CWM firmware and then I applied the root software from the zip file. Sound like an accurate summary?
How does the root software actually work? I am familiar with froot on Unix but this seems different.

[Q] Installing CM10.1 on top of 4.2.1 bootloader

So, I decided to install CM10.1 on my TF300T, because I want to get some customization. But, there is 3 major questions where answers are yet to be found. I'm on official 4.2.1. My bootloader is locked. No root(but I've had a lot of root experience with my Xperias).
1) Is it safe to install TWRP on new bootloader? What are the pitfalls which I can encounter?
2) Is it safe to install CM10.1? Or I'll get the nice white and black brick? Again, what are the pitfalls?
3) What are the problems with current CM10.1? What is malfunctioning?
Thanks in advance and sorry for newbie questions - the process with this tablet is much different from Xperia phone, and the risk of bricking it is way too high for me to experiment(unlike Xperia, where I flashed BAT file into kernel partition on mistake, and restored it without any hassle).
You can't.
CM10.1 is using 4.1 bootloader. Forcing anything in this direction will result in brick. You can only flash stock 4.2.1 or CROMI 4.2.1
About twrp read guides. There are two versions for both bootloaders. Don't mess them or another brick will happen.
It won't boot so no point in trying.
If you want CM10.1 you need to downgrade the bootloader to 4.1.1. first. See thread in general for how to do that.
Dr.Alexander_Breen said:
So, I decided to install CM10.1 on my TF300T, because I want to get some customization. But, there is 3 major questions where answers are yet to be found. I'm on official 4.2.1. My bootloader is locked. No root(but I've had a lot of root experience with my Xperias).
1) Is it safe to install TWRP on new bootloader? What are the pitfalls which I can encounter?
2) Is it safe to install CM10.1? Or I'll get the nice white and black brick? Again, what are the pitfalls?
3) What are the problems with current CM10.1? What is malfunctioning?
Thanks in advance and sorry for newbie questions - the process with this tablet is much different from Xperia phone, and the risk of bricking it is way too high for me to experiment(unlike Xperia, where I flashed BAT file into kernel partition on mistake, and restored it without any hassle).
Click to expand...
Click to collapse
hi
I'm tryng since three days stacked at cyanogen logo... no way to have the cm10.1 for the moment, only stock, but I have installed the specific recovery twrp 2.4.4.0 for the bootloader 4.2 and it work fine to get the root acces and to do backup and restore
we have to wait a little more

[Q] Is there any risk by doing full wipe in jb stocked rooted with CW 6.0.3.0?

My model is P6800. After updating to JB stocked, i rooted it and until now i've never done a full wipe. I have CWM Recovery v6.0.3.0.
The problem of the brickbug in ICS is still present in JB? Can i perform a full wipe without any problems? Maybe i decide to install the ROM Skyhigh 3.5. Thank you very much!!!
Edit: I confirmed that i have the wrong emmc chip, so thats why i ask about the risk.
Edit: I aswer myself. Seems not to have any problem. I could install Skyhigh 3.5 without any problem.

Categories

Resources