Database Info

Kernel Flashing Questions

Ok, sorry for the newb questions but this is the first time i am going to do something to any smartphone so there's somethings I don't understand.
1. Will I loose all of my data on my phone? I understand with flashing a new ROM i would but flashing a different kernel is different right? Also, what's the difference between a ROM and a kernel?
1b. If I will loose my data, is there anyway to back up some of that app data without being rooted? I know that once I am rooted I can use Titanium Backup.
2. Would you recommend using Odin to flash the Charge or something else? All of the instructions in the dev section say to use Odin but I've also seen some people say that you should use Heimdall and idk what that is. If you think I should use Odin, what version should i use?
3. Which kernel are you using and which one would you recommend.
4. If something goes wrong, you guys got my back right? lol
Thank you very much

1. No data loss.
2. Kernel is what the rom uses to operate in a sense. The kernel is what drives the phone, rom is what dresses it up.
3. I flash my kernels via cwm... but I use Odin for a lot as well. I use version 1.3 on my laptop and 1.7 on my gf's. Both do the same thing.
4. If you have problems people can help. Just read a lot before committing.

thanks for the reply.
actually, reading more into it, i think I want to flash the altered beast rom. with that there would be data loss right?

streetlightman said:
thanks for the reply.
actually, reading more into it, i think I want to flash the altered beast rom. with that there would be data loss right?
Click to expand...
Click to collapse
pretty sure when I flashed that it did wipe data.

I believe it doesn't touch data. It only has a system file no data or datadata
Sent from my SCH-I510 using XDA Premium App

thanks for the replies. so basically, all i have to do is hook up to Odin and flash it and I'm done? I don't have to do a manual data wipe before I flash it correct?
I'm running stock non-rooted ED2 right now if that matters.

papi92 said:
I believe it doesn't touch data. It only has a system file no data or datadata
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
You may be right, I lost data once in the first couple days, but don't remember what I flashed anymore.

didn't do a data wipe for me. still have angry birds data
thanks for all your help

How does the rom flashing process work?

I flashed a custom rom + kernal on my kindle fire it went by really smoothly and was a simple process..
Is doing it on the skyrocket different? Can flashing a rom get you a hard brick?
Also I'm thinking about a rom to flash where I can turn off LTE ( not in my area a huge battery waste ), but it sais I need to flash a new modem or radio or something.. dufuq is that?
Thanks,.

Read the forum and your questions will be answered

xcrazydx said:
Read the forum and your questions will be answered
Click to expand...
Click to collapse
I have and Im gonna try to do it tonight,I dont want to miss anything. Im just not the guy who has 450$ to go buy a new phone if my'n breaks

Any time you flash anything you risk a brick. It's uncommon, if you know what you're doing, but it happens. Almost Every ROM has specific instructions for flashing.

And make sure you do a nandroid backup first.
Sent from my SAMSUNG-SGH-I727 using xda premium

robin48 said:
And make sure you do a nandroid backup first.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Im doing a clockwordrecovery back up as we speak, does that work?
Also, how do I flash a modem? lol

Juicy555 said:
Im doing a clockwordrecovery back up as we speak, does that work?
Also, how do I flash a modem? lol
Click to expand...
Click to collapse
Yes, that's what a nandroid is.
Wipe cache, wipe dalvik.
Buddy, you need to stop what you're doing and read for a few days before flashing.

xcrazydx said:
Yes, that's what a nandroid is.
Wipe cache, wipe dalvik.
Buddy, you need to stop what you're doing and read for a few days before flashing.
Click to expand...
Click to collapse
I just made sure I did everything exactly it said and am now running a flashed rom

Do you know how warm I feel inside to see someone that actually READS?
And to clarify on ROM flashing, what happens is your internal storage is partitioned I to several parts. When you flash, you write to those partitions. For example, when you flash a recovery, it writes an image to that partition, similar to burning an ISO onto a CD. Hope that makes stuff a little clearer... so yes, if you're not careful, you're going to screw yourself over by telling your processor to do something it doesn't understand. It's like if I suddenly told you to go make me a sandwich in Chinese. Unless you understand Chinese, you would freak out and get confused.
Sent from my SAMSUNG-SGH-I727 using XDA

iandr0idos said:
Do you know how warm I feel inside to see someone that actually READS?
And to clarify on ROM flashing, what happens is your internal storage is partitioned I to several parts. When you flash, you write to those partitions. For example, when you flash a recovery, it writes an image to that partition, similar to burning an ISO onto a CD. Hope that makes stuff a little clearer... so yes, if you're not careful, you're going to screw yourself over by telling your processor to do something it doesn't understand. It's like if I suddenly told you to go make me a sandwich in Chinese. Unless you understand Chinese, you would freak out and get confused.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
And might possibly turn into a brick, don't forget that part.

[CAUTION][ICS][UPDATE][DOWNGRADE]Read before flashing ICS

After the ICS was leaked, it bought some good news and as well some bad news..
Some of our user have just bricked their mobile after performing a wipe data thru recovery..
The cause of error is yet unknown..
Out user vijai has published some of the known causes...
The credit goes to vijai for pointing it out
vijai2011 said:
CAUSES
Symptoms of super brick(caused by emmc bug):
1.Phone gets stuck at splash screen.
2.recovery gets stuck at whenever trying to access corrupted partition.
3.ODIN gets stuck at flashing factoryfs.
4.You can flash kernel but almost nothing else using both ODIN and cwm.
Sent from my GT-N7000 using xda app-developers
Click to expand...
Click to collapse
vijai2011 said:
FIX
No problem....temporary fix to avoid bricking is to avoid using cwm to flash anything,doing wipes in cwm,formatting partitions in cwm,doing factory reset through settings and by typing code in phone,removing large size files from sdcard.
The permanent fix is to disable MMC_CAP_ERASE in kernel while making it.Any kernel dev can do that easily I guess....
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
This definitely doesn't mean that all galaxy R handset are brick bug or you may encounter such problem..
Only a few have encountered the problem and the cause is yet unknown. This definitely, doesn't stop you from flashing ics..if you want to flash keep these things in mind.
Also, please do not completely rely on brick bug app from play store because the app (imo) is not supported to our device (correct me if i am wrong)
(i am no developer, just heard from my fellow user )
*****NOTE******
This applies to the Stock ROM released by machram and as well to all those ROM which are based/built upon the Stock ROM.
Click to expand...
Click to collapse
SO WHAT DOES IT MEANS TO YOU ?
If you have already flashed ICS, you are requested not to wipe data through CWM/Stock recovery and also do not factory reset the phone till the issue is identified. i.e. Once ICS === No Wipe (till its rectified)
Click to expand...
Click to collapse
Currently there are only two users who have hard bricked their phone after flashing ICS.
As you might be aware by now that the emmc brick bug app is not compatible with our phone.
The most elite developer Entropy512 wants to make it compatible and hence wants some sample..
Entropy512 said:
Can someone who experienced damage and still has their device contact me via PM? One of my contacts wants to collect a few damaged devices.
Click to expand...
Click to collapse
Note: I dnt recommend you to brick your phone
(thanks m.kochan, callmeventus, cooleagle)
A big thanks to entropy for showing interest to our device

Caution:
Here's what to say from a user who bricked his phone
mj.vikram said:
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck..
Click to expand...
Click to collapse
*******UPDATE********
Here is the new fix method
vijai2011 said:
And guys for the guide to safe flash:
Flash a GB kernel,boot into recovery,flash any rom.GB or ICS.Its safe to wipe in gb kernel.But once you flashed ICS you arent safe.If you need to wipe again,you need a GB kernel again.
This was the method we used in Note to wipe when had not got a safe kernel.
Click to expand...
Click to collapse
We have got one lucky user who is enough brave and tested this method
selva.simple said:
To make a conclusion to that, i have tested your method in Galax R buddy. I found that i had a GB kernel in my phone. So why wait till i reach home. Tested now itself. I tested two rounds. One is for getting ICS via CWM flash and the other is for getting ICS via CWM restore.
First Test:
1. Flashed GB kernel
2. Rebooted to Recovery
3. Wipe data
4. Flash ICS by CWM flash i.e., "Install from Zip" method
5. Reboot
Second Test:
First Three points are same. and finally Restored a nandroid backup of ICS i took earlier. Reboot
In both the method i was able to boot the phone and get the ICS ROM and ICS kernel. To add more,
After both boots, I tested the system apps and data apps - mainly Play store, Gmail, Music player, Gallery, Camera for any FC issues. Everything is working perfectly and no issues created apart from existing issues of ICS.
Click to expand...
Click to collapse

And I forgot to add that It is not necessary that brick occurs once you do the above said things....for example,brick may occur at 10th factory reset,100th flash etc....And it is safe to flash anything with Odin as it shouldn't invoke MMC_CAP_ERASE from kernel when flashing.
Sent from my GT-N7000 using xda app-developers app

vijai2011 said:
And I forgot to add that It is not necessary that brick occurs once you do the above said things....for example,brick may occur at 10th factory reset,100th flash etc....And it is safe to flash anything with Odin as it shouldn't invoke MMC_CAP_ERASE from kernel when flashing.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes i do agree..d problem may arise on 1st or on 100th wipe...
Bt the cause is yet unknown...
So imho, all the noobs shldnt do..who knows they get it for the first time...
Sent from my GT-I9103 using Tapatalk 2

Seriously? Removing large size files from sdcard can brick my phone?

Fusrodah said:
Seriously? Removing large size files from sdcard can brick my phone?
Click to expand...
Click to collapse
Dont know...but i have tried deleting large files as 1gb game data...such as max payne and asphalt7
No brick...
Sent from my GT-I9103 using Tapatalk 2

Fusrodah said:
Seriously? Removing large size files from sdcard can brick my phone?
Click to expand...
Click to collapse
Yes....sometimes.....it was reported by like 2 users have galaxy Note.While deleting large files,the phone stuck and force reboot caused damaged sdcard.
Sent from my GT-N7000 using xda app-developers app

vijai2011 said:
Yes....sometimes.....it was reported by like 2 users have galaxy Note.While deleting large files,the phone stuck and force reboot caused damaged sdcard.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Well, how much reports from Galaxy R users with bricks? I see one from mj.vikram. Anyone else?

So a little story now.
From where has this infamous brick bug appeared??
Analysis by kernel devs say that MMC_CAP_ERASE command in kernels are present from gb periods.But why hasn't it been causing problems in GB?That's because it was disabled as Google didn't see the need for it.
But in ICS they feel that just removing files causes security problems.so they thought of enabling MMC_CAP_ERASE command which will completely wipe instead of removing.
So why should it need to brick our devices?
That's because,one of the Google engineer said that our mmc uses buggy firmware that initiates wrong process when the kernel receives MMC_CAP_ERASE command.
Actually MMC_CAP_ERASE command and mmc buggy firmware are harmless on its own.But when both are combined the result is super brick.
Sent from my GT-N7000 using xda app-developers app

This is not the worst scenario. In worst case you're gonna get hardbrick with no possibility to turn your device on.
MMC_CAP_ERASE on - wasn't present in every ICS version, at least not for S2 (I know that NOte users had bigger problem with that). All previous 4.0.3 were totally safe. Latest 4.0.4 - unfortunately not. It's not really buggy firmware that causes any problem here. According to Entropy512 (I guess the best xda-expert in that matter) MMC_CAP_ERASE was activated in order to improve writing speed. Hard brick occur if the all three conditions are fulfilled here:
1) You have a faulty (brickable) emmc-chip
2) If MMC_CAP_ERASE command is activated in kernel
3) If you perform wipe/restore nand backup/install roms (wipe-type) where:
a) cwm recovery - very high risk
b) stock recovery - lower risk but still not equal 0.
So faulty emmc chip is a bomb, mmc_cap_erase is a fuse, wiping in cwm - is a trigger or fire!
Not all devices are endangered, only those with brickable emmc-chips. In regard to Note or S2 it's easier because those devices have great dev support and there were thoroughly examined. So there are known some ways to bypass this problem. In case of SGR is much harder. First of all ... we don't know which chips are really sane and which are not.

Fusrodah said:
Well, how much reports from Galaxy R users with bricks? I see one from mj.vikram. Anyone else?
Click to expand...
Click to collapse
Just two as of now so don't panic !
You can use ICS 4.0.4 but till the cause of the bricking is confirmed just don't preform any Wipe data / Wipe Cache / Factory reset operations while on ICS 4.0.4 ROM.
As per mkochan if you want to go back to the stock ROM for giving it to the service center / etc then directly flash GB / 2.3.x ROM without wiping the cache / data using CWM.
m.kochan10 said:
1) To avoid brick = don't wipe, don't do factory reset, do not restore nandbackups.
a) If you wanna to get rid of this fw.version
-> Flash a safe kernel / or best stock rom directly via Odin.
-> Wipe after installation process is done. NOT BEFORE!
2) To recover...one guy from Note section wrote a tutorial for those bricked devices that was able to turn on. He managed to recover it but he had to sacrifice 2-3 gb of internal storage. If device is not bootable then it's a motherboard replacement.
3) Turning off this function in kernel is not easy thing. I don't think this flag can be easily removed. I'm not a kernel guy....so I'm sorry but don't know much more about that. Our devs can take a look, maybe they can find a solution.
4) Bootloaders cannot be flashed via recovery, not via mobile odin either. And FW-odin version is still unavailable so I assume you still have GB ones.
5) About USB jig - Is your DM protocol the same like before? 2.0? (people with 2.1 have never been able to used jig as far as I remember)
Click to expand...
Click to collapse

Okay, we must wait for kernel with disabled MMC_CAP_ERASE. I hope we'll get it. Thanks for the information.

Oh my god
I did factory reset in ics because my keyboard dissappeared. Will my device hard brick?
I cannot understand why Samsung realeses a firmware which should make our mobile dead! What is this function even for?
Sent from my GT-I9103 using xda premium

You can find sort of explanation on the previous page

Just wondering should I worry about this if the bug eMMC app reports that I have a sane chip?

Google86 said:
Just wondering should I worry about this if the bug eMMC app reports that I have a sane chip?
Click to expand...
Click to collapse
I think app is not working for SGR, both user have used this app and app shown sane chip yet those both guys devices are bricked.
We should contact dev of app to make comp with SGR.
Sent from my CM7.2 powered Galaxy R using Tapatalk 2.

Damn it , I knew this would happen.....
"Friends forever." - Ventus

Guys actually you could check if you have any bad blocks in any partition through gpartrd in adb.Just looking its info.will post when I find some.
Sent from my GT-N7000 using xda app-developers app

OP please add this also,
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck ..
Sorry i have't seen this thread and created new one, so if you think i have created duplicate one please ask Justin to delete it....

mj.vikram said:
OP please add this also,
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck ..
Click to expand...
Click to collapse
Dude i dont have a GB Backup (CWM BACKUP)
and dude, what you gonna do now, how will you get back your phone ???

[Q] CWM or TWRP

There are a bunch of threads asking about the differences between CWM and TWRP, but I have a question that I think is more specific and I have not seen answered.
Is there any reason besides personal preference for using one over the other?
In most ROM installation guides and such they mention CWM. But I personally like using TWRP better. Does it actually matter? Is there something that I won't be able to do in TWRP that CWM does? So fare, it seems like they do the same thing.

There is nothing different as far as functionality, aside from being able to flash more than one package at a time and the ability to wipe cache and dalvik cache right after flashing a package. (Which I don't recommend doing, it might throw you into a boot loop upon rebooting) only wiping the regular cache is recommended right after flashing packages. Wiping dalvik is usually performed *before* you flash a package.
So, to answer your question... it's pretty much (but not all) cosmetic differences.. plus, the added ease of access features.
But when TWRP is compared to an outdated recovery system such as clock work mod, then yeah it seems like light years of differences. Yes I said it, CWM IS OUTDATED.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

_Zero said:
But when TWRP is compared to an outdated recovery system such as clock work mod, then yeah it seems like light years of differences. Yes I said it, CWM IS OUTDATED.
Click to expand...
Click to collapse
You can say anything you want, but that doesn't make it true. That outdated recovery is the only supported recovery for a lot of ROMs.

aycockonxion said:
You can say anything you want, but that doesn't make it true. That outdated recovery is the only supported recovery for a lot of ROMs.
Click to expand...
Click to collapse
Supported by whom lol twrp flashes everything cwm will to go as far as to say outdated is too far yes but to say twrp won't do it is just ridiculous this is why best threads are dumb
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Thanks
aycockonxion said:
You can say anything you want, but that doesn't make it true. That outdated recovery is the only supported recovery for a lot of ROMs.
Click to expand...
Click to collapse
This is the heart of my question. Do I need CWM for specific ROM's? And if so, why? You seem to suggest so.
Illnevertell said:
Supported by whom lol twrp flashes everything cwm will to go as far as to say outdated is too far yes but to say twrp won't do it is just ridiculous this is why best threads are dumb
Click to expand...
Click to collapse
But then here the suggestion is that it is not so.
Also, you state exactly why I didn't word this as a best thread. Because I also think those are dumb. They just get people spouting their personal opinions and using that as proof that one is better than the other.
I don't care which one people feel is better, I simply want to know whether there is anything I can't do with one (mainly TWRP) versus the other.
I would have to accept the responses to this thread as saying no, there isn't anything (important) that I can't do with one versus the other. There may be conveniences in one versus the other (like multiple zip installs at once in TWRP), but no show stoppers.
Thanks for your responses.

_Zero said:
There is nothing different as far as functionality, aside from being able to flash more than one package at a time and the ability to wipe cache and dalvik cache right after flashing a package. (Which I don't recommend doing, it might throw you into a boot loop upon rebooting) only wiping the regular cache is recommended right after flashing packages. Wiping dalvik is usually performed *before* you flash a package.
So, to answer your question... it's pretty much (but not all) cosmetic differences.. plus, the added ease of access features.
But when TWRP is compared to an outdated recovery system such as clock work mod, then yeah it seems like light years of differences. Yes I said it, CWM IS OUTDATED.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
sk8erwitskil's CWM touch is FAR from outdated (last updated 9/17/12). I personally prefer it to TWRP, but TWRP is great too.
You really can't go wrong with either one. Give each a shot and see what you like best.. it's a better route than asking some of the *cough* -opinionated- *cough* people around here.
.

Locoman_ said:
sk8erwitskil's CWM touch is FAR from outdated (last updated 9/17/12). I personally prefer it to TWRP, but TWRP is great too.
You really can't go wrong with either one. Give each a shot and see what you like best.. it's a better route than asking some of the *cough* -opinionated- *cough* people around here.
.
Click to expand...
Click to collapse
That's what I'm saying both work its all preference
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Locoman_ said:
sk8erwitskil's CWM touch is FAR from outdated (last updated 9/17/12). I personally prefer it to TWRP, but TWRP is great too.
You really can't go wrong with either one. Give each a shot and see what you like best.. it's a better route than asking some of the *cough* -opinionated- *cough* people around here.
Click to expand...
Click to collapse
This. You can't go wrong with sk8er's CWM Touch or TWRP. The only recovery you should stay away from is non-touch CWM. The older versions of button-mashing CWM have a history of doing bad things to Skyrockets.
If a ROM requires one recovery or another, the dev will specify as much. The dev may also suggest a certain recovery, even if it will work on the other. Lots of people like CWM, and lots of others like TWRP. Changing recoveries is not hard at all, so go ahead and try both. Get a feel for which you like more. Nothing to lose by trying them both out.
Kind of funny to see that there are recovery zombies out there. ROM zombies we all knew about, but recovery zombies? :laugh:

_Zero said:
There is nothing different as far as functionality, aside from being able to flash more than one package at a time and the ability to wipe cache and dalvik cache right after flashing a package. (Which I don't recommend doing, it might throw you into a boot loop upon rebooting) only wiping the regular cache is recommended right after flashing packages. Wiping dalvik is usually performed *before* you flash a package.
So, to answer your question... it's pretty much (but not all) cosmetic differences.. plus, the added ease of access features.
But when TWRP is compared to an outdated recovery system such as clock work mod, then yeah it seems like light years of differences. Yes I said it, CWM IS OUTDATED.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I have a Touchpad and a Skyrocket and I've always just installed the updates then wiped cache and dalvik. Are you saying that's not what you should be doing with CM9/CM10?

I personally like CWM Touch over TWRP as well.
But at the same does it really matter when it's a 5sec flash to switch between either one?

copene said:
I have a Touchpad and a Skyrocket and I've always just installed the updates then wiped cache and dalvik. Are you saying that's not what you should be doing with CM9/CM10?
Click to expand...
Click to collapse
Wiping dalvik will not brick you. I always wipe cache and dalvik 3 times before an update and one time after. Never had a bootloop caused by anything other than stupidity (forgot to wipe cache/dalvik before flashing 3 updates in a row, oops).
sb0 said:
But at the same does it really matter when it's a 5sec flash to switch between either one?
Click to expand...
Click to collapse
This. So much of this.

^^^ ??

sb0 said:
^^^ ??
Click to expand...
Click to collapse
I'm agreeing with you wholeheartedly.

Yea I just flashed twrp couple days ago. I will stick w cwm where I am more comfortable... at least until more justifiable reason(s) to switch.
Ppl say its outdated but u can also see this as a more widely tested product too (been around longer... more ppl are using, etc.).
Sent from my SAMSUNG-SGH-I727 using xda premium

Is rooting too risky?

Hello, i just got an asus tf300t running 4.1.1
After reading a bit about rooting the tablet, it seems a lot more dangerous and risky than other devices ive rooted in the past (HTC desire and Galaxy S3)
From what ive read so far this is what needs to be done right?:
-unlock using asus unlock tool
-flash a recovery using fastboot
-flash root through recovery
-optionally flash a rom later
There are so many post of people saying they have bricked their device, so it it really that dangerous compared to other devices?

chromium96 said:
Hello, i just got an asus tf300t running 4.1.1
After reading a bit about rooting the tablet, it seems a lot more dangerous and risky than other devices ive rooted in the past (HTC desire and Galaxy S3)
From what ive read so far this is what needs to be done right?:
-unlock using asus unlock tool
-flash a recovery using fastboot
-flash root through recovery
-optionally flash a rom later
There are so many post of people saying they have bricked their device, so it it really that dangerous compared to other devices?
Click to expand...
Click to collapse
You summed it up nicely. That is exactly what you need to do. I've done all but the optional ROM because stock is OK for me on this. Just follow directions and you should be fine. Don't flash an ICS recovery if you're running jb already. Don't wipe your system partition, etc.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

chromium96 said:
There are so many post of people saying they have bricked their device, so it it really that dangerous compared to other devices?
Click to expand...
Click to collapse
I think the non-brick group isn't necessarily as vocal as the bricked group. No one is starting a thread with the subject "All is fine!!! "
Sent from my Vivid 4G using xda app-developers app

bsaman said:
I think the non-brick group isn't necessarily as vocal as the bricked group. No one is starting a thread with the subject "All is fine!!! "
Sent from my Vivid 4G using xda app-developers app
Click to expand...
Click to collapse
Lol that's true, but compared to the q&a threads for other devices I've worked with, this one has a lot more people complaining about bricking.
Do you have any idea why?

Many of the people here who have bricked their device made the mistake of wiping the system instead of doing a factory reset. BIG difference. Lol
Hopefully one day the JB boatloader will have the same brickproof feature the ICS bootloader does.
Until then we'll have to be very careful.:thumbup:
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

Rooting this tablet is admittedly harder than most Android devices I'd encountered prior to purchasing it, but that's largely because of the instruction length. It's nothing more than downloading, copying, pasting, and clicking a few hard buttons. Simple, and there are lots of YouTube Videos that don't miss a beat when explaining how it's done. As long as you're exacting, the process is still pretty easy.
The benefits? A tablet that doesn't suck pretty badly. The lag on this thing prior to rooting made it virtually unusable for my needs at least.
That being said, people usually join forums to complain about things, which is why you get a disproportionate amount of "I bricked my device" comments. Typically it's operator head space that causes bricks, but it definitely happens at times to people despite having done everything correctly. It's just very uncommon in my experience.
Either way, the people on XDA are incredibly helpful and will go out of their way to try and fix any issue you encounter. If you're ever concerned about something, your best bet is to research on here, then ask if you can't find your answer. Good luck!
Sent from my HTC Sensation using xda app-developers app

I'd agree.
wetbiker7 said:
Many of the people here who have bricked their device made the mistake of wiping the system instead of doing a factory reset. BIG difference. Lol
Hopefully one day the JB boatloader will have the same brickproof feature the ICS bootloader does.
Until then we'll have to be very careful.:thumbup:
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
I'd definitely agree with this sentiment. Most of the support threads I see are because users didn't properly follow the directions.
As for rooting, it was incredible simple. (I rooted mine about a week ago.)
Where I ran into problems is when I tried to flash custom roms. First I tried to flash an older ICS based rom which I discovered doesn't work with the JB bootloader. Then I tried CM 10.1 Nightly, which had wifi issues for me. After some issues with recovery (admittedly my own fault) I was able to push the stock rom back on via ADB system flash command.
After I was back in stock, I was able to easily re-root. So now I am back on 10.4.2.9-Stock rooted.
Even if you think it's too risky to flash custom roms, it's still worth rooting the device. It's hardly risky and you can just reflash stock recovery after you are done.
The ability to remove bloatware and use apps like titanium backup is really worth it.

porksandwich9113 said:
I'd definitely agree with this sentiment. Most of the support threads I see are because users didn't properly follow the directions.
As for rooting, it was incredible simple. (I rooted mine about a week ago.)
Where I ran into problems is when I tried to flash custom roms. First I tried to flash an older ICS based rom which I discovered doesn't work with the JB bootloader. Then I tried CM 10.1 Nightly, which had wifi issues for me. After some issues with recovery (admittedly my own fault) I was able to push the stock rom back on via ADB system flash command.
After I was back in stock, I was able to easily re-root. So now I am back on 10.4.2.9-Stock rooted.
Even if you think it's too risky to flash custom roms, it's still worth rooting the device. It's hardly risky and you can just reflash stock recovery after you are done.
The ability to remove bloatware and use apps like titanium backup is really worth it.
Click to expand...
Click to collapse
OK i think in going to root. Which guide do u use?
Also were you on the stock 4.1.1 ROM while rooting?

You may want to start here.
http://forum.xda-developers.com/showthread.php?t=1949758

wetbiker7 said:
Many of the people here who have bricked their device made the mistake of wiping the system instead of doing a factory reset. BIG difference. Lol
Hopefully one day the JB boatloader will have the same brickproof feature the ICS bootloader does.
Until then we'll have to be very careful.:thumbup:
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
According to CLEANROM installment guide.
"• OPTIONAL: Wipe data / Factory Reset in Recovery if coming from a non-Stock Rom"
it seem need to wipe data / Factory Reset in Recovery. Did you do it?

z1022 said:
According to CLEANROM installment guide.
"• OPTIONAL: Wipe data / Factory Reset in Recovery if coming from a non-Stock Rom"
it seem need to wipe data / Factory Reset in Recovery. Did you do it?
Click to expand...
Click to collapse
its ok to do a full wipe in a custom recovery like twrp or cwm. I believe that when he said dont wipe the system, he meant dont wipe using the stock bootloader as that has caused many bricks.
If someone could confirm that would be great.

chromium96 said:
its ok to do a full wipe in a custom recovery like twrp or cwm. I believe that when he said dont wipe the system, he meant dont wipe using the stock bootloader as that has caused many bricks.
If someone could confirm that would be great.
Click to expand...
Click to collapse
+10
See my signature!
To be fair there have been five I have worked with who did recover.
The others weren't so lucky!

When I got my TF300T ICS .29 (no root and no unlock). I use WIPE DATA on the bootloader (stock recovery). Lucky, no bricks.

chromium96 said:
its ok to do a full wipe in a custom recovery like twrp or cwm. I believe that when he said dont wipe the system, he meant dont wipe using the stock bootloader as that has caused many bricks.
If someone could confirm that would be great.
Click to expand...
Click to collapse
Yes as already pointed out don't wipe from the bootloader especially of you are on an older recovery version or a pre jb bootloader with a newer recovery. Brick....
Your sig pic is massive and quiite intrusive by the way.

well im as thick as a brick and ive rooted while ics flashed roms, updated to jellybean and re rooted so if i can do it anyone can lol

Can I understand as below?
Don't use stock bootloader to wipe the data.
Can use TWRP and CWM to wipe the data.
Right
---------- Post added at 12:58 PM ---------- Previous post was at 12:57 PM ----------
sbdags said:
Yes as already pointed out don't wipe from the bootloader especially of you are on an older recovery version or a pre jb bootloader with a newer recovery. Brick....
Your sig pic is massive and quiite intrusive by the way.
Click to expand...
Click to collapse
Can I understand as below?
Don't use stock bootloader to wipe the data.
Can use TWRP and CWM to wipe the data.
Right

z1022 said:
Can I understand as below?
Don't use stock bootloader to wipe the data.
Can use TWRP and CWM to wipe the data.
Right
---------- Post added at 12:58 PM ---------- Previous post was at 12:57 PM ----------
Can I understand as below?
Don't use stock bootloader to wipe the data.
Can use TWRP and CWM to wipe the data.
Right
Click to expand...
Click to collapse
I would think the function inside the rom itself in the settings would be ideal.
As for the bootloader wipe, if you are using, or have used a custom rom, then a data wipe via the bootloader is not recommended and I think has caused a few bricks, but for those who have stock loaded and have never utilized a custom rom, there should not be an issue. If I'm wrong please correct me.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2