Database Info

My tab is in danger of brickbug HELP please

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

[Q] Help with upgrading from GB to ICS via Kies

So I had downloaded Kies and it was ready to upgrade my blaze to ICS, but I read that the phone should be unrooted first. So I did this:
http://forum.xda-developers.com/showthread.php?t=1591601
Apparently that was a mistake. Now I get the following error in Kies:
"Your device does not support software upgrading via Kies" "Current firmware version: PDA:LB7 / PHONE:LF4 / CSC:LB7 (TMB)"
Should I have just upgraded without unrooting? Why is it telling me this? I thought this was the stock ROM? If I keep flashing me Blaze with different ROMs without completely reformatting, will that slow it down?

You gotta go back to the OG rom before the first update.... If u look there is a thread about it on here somewhere
Sent from my SGH-T769 using xda app-developers app

WhaleWithWings said:
So I had downloaded Kies and it was ready to upgrade my blaze to ICS, but I read that the phone should be unrooted first. So I did this:
http://forum.xda-developers.com/showthread.php?t=1591601
Apparently that was a mistake. Now I get the following error in Kies:
"Your device does not support software upgrading via Kies" "Current firmware version: PDA:LB7 / PHONE:LF4 / CSC:LB7 (TMB)"
Should I have just upgraded without unrooting? Why is it telling me this? I thought this was the stock ROM? If I keep flashing me Blaze with different ROMs without completely reformatting, will that slow it down?
Click to expand...
Click to collapse
use the file from here http://forum.xda-developers.com/showthread.php?p=32313738
i used this and it worked

woodzx67 said:
use the file from here http://forum.xda-developers.com/showthread.php?p=32313738
i used this and it worked
Click to expand...
Click to collapse
I used this and now Kies is timing out trying to upgrade to ICS when it gets to the 100% downloading firmware part. Apparently reading the thread this tar isn't good for upgrading to ICS. But you did somehow?

Yup it took me a couple tries but it worked
Sent from my SGH-T769 using xda premium

WhaleWithWings said:
I used this and now Kies is timing out trying to upgrade to ICS when it gets to the 100% downloading firmware part. Apparently reading the thread this tar isn't good for upgrading to ICS. But you did somehow?
Click to expand...
Click to collapse
that's a kies issue. lets face it, it sucks. but that's the only tar I've been able to find that puts it back to Samsung Official and allows you to upgrade via kies. If you dont trust the links I have, you can find the tar at sammobile.com but you'll have to register to download

WhaleWithWings said:
I used this and now Kies is timing out trying to upgrade to ICS when it gets to the 100% downloading firmware part. Apparently reading the thread this tar isn't good for upgrading to ICS. But you did somehow?
Click to expand...
Click to collapse
The tar from http://forum.xda-developers.com/showthread.php?t=1917570
[FIX] "Your device does not support software upgrading via kies" is fine and 100% working. I can personally confirm this ;]
Sent from my SAMSUNG-SGH-T769 using xda premium

I never understood why people choose to use Kies... I personally hate it. It is much faster and easier to do it the XDA way and root/CWM and then flash whatever rom you want. If you want I'll post the quicker way to do this. No one has hard bricked from this method and its quite simple.
Root your device (you already have I see)
Install CWM HERE. (make sure not to check re-partition)
Boot into CWM by holding Volume UP and Volume DOWN and pressing POWER. USB must be unplugged. (could take up to 20 seconds to load CWM)
Flash your new ICS modem HERE in CWM
Now you can install any ROM you wish. You can install the stock ICS rom or a modified ROM. It is best to always have CWM just in case something messes up you have options to fix. If you install through Kies you have to install CWM over again anyways. This is faster. Now to install a ROM, there is a common process that will help out....
To install a ROM:
Boot into CWM
Perform a factory/reset
Wipe cache
Wipe Dalvik cache (under advanced)
Install zip (ROM)
Reboot and let your phone sit for at least 5 minutes, 10 is preferred.
Newbie Guide for Modding
You can read the above link for a small rundown on CWM and its available options. If you are here on XDA you probably should have CWM.

I had unrooted my device before installing CWM and didn't see the part that says to root it before hand. I installed it, seems to work fine. Will I have any problems.
Also, I just learned you're instructions are missing a step, I have flash the actual ICS ROM here:
http://forum.xda-developers.com/showthread.php?t=1918608
Before the radio mod you listed. Other than that, thanks!
P.S. What do you mean by "modem"?

Unbrickable stock JB possible

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

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

WARNING WARNING please read before rooting!!!

I know this isn't technically the right section for this but I put it here in hopes more people would see it. This is very important for anyone rooting using the dirtysanta method and perhaps other methods as well. It would be nice if this could get a sticky because people need to see this or this problem is going to keep occurring. I'm seeing it all over the threads.
DO NOT FACTORY RESET FROM INSIDE THE ROM. DO NOT USE LG's BUILT IN FACTORY RESET IN THE PHONE OR YOU WILL GET STUCK IN RECOVERY. Use the factory reset option inside of TWRP if you want to do a factory reset.
There have been many people (myself included even though I knew better and told myself not to do it before I did) who have got stuck in recovery because of this and it's not common sense to get out of it. I've been rooting and messing with this stuff for over 5 years and for 2 hours tried every trick I knew and nothing worked. What did finally end up working for me personally is this:
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power (hold them down), as soon as you see the LG logo let go of power for a brief moment and continue to press and hold both buttons until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount storage button, and reboot system.

lol this is only because it give you your stock boot.img. So if you factory reset, you have to flash SuperSU, no need to freak out.
If you format /system, you will need to flash a ROM, if the ROM does not flash SuperSU, you will h ave to flash it.
That's all folks!
That said, who wants a VZW Custom ROM and Kernel? Making the thread now. Identical to my H918 5.1 MOD ROM

Tilde88 said:
lol this is only because it give you your stock boot.img. So if you factory reset, you have to flash SuperSU, no need to freak out.
If you format /system, you will need to flash a ROM, if the ROM does not flash SuperSU, you will h ave to flash it.
That's all folks!
That said, who wants a VZW Custom ROM and Kernel? Making the thread now. Identical to my H918 5.1 MOD ROM
Click to expand...
Click to collapse
I tried flashing supersu.zip but that wouldn't work either. I challenge you to factory reset in the rom and then once stuck in recovery flash a new rom and the supersu zip and see if that works. I did this several times and it wouldn't work. I tried it with flashing a rom, and after restoring a backup. What appears to be happening is the system isn't mounting and it doesn't recognise that you have a ROM installed.
Not freaking out either, just trying to let people know not to factory reset inside the rom but use TWRP. There have been many people with this issue.

imucarmen said:
I tried flashing supersu.zip but that wouldn't work either. I challenge you to factory reset in the rom and then once stuck in recovery flash a new rom and the supersu zip and see if that works. I did this several times and it wouldn't work. I tried it with flashing a rom, and after restoring a backup. What appears to be happening is the system isn't mounting and it doesn't recognise that you have a ROM installed.
Not freaking out either, just trying to let people know not to factory reset inside the rom but use TWRP. There have been many people with this issue.
Click to expand...
Click to collapse
Oh, sorry. I overlooked something. That you had in huge bold caps the words IN THE ROM lol, my bad. I've never factory reset from within the ROM.
But my post stands when factory resetting from TWRP.

Tilde88 said:
Oh, sorry. I overlooked something. That you had in huge bold caps the words IN THE ROM lol, my bad. I've never factory reset from within the ROM.
But my post stands when factory resetting from TWRP.
Click to expand...
Click to collapse
Yea I knew better too, that's the bad part. In 5+ years I've never factory reset while in a rom when I have root and TWRP installed. Before I did it I even told myself it was probably a bad idea and I should just use TWRP. But my lazy conscience said "ahhh what the heck! just do it, it's too much trouble to boot into TWRP and besides, it might work ok" I hate my lazy consicence :'(

Exactly what I did and exactly what happened.
Gonna try this in the AM. One question...
If I'm able to flash back to "stock" using a deoxed stock rom, how can I then get rid of the boot warning so I can return this device to T-Mobile?

mrbigdrawsz said:
Exactly what I did and exactly what happened.
Gonna try this in the AM. One question...
If I'm able to flash back to "stock" using a deoxed stock rom, how can I then get rid of the boot warning so I can return this device to T-Mobile?
Click to expand...
Click to collapse
You'll need to return to full stock. I can't verify it works but this thread here claims to have a method for returning to stock.

imucarmen said:
You'll need to return to full stock. I can't verify it works but this thread here claims to have a method for returning to stock.
Click to expand...
Click to collapse
Well pray for me. Downloading now and will try first thing tomorrow.

mrbigdrawsz said:
Well pray for me. Downloading now and will try first thing tomorrow.
Click to expand...
Click to collapse
Did it work for you? Also since there is no t mobile rom there what did you use?

thegameksk said:
Did it work for you? Also since there is no t mobile rom there what did you use?
Click to expand...
Click to collapse
I used this guide https://goo.gl/ZHZPfO and it worked perfectly. Had a little stress when attempting to flash the stock recovery, but after installing two again, I was able to revert back to stock. Locked bootloader and it's as if I never did anything but boot up the stock OS.
Returning to T-Mobile today and just waiting on my Oneplus 3T to ship (granted I'm pissed off because the 128gb version is out of stock).

mrbigdrawsz said:
I used this guide https://goo.gl/ZHZPfO and it worked perfectly. Had a little stress when attempting to flash the stock recovery, but after installing two again, I was able to revert back to stock. Locked bootloader and it's as if I never did anything but boot up the stock OS.
Returning to T-Mobile today and just waiting on my Oneplus 3T to ship (granted I'm pissed off because the 128gb version is out of stock).
Click to expand...
Click to collapse
Glad you got it fixed.
Just for the record, this thread isn't for helping people get back to stock, its main focus is to warn people not to factory reset inside the rom. Then I just shared the method that worked for me to get out of being stuck in TWRP. Not saying you implied any different, I'm just clarifying for anyone that may read in the future. It's awesome return to stock methods are now popping up which are usually good for fixing all sorts of issues.
Enjoy your OnePlus 3T