Related
As the title suggests I am stock gingerbread (the one pushed then oulled back). I would like to remain this way until cm7 has become official for the thunderbolt or at least until it has a few of the bugs ironed out in the rom so we don't have to flash fixes.
Anyway I am familiar with the method of renaming otacerts.zip to otacerts.zip.bak and I have done that.
I wonder if others have had success blocking ota's with that method?
Is anyone familiar with a better method?
recDNA said:
As the title suggests I am stock gingerbread (the one pushed then oulled back). I would like to remain this way until cm7 has become official for the thunderbolt or at least until it has a few of the bugs ironed out in the rom so we don't have to flash fixes.
Anyway I am familiar with the method of renaming otacerts.zip to otacerts.zip.bak and I have done that.
I wonder if others have had success blocking ota's with that method?
Is anyone familiar with a better method?
Click to expand...
Click to collapse
well, renaming files at least works for boot animations & such, so i don't see why it wouldn't work for that ota file. normally, if it's something i don't want/need, i'll either freeze it or remove it entirely. try 'Anttek App Manager'(it's free).
additionally, i wouldn't wait around on an "official" CM7 for the Thunderbolt as that may never happen. i find at least that the latest 'SHIFTAO5P" roms that dhacker is now working on are the most stable ones and seem to have everything working ok.
recDNA said:
As the title suggests I am stock gingerbread (the one pushed then oulled back). I would like to remain this way until cm7 has become official for the thunderbolt or at least until it has a few of the bugs ironed out in the rom so we don't have to flash fixes.
Anyway I am familiar with the method of renaming otacerts.zip to otacerts.zip.bak and I have done that.
I wonder if others have had success blocking ota's with that method?
Is anyone familiar with a better method?
Click to expand...
Click to collapse
Has anyone actually tried the method I mentioned
Did it work
Now that an ota IS being pushed I guess i'll find out the hard way unless someone can help me out?
I got a OTA request right before I updated from Stock Rooted Gingerbread to the current stock rooted.
Now I'm on the current version same as OTA but rooted, renamed otacert.zip.bak but still had in the software update "deferred update pending".
Not sure how to stop this. Any help appreciated.
Can't u accept the OTA n just reinstall Superuser as long as ur S-Off? Been awhile so I can't remember.
Sent from my ADR6400L using xda premium
I accepted the OTA this evening & now I'm stuck. It shut down to then reboot & I ended up stuck at the triangle ! screen for over an hour.
Removing the battery & turning it on allows me to get it back, but as soon as the system is loaded it powers down again to complete the update...
Rooted via Revolutionary method & I'm stuck until someone with more xp comes along & can point me in the correct direction.
My bad.
Tantalin said:
I accepted the OTA this evening & now I'm stuck. It shut down to then reboot & I ended up stuck at the triangle ! screen for over an hour.
Removing the battery & turning it on allows me to get it back, but as soon as the system is loaded it powers down again to complete the update...
Rooted via Revolutionary method & I'm stuck until someone with more xp comes along & can point me in the correct direction.
My bad.
Click to expand...
Click to collapse
Rev method copies its own version of hboot and does not allow an OTA to copy over its own version. I could be completely wrong since i didnt use Revo to root my phone but you may want to try powering to hboot menu if you can power on you can get there, and try flashing the rooted version after full system wipe.
If I helped you in any way please use the thank you button
Could you just restore a nandroid?
I noticed when I updated manually (with help from mike and grlantern) that the file I had renamed otacerts.zip.bak is now back to otacerts.zip. I don't know if the update process created a new version or what but the date next to the zip folder is August, not October.
Is it possible for you to get to hboot by holding volume down as you push power key, then choose recovery, then restore to a nandroid (assuming you ever backed up your rooted rom).
I'm not sure if recovery will still be available though if the update made you s-on.
I'm no expert so perhaps you may want to wait for grlantern to chime in.
recDNA said:
I noticed when I updated manually (with help from mike and grlantern) that the file I had renamed otacerts.zip.bak is now back to otacerts.zip. I don't know if the update process created a new version or what but the date next to the zip folder is August, not October.
Is it possible for you to get to hboot by holding volume down as you push power key, then choose recovery, then restore to a nandroid (assuming you ever backed up your rooted rom).
I'm not sure if recovery will still be available though if the update made you s-on.
I'm no expert so perhaps you may want to wait for grlantern to chime in.
Click to expand...
Click to collapse
1. Have you ever looked at other files in there or files in windows. They don't update files that don't need updates so some files could be from launch of Thunderbolt if the file did not need an update.
2. Revo protects you from an RUU gaining S-On with its version of Hboot. I think the process of returning to stock by flashing an RUU is just for the ADB method which is what I used. I think Revo has to use a different method to regain stock.
If I helped you in any way please use the thank you button
You realize I was trying to give tanalin an idea of how to get his phone working again right?
I just thought he might be able to get into recovery and restore a nandroid or even wipe everything and install a custom rom? Of course I don't know if he can get into cwm.
recDNA said:
You realize I was trying to give tanalin an idea of how to get his phone working again right?
I just thought he might be able to get into recovery and restore a nandroid or even wipe everything and install a custom rom? Of course I don't know if he can get into cwm.
Click to expand...
Click to collapse
I was answering your file question while telling him why his OTA didn't work cause of the hboot problem
If I helped you in any way please use the thank you button
Grnlantern79 said:
1. Have you ever looked at other files in there or files in windows. They don't update files that don't need updates so some files could be from launch of Thunderbolt if the file did not need an update.
2. Revo protects you from an RUU gaining S-On with its version of Hboot. I think the process of returning to stock by flashing an RUU is just for the ADB method which is what I used. I think Revo has to use a different method to regain stock.
If I helped you in any way please use the thank you button
Click to expand...
Click to collapse
I'm in the same pickle as tantalin. Let me ask some dumb questions:
- I can get to the CWM recovery screen. Are you saying I could do a factory re-set, then restore the ROM pre-update? Would I have to have backed up before the OTA (which I didn't, as I only rooted yesterday...argh).
Thanks for your help.
Keep in mind Im a beginner too so you may want to wait for someone with more experience.
CHECK WITH AN EXPERIENCED USER BEFORE FOLLOWING MY DIRECTIONSDIRECTIONS
Yes, you would have had to have a rom to restore to. You could try wiping data, cache, and dalvik cache but I don't know whether phone would boot.
Another alternative would be to shut off phone, take out flash card, copy a custom rom like bamf forever 1.0.8 or the rooted version of the update on the sdcard. Put sdcard back in phone, turn on phone whole holding volume key down. Go to recovery. Wipe data, wipe cache, wipe dalvik cache (under advanced choices)Choose instal from sdcard. Browse to custom rom you put on sdcard. Choose it and install.
Keep in mind Im a beginner too so you may want to wait for someone with more experience.
TOTALLY INADVERTENT SUCCESS!!
I booted into clockworkmod recovery, deleted the cache partition, then under "advanced", I deleted the dalvik cache. I have literally no idea what either of these two things are, but since a factory reset was my worst case scenario, jimmy cracked corn and I didn't care.
Rebooted recovery (accidentally), then rebooted the phone. An error message saying the update failed! Happy day!
Now I can back the phone up properly, and go forward. So worried I'd lose all my apps and information not backed up to my Exchange server! Phew!!!!
If you have a rooted stock phone, and then you accept an OTA or load an RUU, you WILL lose root and the custom recovery program. But you SHOULD still be S-Off. If you are in that position right now, you need to re-flash the custom recovery to be able reload the SU app to regain root.
If you are actually back in S-on, you need to restart the root process from the beginning.
THEN BACK UP IMMEDIATELY BEFORE YOU DO ANYTHING ELSE....
---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------
Fastlivin said:
TOTALLY INADVERTENT SUCCESS!!
Click to expand...
Click to collapse
Good job.
Fastlivin said:
TOTALLY INADVERTENT SUCCESS!!
I booted into clockworkmod recovery, deleted the cache partition, then under "advanced", I deleted the dalvik cache. I have literally no idea what either of these two things are, but since a factory reset was my worst case scenario, jimmy cracked corn and I didn't care.
Rebooted recovery (accidentally), then rebooted the phone. An error message saying the update failed! Happy day!
Now I can back the phone up properly, and go forward. So worried I'd lose all my apps and information not backed up to my Exchange server! Phew!!!!
Click to expand...
Click to collapse
Excellent! I know that phew feeling all to well!
Now please, PLEASE READ THIS THREAD (You'll be glad you did!)
http://forums.androidcentral.com/showthread.php?p=829066
Grnlantern79 said:
Rev method copies its own version of hboot and does not allow an OTA to copy over its own version. I could be completely wrong since i didnt use Revo to root my phone but you may want to try powering to hboot menu if you can power on you can get there, and try flashing the rooted version after full system wipe.
If I helped you in any way please use the thank you button
Click to expand...
Click to collapse
I was able to get to HBOOT & I followed the steps in the 3rd post of this thread starting at step 5.
I didn't wipe anything (Wipe data, cache, and dalvik), so I don't know what the short term or long term effects are.
I used TiBup & My Backup Pro to restore my SMS/MMS...I don't really want to go any further until I know if I should go back & wipe those things & then do it over...anyone?
I ended up in the exact situation as the op. I went back to stock rooted with perm S-Off and the update got pushed to my phone.
When I noticed the phone trying to update but stuck at the screen you are describing I pulled the battery and went into recovery from hboot. In recovery under mounts there is an option to turn on sd storage or something like that. I've used it before so I knew it would allow me to access the sd card from pc. I then downloaded the rooted rom of the ota. Then I unmounted the phone from pc, rebooted recovery, and went through the normal rom installation.
Sent from my ADR6400L using xda premium
The only issue to me seems if you have something on the phone not backed up you want to keep. Even if the update installs and it updates the bootloader back to s-on, revolutionary root still works so you cam just re-root.
Edit: I recommend you head over to thunderboltforums to at least restore the bootloader to stock s-off if you want to accept the update and re-root.
Sent from my ADR6400L using Tapatalk
Hey, guys-
I'm unrooted and running stock Android. I have all of my settings and apps exactly how I like them right now.
In the past, I've flashed different ROMs and Kernels. When I get tired/frustrated with them and want to revert back to stock, I usually just do the 1 click revert back to factory settings. When you do that, it... well.. erases anything and everything in order to get back to factory settings.
Nothing is broke. I just don't want to delete my SD card contents and lose root. I just want to revert to the stock kernel and ROM from another ROM and kernel.
I was wondering if there's an easier way to get back to my current settings on the stock Android and Kernels WITHOUT using the 1 click revert back to factory method? If there is, could you PLEASE tell me how to do it EXACTLY? I say that because sometimes people on here give instructions that are clear as mud. Thanks!
Factory reset does NOT restore kernels or roms. It simply wipes user data.
You're confused. What you really want is a nandroid back up
If you have ROM Manager installed, open it up and go to "Download ROM". At the very bottom of the list, there should be a selection that says "Stock Images". I'm pretty sure you can use that to get back to stock. I'M NOT POSITIVE, I've never tried it before. It may unroot your phone/get rid of clockwork mod recovery. Just a suggestion
Remember to fastboot OEM lock
Sent from my HD2 using Tapatalk
shockem said:
Remember to fastboot OEM lock
Sent from my HD2 using Tapatalk
Click to expand...
Click to collapse
Ummm... what?
DangerZone1223 said:
Ummm... what?
Click to expand...
Click to collapse
That is to relock your bootloader. Just flash a stock rom in recovery with a full wipe, You'll be unrooted.
Stock roms can be found here.
http://forum.xda-developers.com/showthread.php?t=1063664
It's also wise to keep your content copied on a folder on your comp. 5 minutes of copying back and you got it all back. If you got all that sorted what you should always do is once you've got a stock rooted rom, run a nandroid backup/backup restore from CWM before you flash new roms / kernels.
People posting all this trash.
Nexus S 4G 1 Click : http://forum.xda-developers.com/showthread.php?t=1167819
Nexus S 1 Click : http://nexusshacks.com/nexus-s-hacks/how-to-unroot-nexus-s-i9020ti9020ai9023/
USE GOOGLE PEOPLE! If you don't know what you're talking about, keep your mouth shut!
The easiest method would've been to nandroid backup your OEM setup & restored it...
Exaxtly. GOOGLE IS YOUR TEACHER.google will teach you so much. Use it!!!!
Mish.Mash said:
People posting all this trash.
Nexus S 4G 1 Click : http://forum.xda-developers.com/showthread.php?t=1167819
Nexus S 1 Click : http://nexusshacks.com/nexus-s-hacks/how-to-unroot-nexus-s-i9020ti9020ai9023/
USE GOOGLE PEOPLE! If you don't know what you're talking about, keep your mouth shut!
The easiest method would've been to nandroid backup your OEM setup & restored it...
Click to expand...
Click to collapse
sent from my Nexus S
I currently have a Motorola Photon 4G running Android 2.3.4 and build 198_7. Simple question: If I unlock, will I be reset to stock?
The reason I ask...
Not long ago, I was running an installation of 198_6. For grins and giggles (and because I knew I'd be flashing the 198_7 SBF later), I flashed derpunlock.sbf, and successfully unlocked. I got into CWM 5.0.2.8 just fine. But after unlocking, I found my phone had been reset to stock. All I had done was flash derpunlock.sbf with RSDLite, then unlock using fastboot. I didn't think that would send me back to square one with a covert factory reset, but it did.
I should have unlocked right after updating to 198_7. But I didn't, because I'm an idiot. Now, I've put hours into configuring my phone, and don't want to lose it with a surprise reset after unlocking. Backing up with MyBackup and Titanium Backup (which I've done) help, but they don't fully cut it.
Does anyone know? Please.
JavaMocha said:
Does anyone know? Please.
Click to expand...
Click to collapse
Yes unlocking will usually do a factory reset. It will inform you on the phone and ask if you want to proceed though. I have never used a Motorola though, so you may want to ask in the specific Q&A forum for your device.
Sent from my Inspire 4G using xda premium
Thank you very much. I certainly wasn't prompted the first time I unlocked and a reset was done. I guess I don't see why it would be any different if I unlocked again.
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
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