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
Related
I did the easy unroor because my usb port is broke. But the superuser app is still there and I cant get rid of it. Need to rma. Any ideas?
I know of a guaranteed way to return to stock, but it's done through NVFlash in which you will need your usb port. You could either...
1. Look into other ways to return to stock which doesn't involve using your usb port (not likely)
2. Go to asus's website and download the firmware and place onto an sd card and see if you can do it that way. Even still, I'm not sure if that will just update, or wipe and update.
3. Shut down your TF and boot up by holding the volume down + power until you get to the option to wipe data and see if that does the trick. Once you get to that option, you only have like 5 10 seconds to select to wipe. If you don't select to wipe, then it will timeout and reboot
cavsoldier19d said:
I know of a guaranteed way to return to stock, but it's done through NVFlash in which you will need your usb port. You could either...
1. Look into other ways to return to stock which doesn't involve using your usb port (not likely)
2. Go to asus's website and download the firmware and place onto an sd card and see if you can do it that way. Even still, I'm not sure if that will just update, or wipe and update.
3. Shut down your TF and boot up by holding the volume down + power until you get to the option to wipe data and see if that does the trick. Once you get to that option, you only have like 5 10 seconds to select to wipe. If you don't select to wipe, then it will timeout and reboot
Click to expand...
Click to collapse
I already installed the original stock rom. And also flashed the stock recovery. I wiped everything each time. But after all that superuser is still there.
Well that sucks. I know of a way to do a full wipe of everything by using a full wipe utility that is flashed by clockworkmod recovery. But then you would have to find a way to restore the stock recovery in order to flash the stock rom. If you do a full wipe without reflashing a rom, then you will have soft bricked it. You might be SOL on that.
cavsoldier19d said:
Well that sucks. I know of a way to do a full wipe of everything by using a full wipe utility that is flashed by clockworkmod recovery. But then you would have to find a way to restore the stock recovery in order to flash the stock rom. If you do a full wipe without reflashing a rom, then you will have soft bricked it. You might be SOL on that.
Click to expand...
Click to collapse
So you think if I wipe it so its in the initial setup. That asus will set it up and see superuser. I mean can they even prove anything just cause theres an app there.
lightsout said:
So you think if I wipe it so its in the initial setup. That asus will set it up and see superuser. I mean can they even prove anything just cause theres an app there.
Click to expand...
Click to collapse
Not sure about that. Ideally, when doing rma returns, to be on the safe side, you want to make it completely transparent that it was ever rooted/rom'ed. I've read posts where some people were successful with returns/exchanges while the device was rooted, without repercussions. It's all up to the return policies of where you bought it, as well as asus. Considering that asus has gone out of their way to change and lock down the bootloader on newer revisions, apparently asus does not want to be development friendly at this time, and may penalize you for returning a modified system.
cavsoldier19d said:
Not sure about that. Ideally, when doing rma returns, to be on the safe side, you want to make it completely transparent that it was ever rooted/rom'ed. I've read posts where some people were successful with returns/exchanges while the device was rooted, without repercussions. It's all up to the return policies of where you bought it, as well as asus. Considering that asus has gone out of their way to change and lock down the bootloader on newer revisions, apparently asus does not want to be development friendly at this time, and may penalize you for returning a modified system.
Click to expand...
Click to collapse
Yah I know man thats what I'm afraid of. I mean anyone can install superuser. But I guess though it wouldn't be there on a clean install
Kind of stuck here. Its too late to return tot he store. But I don't want to be stuck with a bad usb port forever. I guess the worst that can happen is they refuse it.
Or if they accept it at first, then asus realizes that its been rooted, they could send u a bill for full price of the replacement. Although I've never heard of that happening. Another extreme measure u could look into is seeing if u could order a motherboard or replacement parts and fix it yourself.
Sent from my Inspire 4G using XDA App
cavsoldier19d said:
Or if they accept it at first, then asus realizes that its been rooted, they could send u a bill for full price of the replacement. Although I've never heard of that happening. Another extreme measure u could look into is seeing if u could order a motherboard or replacement parts and fix it yourself.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Ouch that would suck, as far as doing it myself I really don't want to mess with popping it open. It still charges, but I can't hook it to a pc. So I would rather have it like that then broken because I opened it.
I guess I'll just put it off a little more.
True. If I were u, I would take my chances with returning it. Just make sure u have the cash just in case they decide to be dicks about it.
Sent from my Inspire 4G using XDA App
The best and easiest way to flash a rom without having any bugs or flaws,etc.
follow this to a 'tee' and you will have no problems, guarantee you.
Instructions:
1. Download .rar from link and extract it
http://www.multiupload.com/FO6TA6OBAH
2. open odin
3. put pda into the pda, phone into phone (their all in the respective folders)
4. let it finish wiping your phone and everything
5. once your phone boots, back up everything on your internal sd
6. go into settings and do a factory reset then let the phone reboot
7. put the rom you want to flash onto your sd card
8. turn off the phone and go into download mode (both volume buttons then plug in your usb cord.) flash gtg's community kernel. (in the root folder, put that .tar into the pda section) let it finish converting the partions.
9. once it finishes and boots up do this:
turn off phone, then:
using three button method. (volume up, volume down, power button. once you see samsung label release power button and keep holding volume buttons til you see your touch buttons light up, thats the way i figured out when to release them)
10. once the red screen appears, do: wipe data/factory reset, wipe dalvik cache
11. install zip from sd card, choose the rom that you placed onto your sd card
good job. works for me!
Which version of flashing stock does this use? Gtg unbrick?
Sent om my SAMSUNG-SGH-I997 using XDA App
Haha, the best way is NEVER using ODIN. Heimdall is much much better.
And why would you return to stock before every flash?
AJerman said:
Haha, the best way is NEVER using ODIN. Heimdall is much much better.
And why would you return to stock before every flash?
Click to expand...
Click to collapse
A clean slate. I use to do this all the time with my Captivate. Never had any problems installing any rom. Still do it now with the Infuse, and no problems installing any rom or Hellraiser Hybrid rom.
bigfau said:
A clean slate. I use to do this all the time with my Captivate. Never had any problems installing any rom. Still do it now with the Infuse, and no problems installing any rom or Hellraiser Hybrid rom.
Click to expand...
Click to collapse
Never did it with the Captivate, never do it with the Infuse, never had any problems. You have a clean slate every time you flash a ROM as long as you wipe all the data and cache partitions. The system partitions are already overwritten with the flash itself. Basically going back to stock is just doing the same thing twice. Unless you are having some big problems and want to drop back to all stock files to see if you can fix a problem, it's generally unnecessary and just a waste of time. I mean, it doesn't hurt if you want to, it's just redundant.
All you gotta do is flash your ROM from Heimdall or CWM, wipe your data and cache partitions, boot up and you're done. As clean and fresh of a slate as it gets.
AJerman said:
Never did it with the Captivate, never do it with the Infuse, never had any problems. You have a clean slate every time you flash a ROM as long as you wipe all the data and cache partitions. The system partitions are already overwritten with the flash itself. Basically going back to stock is just doing the same thing twice. Unless you are having some big problems and want to drop back to all stock files to see if you can fix a problem, it's generally unnecessary and just a waste of time. I mean, it doesn't hurt if you want to, it's just redundant.
All you gotta do is flash your ROM from Heimdall or CWM, wipe your data and cache partitions, boot up and you're done. As clean and fresh of a slate as it gets.
Click to expand...
Click to collapse
yeah i've always had a question about this... would you mind answering?
some instructions say to wipe data factory reset wipe cache before installing custom ROM,
some say after install wipe data factory and all that...
any difference? same? thanks!
jhong91 said:
yeah i've always had a question about this... would you mind answering?
some instructions say to wipe data factory reset wipe cache before installing custom ROM,
some say after install wipe data factory and all that...
any difference? same? thanks!
Click to expand...
Click to collapse
I was once watching a youtube video on how to flash and he said something very simple, "wipe, fix, delete, get rid of, whatever. Old school rom flashing: make sure that you knock out everything so that you start on a fresh slate." Jordan is definitely right and knows much more than I. But I agree with AJerman that says its redundant. Just my two cents.
Jordan would you recommend using this method if you just got and rooted an infuse?
(have a warranty replacement on the way )
Sent from my SAMSUNG-SGH-I997 using XDA App
Using this method coming from Darky in an attempt to flash the FusionXII ROM, i recieved the message "installation aborted" after clockwork mod started and then ended the flash of the file. any advice? i cleared both data and dalvik in that order.
- Thanks
Odin back to Froyo, then Odin one of the gingerbread leaks, Odin entropys kernel, turn phone off and get into cwm and flash Fusion. Make sure to wipe data as well.
Sent from my SAMSUNG-SGH-I997 using xda premium
Bump - This should be a sticky
is there another link for it
GoSooners345 said:
is there another link for it
Click to expand...
Click to collapse
Yes please ...
Sent from my SPH-D710 using Tapatalk
Well said Jordan...glad I'm not the only one with that opinion....
Sent from my SAMSUNG-SGH-I997 using xda premium
Nice guide, it should definitely alleviate lots of the questions around. I'd reccomend maybe flashing a rom with the gb loaders somewhere near the end so that theres no more rainbow issues.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
can anyone please upload the package form op
should probably mention that this guide isn't for rogers users
threi_ said:
should probably mention that this guide isn't for rogers users
Click to expand...
Click to collapse
oh. Is there a guide for rogers I am looking for one
dlzp said:
oh. Is there a guide for rogers I am looking for one
Click to expand...
Click to collapse
Yeah people that can't read to save their lives.
http://forum.xda-developers.com/showthread.php?t=1326143
[Guide] [UXKG3] Complete Stock (FOR ROGERS USERS ONLY)
Do thank me.. That was hard work.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
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.....
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
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