Related
thederekjay; recognized dev from over in the T-Mobile forum (and many other places), has posted a custom full wipe script to be flashed each time before flashing a new rom. PLEASE READ HIS THREAD for full details...link below...
http://forum.xda-developers.com/showthread.php?t=1477955
I have flashed this wipe twice already with no problems.
Cool! this will be really useful
"After it is complete with format and erase, it will align all disks partitions properly"
I don't doubt it works great, but partition stuff makes me nervous.
It doesnt touch any internal or external memory.
orlandoxpolice said:
"After it is complete with format and erase, it will align all disks partitions properly"
I don't doubt it works great, but partition stuff makes me nervous.
Click to expand...
Click to collapse
Message relayed from the dark side.
Samsungs get finicky when you start messing with the partitions. I don't think Orlando was referring to the internal/next memory more so the boot and system partitions etc
chib1panda said:
It doesnt touch any internal or external memory.
Message relayed from the dark side.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I727 using XDA App
Well, i've used it 3 times now with no issue yet. No problems...what do you think 'wipe data/cache/dalvik' boils down too?
Sent from my Skyrocket using XDA App
Dude . If you are a skeptic then check out darksides thread and ask him for more details after reading the thread.
00mred00 said:
Samsungs get finicky when you start messing with the partitions. I don't think Orlando was referring to the internal/next memory more so the boot and system partitions etc
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
Message relayed from the dark side.
I'm not knocking it, just voiced a concern. if it has worked for you multiple times i dont doubt it validity. i will most likely use it next time i flash a new rom.
My skyrocket has only had crazy fc's once but seems like some are more susceptible to the fc's more than others. Wgich leads back to a subpar version of cwm...if running this script before flashing prevents crazy fc's, then it's a pretty big deal for our device. Mostly as a supplement to a cwm that requires wiping all partitions 3 times each in HOPES of a clean wipe.
Sent from my Skyrocket using XDA App
bacheezy said:
My skyrocket has only had crazy fc's once but seems like some are more susceptible to the fc's more than others. Wgich leads back to a subpar version of cwm...if running this script before flashing prevents crazy fc's, then it's a pretty big deal for our device. Mostly as a supplement to a cwm that requires wiping all partitions 3 times each in HOPES of a clean wipe.
Sent from my Skyrocket using XDA App
Click to expand...
Click to collapse
Yeah I have wondered why no one had written a script to do this sooner.
I like darksides work...haven't had any issues with anything he has produced so far.
00mred00 said:
Yeah I have wondered why no one had written a script to do this sooner.
I like darksides work...haven't had any issues with anything he has produced so far.
Click to expand...
Click to collapse
Can this script be added to the CWM touch version that was created. It seems that the CWM touch still has the same problem of not completely wiping data from the SkyRocket. If this script were to be incorporated into it, it might solve the CWM "wipe" problem?
wow thank you for the link. total time saver.
Its a cwm flashable zip...it should work I would think.
scott14719 said:
Can this script be added to the CWM touch version that was created. It seems that the CWM touch still has the same problem of not completely wiping data from the SkyRocket. If this script were to be incorporated into it, it might solve the CWM "wipe" problem?
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I727 using XDA App
Works perfect on Skyrocket.
Sent from my SAMSUNG-SGH-I727 using xda premium
So far it is working really well for me too
hcyplr29 said:
Works perfect on Skyrocket.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I727 using XDA App
so much better than having to flash back to odin
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.
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
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
PSA **********
Custom recoveries can wipe stock Rom files when you wipe data. HTC started loading pieces of the gallery/camera app to data via a preload option. The files will show up in /data/preload on a stock rom. IF you use ANY recovery other than stock, it will ERASE these files if you wipe data .. and you won't be able to restore them (without /data backup).
Be careful and if you need to simply factory reset make sure you use stock recovery as it will NOT erase these files.
dottat said:
PSA **********
TWRP needs updated to not erase certain pieces of userdata now. HTC started loading pieces of the gallery/camera app to data via a preload option. The files will show up in /data/preload on a stock rom. IF you use ANY recovery other than stock, it will ERASE these files.. and you won't be able to restore them (without /data backup).
Be careful and if you need to simply factory reset make sure you use stock recovery as it will NOT erase these files.
Click to expand...
Click to collapse
I have no issues here. Just tested stickers and everything and 0 issues. I am using official TWRP and have factory reset about 20 times. You should prob word your post diff or you're going to scare a lot of ppl for no reason.
droidkevlar said:
I have no issues here. Just tested stickers and everything and 0 issues. I am using official TWRP and have factory reset about 20 times. You should prob word your post diff or you're going to scare a lot of ppl for no reason.
Click to expand...
Click to collapse
Could be version specific. Which version do you have?
Did you restore your data partition?
Sent from my HTC6525LVW using Tapatalk
dottat said:
Could be version specific. Which version do you have?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
The official, 2.7.0.2
droidkevlar said:
The official, 2.7.0.2
Click to expand...
Click to collapse
When I wipe data on that it wipes /data/preload
Stickers then show up as white tiles.
Sent from my HTC6525LVW using Tapatalk
dottat said:
When I wipe data on that it wipes /data/preload
Stickers then show up as white tiles.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
This is why you should word your first post diff and not scare people. You said factory reset, you didnt mention wiping data partition. 2 diff things. When I flash, I only factor reset. Nothing else.
droidkevlar said:
This is why you should word your first post diff and not scare people. You said factory reset, you didnt mention wiping data partition. 2 diff things. When I flash, I only factor reset. Nothing else.
Click to expand...
Click to collapse
I see what you are saying there. Point taken...
Sent from my HTC6525LVW using Tapatalk
dottat said:
I see what you are saying there. Point taken...
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
No worries. Just rem that people search for issues and when they see possibly wrong info, it can cause more issues down the line. If you avent already, post this issue in the main thread for TWRP and Im sure they will fix it quickly
Anyone on stock Rom who has wiped data and lost the stickers in their gallery can use this zip to put them back.
http://www.androidfilehost.com/?fid=23329332407590188
Sent from my HTC6525LVW using Tapatalk
dottat said:
Anyone on stock Rom who has wiped data and lost the stickers in their gallery can use this zip to put them back.
http://www.androidfilehost.com/?fid=23329332407590188
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Off topic but cool to see a fellow XDA/M8 user from York on here!
mcp2009 said:
Off topic but cool to see a fellow XDA/M8 user from York on here!
Click to expand...
Click to collapse
Same! What's up, fella?!
dottat said:
Anyone on stock Rom who has wiped data and lost the stickers in their gallery can use this zip to put them back.
http://www.androidfilehost.com/?fid=23329332407590188
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
ethan.r.besbris said:
Same! What's up, fella?!
Click to expand...
Click to collapse
Hey! Look at that another one!
mcp2009 said:
Hey! Look at that another one!
Click to expand...
Click to collapse
Let's have an M8 party! Hahaha!
ethan.r.besbris said:
Let's have an M8 party! Hahaha!
Click to expand...
Click to collapse
Lol wonder how many more there are
@mcp2009 @ethan.r.besbris
Local rom parties soon... lol.. I support this device because my wife and daughter have it... I like my one max a LOT for now
I will have to keep you both in mind since I like to test on devices I can get my hands on...
By all means, brother!
I'm more than likely grabbing one of these, so this is good info to know. Thanks
While I think the OP has a valid concern, and therefore made this post, I have not had any problem such as this. I flash new ROM's all the time, and haven't experienced any problems at all. I do thank the OP for making this post
xRogerxC said:
While I think the OP has a valid concern, and therefore made this post, I have not had any problem such as this. I flash new ROM's all the time, and haven't experienced any problems at all. I do thank the OP for making this post
Click to expand...
Click to collapse
You will likely be safe on custom roms as the devs usually include /data files in their rom too. This really would only apply to a user on a stock rom who inadvertently wipes /data.
The only problem would show when you go to edit a picture in gallery and want to apply a sticker to it.
If this applies to you, you will know it