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
Related
Hi guys, I recently downloaded the app from this XDA user that verifies if you're in danger of bricking your device.
Apparently I am, the app says 'this is a chip with KNOWN issues'. I don't really understand what causes the issue, if I'm actually in danger or I just shouldn't do XYZ. Would anyone with more knowledge please take the time to explain as best they can what the situation is?
I'm running AOKP with UCLE2, and it seems plenty of people are sticking with ICS roms so it doesn't seem to be that heavy a situation.
I'm pretty sure the brickbug is only caused from recoveries that use ICS kernels. Currently the skyrocket doesnt have any recovery available that has an ICS kernel so I'm pretty sure were in the green.
BaconStep said:
I'm pretty sure the brickbug is only caused from recoveries that use ICS kernels. Currently the skyrocket doesnt have any recovery available that has an ICS kernel so I'm pretty sure were in the green.
Click to expand...
Click to collapse
Thank you, from what I was reading it had to do with a method of erasing that corrupted the eMMc, but I honestly didn't understand anything more than that and from the thread here it basically said 'if you flash a ROM, it may be your last'.
There was a lot of technical talk that I didn't quite follow.
And I am aware this isn't Q/A forum, but a possible hard brick I thought deserved more light.
whosgotlag said:
Thank you, from what I was reading it had to do with a method of erasing that corrupted the eMMc, but I honestly didn't understand anything more than that and from the thread here it basically said 'if you flash a ROM, it may be your last'.
There was a lot of technical talk that I didn't quite follow.
And I am aware this isn't Q/A forum, but a possible hard brick I thought deserved more light.
Click to expand...
Click to collapse
yes and no, but its not by flashing rom with cwm read this http://forum.xda-developers.com/showthread.php?t=1621679
whosgotlag said:
Thank you, from what I was reading it had to do with a method of erasing that corrupted the eMMc, but I honestly didn't understand anything more than that and from the thread here it basically said 'if you flash a ROM, it may be your last'.
There was a lot of technical talk that I didn't quite follow.
And I am aware this isn't Q/A forum, but a possible hard brick I thought deserved more light.
Click to expand...
Click to collapse
I might not be %100 on the money but I remember something with ics leaks and recoveries cause super bricks.
Sent from my SAMSUNG-SGH-I727 using xda premium
It's not flashing a ROM that causes bricks. It's using the wipe functions with ics kernels. Aka, if you're on ics and you have one of the chips in question, and you perform wipe functions in cwm you have a good chance of bricking at some point. Maybe not next time, maybe not in the next 30 wipes, but it will most likely happen at some point according to what's been happening with other users of the chips.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
My understanding is that if you use a gingerbread based cwm (which is any of the cwm versions posted on XDA) to wipe that you "should" be safe. It's when you use Factory Data Reset while on ics using the gui that you risk getting the bug. (ie DO NOT go into Settings/Backup and Reset/Factory Data Reset).
EDIT: Also do not go into stock 3e recovery to wipe data after flashing the one-click leaks. I'm assuming that recovery was based on an ics kernel, but I could be wrong about that. But to be safe, DON'T!
This post explains that it is because the Skyrocket and t989 have separate recovery and kernel partitions: http://forum.xda-developers.com/showpost.php?p=27140915&postcount=122
I'm not completely sure now as there seems to be two differing takes on the situation. I am on AOKPs latest R4INS linaro build, using the 5.8.somethingsomething recovery from here. I've been told it's a Gingerbread Recovery. But I don't know how to actually tell or what the difference is.
If the problem is ICS recovery then I should theoretically be fine. If the problem is ICS builds in general then I'm in danger. And if the problem is ICS kernel then I'm not sure if I'm in danger, I haven't specially flashed a new kernel, but I'm not sure if they are included with the ROM.
I'm sorry for these lines of questions. Still learning the technical aspect.
Its wiping with anything using an ics kernel so either from or recovery none of our recoveries use ics so that leads us to roms atm
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Is this issue expected to persist even once official ICS is released and specifically isolated to rooted devices, or should this be solved once we have the final build?
When I had my gs2 i777 and the bug first showed up it only affected users who flashed the leaked stock ics kernel. Those on custom kernels such as cm9 or aokp were not affected. Also page 7 of the gotbug app post (linked by the op in this thread) has all of the details posted by entropy512 the Dev who discovered the bug.
Sent from my SAMSUNG-SGH-I727 using xda premium
whosgotlag said:
I'm not completely sure now as there seems to be two differing takes on the situation. I am on AOKPs latest R4INS linaro build, using the 5.8.somethingsomething recovery from here. I've been told it's a Gingerbread Recovery. But I don't know how to actually tell or what the difference is.
If the problem is ICS recovery then I should theoretically be fine. If the problem is ICS builds in general then I'm in danger. And if the problem is ICS kernel then I'm not sure if I'm in danger, I haven't specially flashed a new kernel, but I'm not sure if they are included with the ROM.
I'm sorry for these lines of questions. Still learning the technical aspect.
Click to expand...
Click to collapse
If you are on an ics ROM, you would be on an ics kernel. Therefore you would have a chance of bricking if you wipe.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
If you are on an ics ROM, you would be on an ics kernel. Therefore you would have a chance of bricking if you wipe.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
But doesn't recovery not use the same kernel as the ROM uses?
Well I'm on the leak but I'm not gonna take the chance and wipe anything. If I really needed to do a wipe or a factory reset I would just fire Odin up and flash back stock and then do a wipe. But from what I've read if I understand it right and correct me if I'm wrong it only happens when you wipe or reset using either cwm or GUI and select to format SD. If I understand it right as long as you don't format the SD when wiping or factory data reset you should be OK. So please someone if I've misunderstood please correct me... as I said if I need to wipe or reset I'll flash back to stock and do it.. your gonna lose your data either way so might as well not take the chance...
Sent from my SAMSUNG-SGH-I727 using xda premium
garydv2002 said:
Well I'm on the leak but I'm not gonna take the chance and wipe anything. If I really needed to do a wipe or a factory reset I would just fire Odin up and flash back stock and then do a wipe. But from what I've read if I understand it right and correct me if I'm wrong it only happens when you wipe or reset using either cwm or GUI and select to format SD. If I understand it right as long as you don't format the SD when wiping or factory data reset you should be OK. So please someone if I've misunderstood please correct me... as I said if I need to wipe or reset I'll flash back to stock and do it.. your gonna lose your data either way so might as well not take the chance...
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
as of now, all cwm recoveries on this i727 forum r based in gb, even if u flashed a rom based on the ics, cwm is never part of the rom as it is flashed seperatly, the only time that would happen is when u odin a stock firmware
garydv2002 said:
Well I'm on the leak but I'm not gonna take the chance and wipe anything. If I really needed to do a wipe or a factory reset I would just fire Odin up and flash back stock and then do a wipe. But from what I've read if I understand it right and correct me if I'm wrong it only happens when you wipe or reset using either cwm or GUI and select to format SD. If I understand it right as long as you don't format the SD when wiping or factory data reset you should be OK. So please someone if I've misunderstood please correct me... as I said if I need to wipe or reset I'll flash back to stock and do it.. your gonna lose your data either way so might as well not take the chance...
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Do not wipe anything on ics atm in GUI cwm is your friend
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
skrambled said:
My understanding is that if you use a gingerbread based cwm (which is any of the cwm versions posted on XDA) to wipe that you "should" be safe. It's when you use Factory Data Reset while on ics using the gui that you risk getting the bug. (ie DO NOT go into Settings/Backup and Reset/Factory Data Reset).
EDIT: Also do not go into stock 3e recovery to wipe data after flashing the one-click leaks. I'm assuming that recovery was based on an ics kernel, but I could be wrong about that. But to be safe, DON'T!
This post explains that it is because the Skyrocket and t989 have separate recovery and kernel partitions: http://forum.xda-developers.com/showpost.php?p=27140915&postcount=122
Click to expand...
Click to collapse
This exactly. The stock recoveries are the main dangerous part. Flash off of it before you do anything. While we have the same problem with the chip, it seems we're not likely to encounter it if you don't use the format operations while on the ics kernels. The 4 current modded recoveries we have are all based on gingerbread. (well 3 are, and the fourth is believed to be unless he has his own leaks)
nrm5110 said:
Do not wipe anything on ics atm in GUI cwm is your friend
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
The bottom line is all wiping (for sd/usb cards too) should be done with a gb cwm if you're using an ics based rom. Correct?
Sorry to beat a dead horse but the amount of information and disinformation out there is staggering...
Locoman_ said:
The bottom line is all wiping (for sd/usb cards too) should be done with a gb cwm if you're using an ics based rom. Correct?
Sorry to beat a dead horse but the amount of information and disinformation out there is staggering...
Click to expand...
Click to collapse
Agreed. I've looked at MANY threads and everyone seems to have a different idea of what causes the brick and what steps to take to avoid it. I've read cwm wiping can cause the brick but here it says cwm is safe. Its hard to know what to think
Sent from my soon to be rooted I727
Mike on XDA said:
Agreed. I've looked at MANY threads and everyone seems to have a different idea of what causes the brick and what steps to take to avoid it. I've read cwm wiping can cause the brick but here it says cwm is safe. Its hard to know what to think
Sent from my soon to be rooted I727
Click to expand...
Click to collapse
My understanding is that when on an ICS based rom wiping with a GB based recovery IS ok. Wiping with an ICS based recovery is NOT ok. Using the ICS gui to wipe is NOT ok.
Would love to have this confirmed.
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
aperture said:
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
Click to expand...
Click to collapse
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
riverboat2001 said:
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
Click to expand...
Click to collapse
As long as you are using cm, I don't think it will be a problem. I will never go back to official. The problem stems from an issue with the stock recovery from Samsung. So in short, the devs are aware of the issue, but Samsung doesn't seem to care. As long as you are running the current cwm, and the dev isn't an idiot, you shouldn't have a problem. (No offense aorth and locerra, I know you're aware)
Sent from my Galaxy Tab 7 Plus
riverboat2001 said:
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
Click to expand...
Click to collapse
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
wingie6200 said:
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
Click to expand...
Click to collapse
Wow, thanks so much for taking the time to offer your advice.
I only have myself to blame for getting into this pickle! After Flashing so many different ROM's on loads of devices i just got a bit blaiz'e
Last night i did a wipe and factory reset through CWM and it all went well, so my question is, giving that i know i'm at risk, i can see three options,which is the "safest"
1/ Put tab away and don't use it until Samsung release a fix we can use
2/ Keep using the tab, but have that worrying niggle in the back of my mind
3/ Follow the post above and carry out the suggested procedure outlined above? (is it 1000% safe?
Can i assume that if i go as far as recovery mode via the ICS version to see the "recovery 3e" but don't wipe/factory reset i'm safe?
And consequently if i DON'T see that i would be safe to go ahead?
I do feel as if I'm sitting on a time-bomb here
(years ago i would have spent weeks messing around with this sort of thing, but as a middle aged housewife thats always on the go, i don't have the time, I just like to get my stuff working fast and bloatware free and i'm happy!)
Once again thanks for your input.
lol cant guarantee the 1000% safe part (since the offending code is in part coming from samsung) but people are aware of it / working to fix it and all non stock stuff is most probably safe. the CWM 6.0.1.0 definitely is, just used it myself.
and these things are kinda random (if all posts are to be believed) so i would just use the tab normally and worry about it much.. reports also say that samsung does repair these bricked tabs under warranty in case the unthinkable does happen.
and its not a time bomb :laugh:! (although there would probably be an app for that somewhere..)
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
ringnutz said:
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Kuniokun said:
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Click to expand...
Click to collapse
Yeah, I did.. happened the first time
Sent from my myTouch 4g via Tapatalk
Brickbug is caused by ****ty flashing firmware on some of our devices.
No danger with cwm 6.0.1.0 from aorth. We r safe!
Sent from my GT-P6200 using xda app-developers app
Hi all
Please could someone in the know give me definitive instructions how to root and upgrade in the safest possible way, avoiding the brick bug.
I have a P6810 which was imported from France (XEF) running HC. There is no Samsung update available and I want at least ICS if not JB.
I have read all I can but got myself confused about the safest way to proceed.
If I have understood correctly, the safe way is to root, install Locerras CWM and then I am safe to factory reset or wipe. Then I can install any custom rom or Sammy rom for the 6810.
Should I use Odin or CWM or mobile Odin?
I do know pretty much what Im doing having been rooting and installing since my HTC Desire days, but this brick bug has me scared!
Sorry, meant to post in General not Development - MOD please move
Yup wrong section.
Here the best place to upgrade via Odin from xenix: http://forum.xda-developers.com/showthread.php?p=21930173
No problem, mistakes happen. Moved
Astrix Ashburn said:
Yup wrong section.
Here the best place to upgrade via Odin from xenix: http://forum.xda-developers.com/showthread.php?p=21930173
Click to expand...
Click to collapse
Yep, I have read that thread through and through and I am quite happy with how to root, how to use Odin etc, and have done it many times on different phones and tablets.
Unfortunately I have picked up snippets all over the place like "Don't factory wipe in stock recovery" and "Locerras CWM is 100% safe to wipe and factory reset".
I was just hoping that someone could confirm the best way to go, and things not to do and the safest program to use to flash. Should I use a particular kernel? Some seem to be safer than others...
Same here P6800
Hi aslo want a guide for avoiding the brick bug. On HC here too but P6800.
Already bricked one P6800. So Im a lillte bit paranoid...
I know that there are NO guarantees.. But please. help out with a dodge the brick bug guide. I really want back to CM10 asap.
Thank you all in advance!!!
Nobody want to commit themselves? I am still reading horror stories all over these pages of people bricking their devices.
There seem to be so many don'ts, last one is flashing ICS via mobile Odin caused a brick.
If there's someone in the know, give us some do's and don'ts.
I'm really surprised there isn't a sticky thread here already about this. And before anyone says search and read, that's what I've been doing all week and I'm more confused and concerned than ever!
I really hate the lag with HC and want ICS.....
As flashing and rooting always have the risk...cant commit there is 100% guarantee
What I do will be as follow; which I believe this should be the safest way.
- from HC, PC Odin to ICS
- Root : http://forum.xda-developers.com/showthread.php?t=1849235
- Flash Locerra's cwm using Mobile Odin
- Flash Ezy kernel as it have removed MMC_CAP_ERASE (BrickBug)
Once on ICS, with locerra's cwm and ezy kernel
- Full wipe
Astrix Ashburn said:
As flashing and rooting always have the risk...cant commit there is 100% guarantee
What I do will be as follow; which I believe this should be the safest way.
- from HC, PC Odin to ICS
- Root : http://forum.xda-developers.com/showthread.php?t=1849235
- Flash Locerra's cwm using Mobile Odin
- Flash Ezy kernel as it have removed MMC_CAP_ERASE (BrickBug)
Once on ICS, with locerra's cwm and ezy kernel
- Full wipe
Click to expand...
Click to collapse
Thanks, this is what I was hoping for. Appreciate nothing is 100% safe, I have recently had the "unknown baseband" problem with my S3 which is one of the reasons I'm trying to be careful here.
The only issue here is EZY kernel is P6800 and I have a P6810. Is there a "safe" kernel for the 6810?
Thanks for the advice so far...
Update - apologies. I've found the thread for EZY kernel for 6810
Method I used so far from stock HC-> rooted LQ1-> rooted LQ2 on P6800.
Desktop odin followed by this. No wiping or clear cache in desktop odin or temporary cwm. A little tedious but no issues so far in the 2 upgrades.
wkweksl said:
Method I used so far from stock HC-> rooted LQ1-> rooted LQ2 on P6800.
Desktop odin followed by this. No wiping or clear cache in desktop odin or temporary cwm. A little tedious but no issues so far in the 2 upgrades.
Click to expand...
Click to collapse
Thank you.
I suppose a factory reset / wipe shouldnt be required as it wouldnt happen with an upgrade via Kies.
robt2379 said:
Thank you.
I suppose a factory reset / wipe shouldnt be required as it wouldnt happen with an upgrade via Kies.
Click to expand...
Click to collapse
factory reset is not required... i'm usually use factory reset when something goes bad and i need the device to start with fresh and clean setup...
edan1979 said:
factory reset is not required... i'm usually use factory reset when something goes bad and i need the device to start with fresh and clean setup...
Click to expand...
Click to collapse
From my reading, it seems the factory reset / full wipe / dalvik wipe is where the danger lies in hitting the brick bug.
Once the unit is upgraded and running Locerras CWM and the EDY kernel, am I right in thinking a wipe through CWM is safe as the particular MMC cap erase command is disabled?
robt2379 said:
From my reading, it seems the factory reset / full wipe / dalvik wipe is where the danger lies in hitting the brick bug.
Once the unit is upgraded and running Locerras CWM and the EDY kernel, am I right in thinking a wipe through CWM is safe as the particular MMC cap erase command is disabled?
Click to expand...
Click to collapse
locerras cwm has already disable the mmc_cap_erase command... so even without EDY kernel... its safe to wipe using locerra cwm
Ok. I'm still really worried about this having read of several more bricked tabs in the last couple of days.
Can anyone confirm, is it safe to do a factory reset through stock GB (my tab is still completely stock, no root, no CWM) and therefore remove all my added software and data before I do anything else? It seems to me that if I return the tab back to "out of the box" state before I upgrade then its less likely a wipe / reset will be needed after I upgrade to ICS?
From reading it seems that all the danger comes once the upgrade to ICS is done.
Thanks
stock is honeycomb... Yes it is totally safe to factory reset through honeycomb.
Thanks for the advice.
I have now rooted, applied Locerras CWM and installed ICS and everything went fine (used Mobile Odin in the end).
Really pleased with the upgrade and relieved that nothing went wrong! Didn't do the factory reset in the end, that may come later when I start playing with some more roms. Already thinking about Paranoid....
Good luck to all who take the same steps.....
Finally got my tablet back from Asus which came with JB. Is there a way to make it unbrickable like you could with ICS? I want to install custom rom again to get rid of the massive amounts of bloatware. Suggestions?
bigworm82 said:
Finally got my tablet back from Asus which came with JB. Is there a way to make it unbrickable like you could with ICS? I want to install custom rom again to get rid of the massive amounts of bloatware. Suggestions?
Click to expand...
Click to collapse
Nvflash is not possible on jb right now.
If you don't want to unlock and flash a custom rom you could disable the bloatware apps to get rid of them.
Sent from my Transformer Pad TF300T using Tapatalk HD
bigworm82 said:
Finally got my tablet back from Asus which came with JB. Is there a way to make it unbrickable like you could with ICS? I want to install custom rom again to get rid of the massive amounts of bloatware. Suggestions?
Click to expand...
Click to collapse
There are apps out on the play store to remove bloatware. (Root Required) Give NoBloat or Root App Deleter a try
I unlocked it once before.. installed cleanrom. Wanted to install updated cleanrom. When i went to factory reset it or whatever and did the press up to continue. Thats when it bricked the first time. Was it from me doing something wrong there that caused it to brick?? I guess if i know that there is something I need to do that i didn't do than I will make sure to do it right. I didn't think doing a factory reset just to install a different rom was going to brick the unit . So now $150 later and back with locked tablet really just don't want the bloatware which is why i liked cleanrom.
dont mess around with it
My advice is not to try anything risky on it.
This device is such a bad one that it bricks by itself (happened to me)
and it is impossible to unbrick,
so my advice is not to mess around with it if you dont want to pay again.
bigworm82 said:
I unlocked it once before.. installed cleanrom. Wanted to install updated cleanrom. When i went to factory reset it or whatever and did the press up to continue. Thats when it bricked the first time. Was it from me doing something wrong there that caused it to brick?? I guess if i know that there is something I need to do that i didn't do than I will make sure to do it right. I didn't think doing a factory reset just to install a different rom was going to brick the unit . So now $150 later and back with locked tablet really just don't want the bloatware which is why i liked cleanrom.
Click to expand...
Click to collapse
Don't use WIPE DATA on the bootloader menu; I think that is what you described. It is a perfect brick maker!
The new Hydro 5 has most bloat removed. It is smooth and easy; not fast. I don't do games so I can't speak to that.
Take your time, there's no hurry. To remove bloat you will need to root or flash a custom rom, on JB that means unlock!
Once you have some ideas from this post read the related threads and make your decisions. Till then that bloat will wait!
Good Luck!
wipe data was what I did before. How do I have all the data go away if i want to reinstall a different rom? I'm familiar with rooting and what not. As I said I had unlocked the tablet before. I didn't know wiping data would make it brick though . I also had an Epic 4g that I had rooted and customed etc..
bigworm82 said:
wipe data was what I did before. How do I have all the data go away if i want to reinstall a different rom? I'm familiar with rooting and what not. As I said I had unlocked the tablet before. I didn't know wiping data would make it brick though . I also had an Epic 4g that I had rooted and customed etc..
Click to expand...
Click to collapse
Use Wipe/Factory Reset in Twrp; not WIPE DATA in the bootloader menu.
tobdaryl said:
Use Wipe/Factory Reset in Twrp; not WIPE DATA in the bootloader menu.
Click to expand...
Click to collapse
Hey Tobdaryl,
Is there any reason why using WIPE DATA from the bootloader menu bricks it? Apparently my NVFlash adventures have lead me to discover that my bootloader is iffy, and I want to do a COMPLETE 100% total wipe of my tablet, and then just flash stock JB on it and be done.
Any advice sir?
opethfan89 said:
Hey Tobdaryl,
Is there any reason why using WIPE DATA from the bootloader menu bricks it? Apparently my NVFlash adventures have lead me to discover that my bootloader is iffy, and I want to do a COMPLETE 100% total wipe of my tablet, and then just flash stock JB on it and be done.
Any advice sir?
Click to expand...
Click to collapse
I'm sorry I don't know the reason WIPE DATA(bootloader) bricks, just that it does. This comes from information provided by those that are unable to recover from what should be a soft brick. Several others are telling the same as I in an attempt to stop some of the bricks.
You can safely use Twrp to wipe Cache, Dalvik Cache, Factory Reset, System, and then flash the factory update of choice. You should be clean at that point.
One warning ensure you have your file to flash on your sdcard (not internal) before you do this and you can access it from Twrp. You do not want to wipe those and reboot without flashing some replacement.
tobdaryl said:
I'm sorry I don't know the reason WIPE DATA(bootloader) bricks, just that it does. This comes from information provided by those that are unable to recover from what should be a soft brick. Several others are telling the same as I in an attempt to stop some of the bricks.
You can safely use Twrp to wipe Cache, Dalvik Cache, Factory Reset, System, and then flash the factory update of choice. You should be clean at that point.
One warning ensure you have your file to flash on your sdcard (not internal) before you do this and you can access it from Twrp. You do not want to wipe those and reboot without flashing some replacement.
Click to expand...
Click to collapse
Yea I can use CWM to perform all those tasks as well. As long as that is a complete wipe, then I will be happy.
It's OK, in my experience, if you wipe and accidentally delete your file on the internal SD card. Just flash it via Fastboot, no big deal
I will work on this at work today after I get these programming assignments taken care of. Thanks for the advice!!!
Your tablet can be unbrickable, but you have to sign the special petition (look at my signature).If you helped sharing petition, It would get succes. There's not another way.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
opethfan89 said:
Yea I can use CWM to perform all those tasks as well. As long as that is a complete wipe, then I will be happy.
It's OK, in my experience, if you wipe and accidentally delete your file on the internal SD card. Just flash it via Fastboot, no big deal
For Info: While you are in CWM or Twrp adb works properly if you have previously established your drivers.
I will work on this at work today after I get these programming assignments taken care of. Thanks for the advice!!!
Click to expand...
Click to collapse
You are welcome, good luck!
The title of this thread is a little misleading at first glance it's not a question but gives the appearance that maybe a nvflash solution has been found.
Sent from my ASUS Transformer Pad TF300T using xda premium
What is the best way to install CWM on my TF300T, I am on the 4.2 bootloader, and I tried to put the CORRECT JB 4.2 version of TWRP 2.5.0 and it is like a split screen and will not function. Some time before that it asked for a password when I booted the recovery. I just want to start fresh with Clockwork Mod I guess.
Please point me in the correct direction.
Thank you
ScottBroker said:
What is the best way to install CWM on my TF300T, I am on the 4.2 bootloader, and I tried to put the CORRECT JB 4.2 version of TWRP 2.5.0 and it is like a split screen and will not function. Some time before that it asked for a password when I booted the recovery. I just want to start fresh with Clockwork Mod I guess.
Please point me in the correct direction.
Thank you
Click to expand...
Click to collapse
Not to be a douche but use the search function. And use twrp. Cwm is too buggy on the tf300. Its very easy for it to bug out and brick your pad.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mhays705 said:
Not to be a douche but use the search function. And use twrp. Cwm is too buggy on the tf300. Its very easy for it to bug out and brick your pad.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
well you are being a DB!
Do you not think I would search , too many posts with too many options.
TY for nothing. TWRP on TF3000T is very buggy btw.
ScottBroker said:
well you are being a DB!
Do you not think I would search , too many posts with too many options.
TY for nothing. TWRP on TF3000T is very buggy btw.
Click to expand...
Click to collapse
If you searched you would have seen all your questions are answered in the stickies. Also you would have seen twrp is recommended over cwm due to cwm bricking devices. I'm sure you would prefer that not to happen.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
If anyone has some useful information, please let me know.
Thanks
ScottBroker said:
If anyone has some useful information, please let me know.
Thanks
Click to expand...
Click to collapse
First and foremost learn how to search. Its a damn stickied topic. Here is what your looking for took less than a minute to search. http://forum.xda-developers.com/showthread.php?t=2187982
If you learned to read you wouldn't have a double screened twrp.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have tried that and still get a split screen, that is why I want to just flash CWM.
I have looked at that thread as well..
ScottBroker said:
I have tried that and still get a split screen, that is why I want to just flash CWM.
I have looked at that thread as well..
Click to expand...
Click to collapse
Update to the most recent boot loader. I'm trying to tell you. You have to use twrp. Cwm bricks the tf300t while flashing ROMs. Everyone advises not to use it. I don't even think there's a guide here for it since its too much of a liability. If your getting a split screen you are doing something wrong. Reading everything and doing everything exactly right is the name of the game here. The tf300 is way to easy to brick. If your having problems just installing a custom recovery your best to just stay away from flashing on this device. You have to pay attention to boot loader version and firmware version or you are going to get errors. Your lucky you haven't hard bricked yet.
I know what I'm talking about. I didn't just fall off the turnip truck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mhays705 said:
Update to the most recent boot loader. I'm trying to tell you. You have to use twrp. Cwm bricks the tf300t while flashing ROMs. Everyone advises not to use it. I don't even think there's a guide here for it since its too much of a liability. If your getting a split screen you are doing something wrong. Reading everything and doing everything exactly right is the name of the game here. The tf300 is way to easy to brick. If your having problems just installing a custom recovery your best to just stay away from flashing on this device. You have to pay attention to boot loader version and firmware version or you are going to get errors. Your lucky you haven't hard bricked yet.
I know what I'm talking about. I didn't just fall off the turnip truck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the advise, but as you can see, I have almost 3 times the thanks than you have posts. But anyway, I have been flashing for years, I have had every Iphone, and every Galaxy and have not had problems like with the tablet. I like TWRP, I have the latest bootloader, I am on 4.2.....
Maybe I will just return to stock and start fresh again...
Thanks anyway
ScottBroker said:
Thanks for the advise, but as you can see, I have almost 3 times the thanks than you have posts. But anyway, I have been flashing for years, I have had every Iphone, and every Galaxy and have not had problems like with the tablet. I like TWRP, I have the latest bootloader, I am on 4.2.....
Maybe I will just return to stock and start fresh again...
Thanks anyway
Click to expand...
Click to collapse
FYI, I went back to stock, and reflashed, and now with your helpful guide, I am back on TWRP.
TY
ScottBroker said:
FYI, I went back to stock, and reflashed, and now with your helpful guide, I am back on TWRP.
TY
Click to expand...
Click to collapse
This is defiantly one of the most sensitive device to do everything on. Asus wasn't to friendly. Its like they want you to brick. And my bad about the rudeness extreme lack of sleep has made me very irritable.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Indeed flashing cwm is another way to brick the TF300. Lucky you didn't flash it.
The problem is that the latest bootloader changes the partition table on the TF300 - it makes /system larger in order to accommodate the larger Asus ROM. The issue is most of the legacy recoveries including the non 4.2 twrp and cwm don't understand this and thus the device becomes bricked as the partition table is now messed up.
sbdags said:
Indeed flashing cwm is another way to brick the TF300. Lucky you didn't flash it.
The problem is that the latest bootloader changes the partition table on the TF300 - it makes /system larger in order to accommodate the larger Asus ROM. The issue is most of the legacy recoveries including the non 4.2 twrp and cwm don't understand this and thus the device becomes bricked as the partition table is now messed up.
Click to expand...
Click to collapse
Gotta love sbdags knowledge and amazing rom
Sent from my SAMSUNG-SGH-I747 using xda app-developers app